Upon reflection it seems to me that both of these are work arounds for
not having regular python wrapper executables created. Now that we can
`pip install gdal-utils` perhaps it's better to use pip to create the
wrappers. I have a little bit of experience with that and am will to
tackle the
On 2022-01-12 2:26 p.m., Idan Miara wrote:
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
On 2022-01-12 4:40 p.m., matt.wil...@yukon.ca wrote:
Also see OSGEO4W make-bat-for-py.bat
On Thu, 13 Jan 2022 at 07:25, Rafael Lima wrote:
> 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
>
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 =/
If you want to manage from the command line
g" %%* >> %%~ng.bat
)
```
-Matt
From: gdal-dev On Behalf Of Idan Miara
Sent: January 12, 2022 2:27 PM
To: Rafael Lima
Cc: gdal dev
Subject: Re: [gdal-dev] How to fix path for gdal .py scripts in
Anaconda-Windows?
Hi,
I had the same problem, here's my solution :
https://gi
ra: gdal-dev@lists.osgeo.org<mailto:gdal-dev@lists.osgeo.org>
mailto:gdal-dev@lists.osgeo.org>>
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
activate the
> default app instead of the activated python =/
> Thanks!
>
> --
> *De:* gdal-dev em nome de Even Rouault
>
> *Enviado:* quarta-feira, 12 de janeiro de 2022 16:09
> *Para:* gdal-dev@lists.osgeo.org
> *Assunto:* Re: [gdal-dev] How to fix p
o 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 :
## Expecte
## 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
