Hi, I had the same problem, here's my solution : https://github.com/OSGeo/gdal/blob/master/swig/python/gdal-utils/osgeo_utils/auxiliary/batch_creator.py
Idan On Wed, 12 Jan 2022, 23:22 Rafael Lima, <[email protected]> wrote: > I thought about uninstalling it to lol > > checking that PYTHONPATH or PYTHONHOME are not defined to an unexpected > value will be sufficient > > It was something of the sorts. The paths were actually fine, but the > "default windows app" is activated when calling a file with a .py > extension. So calling ogrmerge.py on the terminal would activate the > default app instead of the activated python =/ > Thanks! > > ------------------------------ > *De:* gdal-dev <[email protected]> em nome de Even Rouault > <[email protected]> > *Enviado:* quarta-feira, 12 de janeiro de 2022 16:09 > *Para:* [email protected] <[email protected]> > *Assunto:* Re: [gdal-dev] How to fix path for gdal .py scripts in > Anaconda-Windows? > > > I would have suggested to uninstall the offending proprietary software > :-), but perhaps checking that PYTHONPATH or PYTHONHOME are not defined to > an unexpected value will be sufficient > Le 12/01/2022 à 19:24, Rafael Lima a écrit : > > ## Expected behavior and actual behavior. > > I installed gdal on a Windows environment using anaconda and tried using > one of the .py scripts (e.g., ogrmerge.py). I expected the script to make > use of the gdal installed in such an environment, but it seems that the > script finds another gdal installation (screenshot below), thus throwing an > error. My question seems to be related to the one in > https://stackoverflow.com/questions/69328298/cannot-run-a-py-which-requires-a-gdal-module-in-anaconda-prompt-nor-in-command, > apparently unsolved. I was wondering what is the correct approach to make > sure gdal scripts find the correct gdal? > > ## Steps to reproduce the problem. > create a conda environment: > conda create -n test1 gdal > activate the environment > conda activate test1 > call a gdal .py script > ogrmerge.py > > In my case, that throws an error apparently because the script uses > another gdal installation: > > > ## Operating system > > Windows 10 Pro - 20H2 version > > ## GDAL version and provenance > > GDAL==3.0.2 > GDAL==3.4.0 > > Thank you! > Rafael > > _______________________________________________ > gdal-dev mailing > [email protected]https://lists.osgeo.org/mailman/listinfo/gdal-dev > > -- http://www.spatialys.com > My software is free, but my time generally not. > > _______________________________________________ > gdal-dev mailing list > [email protected] > https://lists.osgeo.org/mailman/listinfo/gdal-dev >
_______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
