Re: [gdal-dev] Running GDAL through Python >= 3.8 on Anaconda - DLL load failed

Hi pedro, Are you sure you are not mixing conda channels? Normally, in the same environment, you should stick to a single channel to avoid dependency problems. I also noticed that you are using anaconda. I suggest you use miniconda instead. It comes with the bare minimal tools to install and mana

[gdal-dev] Python gdal.Translate(...) and unicode in Band Descriptions.

Hi, The attached python script that reads from a vendor’s SPOT6 distribution archive and creates a cloud optimized geotiff. Reading and writing works, but the band description does not take properly. Problem 1: The greek letter Mu or Micron

Re: [gdal-dev] GeoTIFF: connection between CRS WKT and GeoKeys

Le 13/10/2021 à 18:35, Eric Robeck a écrit : I have a question about which GeoTIFF tags should be used for storing CRS information. I have two GeoTIFFs: one original and the same file saved as a COG. Then I created gdalinfo and listgeo reports for each and compared them for changes. *gdalinf

[gdal-dev] GeoTIFF: connection between CRS WKT and GeoKeys

I have a question about which GeoTIFF tags should be used for storing CRS information. I have two GeoTIFFs: one original and the same file saved as a COG. Then I created gdalinfo and listgeo reports for each and compared them for changes. *gdalinfo*: Aside from the difference in the PROJCRS citati

Re: [gdal-dev] Running GDAL through Python >= 3.8 on Anaconda - DLL load failed

I will ask on GDAL conda-forge, maybe this can be some packaging problem. Thanks! Pedro Venâncio escreveu no dia quarta, 13/10/2021 à(s) 17:00: > Tried to define several environment variables, but nothing seems to work > > [image: env_win10.jpg] > > > Joaquim Manuel Freire Luís escreveu no di

Re: [gdal-dev] Running GDAL through Python >= 3.8 on Anaconda - DLL load failed

Tried to define several environment variables, but nothing seems to work [image: env_win10.jpg] Joaquim Manuel Freire Luís escreveu no dia quarta, 13/10/2021 à(s) 16:23: > Não Pedro, > > > > When I look into my own build of the gdall dll I see no dependency on that > “opj_encoder_set_extra_opt

Re: [gdal-dev] Running GDAL through Python >= 3.8 on Anaconda - DLL load failed

Não Pedro, When I look into my own build of the gdall dll I see no dependency on that “opj_encoder_set_extra_options” but likely because it’s a different version (I build from master). From my experience on this there is really nothing one can do other than rebuild the dll or replace the depen

Re: [gdal-dev] Running GDAL through Python >= 3.8 on Anaconda - DLL load failed

Hi Joaquim, Thanks for sharing your case. Did you manage to make it work in some way? I've already uninstalled a test PostgreSQL/PostGIS that I supposed to be the source of the conflict, but I keep having the same error. I also reinstalled conda, but nothing had changed. Joaquim Manuel Freire

Re: [gdal-dev] Running GDAL through Python >= 3.8 on Anaconda - DLL load failed

Hi, I have a certain horror to python (that I’m trying to fight) a bit of it is because I never manage to really use it. I had and older Miniconda (Mini => 18 GB ) that was so big that I removed and installed a new one in which I tried Pedro’s case and got exactly the same errors. I then

Re: [gdal-dev] Running GDAL through Python >= 3.8 on Anaconda - DLL load failed

ok, so now you have to inspect the PATH and fix it so that the gdal DLL and its dependencies are in it. But all of this sounds like there's something weird in your environment. Perhaps a mix of GDAL versions? Le 13/10/2021 à 15:36, Pedro Venâncio a écrit : Can you change in __init__.py

Re: [gdal-dev] Running GDAL through Python >= 3.8 on Anaconda - DLL load failed

> Can you change in __init__.py > > try: > os.add_dll_directory(p) > except FileNotFoundError: > continue > > > to > > try: > os.add_dll_directory(p) > except (FileNotFoundErr

Re: [gdal-dev] Running GDAL through Python >= 3.8 on Anaconda - DLL load failed

Can you change in __init__.py     try:     os.add_dll_directory(p)     except FileNotFoundError:     continue to     try:     os.add_dll_directory(p)     except (FileNotFoundError, OSError):    

Re: [gdal-dev] Running GDAL through Python >= 3.8 on Anaconda - DLL load failed

> But I don't understand why you still get the "On Windows, with Python >= > 3.8, DLLs are no longer imported from the PATH." error message. > > It shouldn't be emitted because USE_PATH_FOR_GDAL_PYTHON is set: > https://github.com/OSGeo/gdal/blob/f3a83a2c2628219bdc60001580da677758015a60/gdal/swig/p

Re: [gdal-dev] Running GDAL through Python >= 3.8 on Anaconda - DLL load failed

Le 13/10/2021 à 14:05, Pedro Venâncio a écrit : Hi Even, Thanks for your help! Yes, I've tried "set USE_PATH_FOR_GDAL_PYTHON=YES" but the behaviour does not change. I believe OSGeo4W shell sets the environment variables through .bat files, and does not use system path. Am I right, Jurgen?

Re: [gdal-dev] Running GDAL through Python >= 3.8 on Anaconda - DLL load failed

Hi Even, Thanks for your help! Yes, I've tried "set USE_PATH_FOR_GDAL_PYTHON=YES" but the behaviour does not change. I believe OSGeo4W shell sets the environment variables through .bat files, and does not use system path. Am I right, Jurgen? (sorry for calling in CC) Meanwhile I've found those

Re: [gdal-dev] Running GDAL through Python >= 3.8 on Anaconda - DLL load failed

Pedro, Did you try to "set USE_PATH_FOR_GDAL_PYTHON=YES" environment variable a suggested ? Can you check if it set in OSGeo4W shell ?  ("echo %USE_PATH_FOR_GDAL_PYTHON%") Wondering if we shouldn't enable that behavior automatically... although that we would go against upstream Python poli

[gdal-dev] Running GDAL through Python >= 3.8 on Anaconda - DLL load failed

Hi all, I'm trying to create an Anaconda environment to run arosics, a software that performs automatic subpixel co-registration of two satellite image datasets. The environment seems correctly created, with GDAL working as expected on the CLI: (arosics) PS C:\Users\PedroVenancio> gdalinfo --ver