[gdal-dev] ogrinfo behaviour with -al and -json options

2024-07-02 Thread Andrea Giudiceandrea via gdal-dev
Hi all, IIUC, the documentation states that with the -al option, ogrinfo should output the info of all layers in a container (e.g. a GPKG file). Anyway, when a layer name is provided in the command line string alongside the -al option, than it looks like the -al option is overridden and not ta

Re: [gdal-dev] Issues specifying PostGIS connection details - possibly related to special characters in passwords?

2024-07-02 Thread Mike Taves via gdal-dev
On Wed, 3 Jul 2024 at 03:36, Robin Wilson via gdal-dev wrote: > Any suggestions welcome, If you routinely access a specific database, a reliable method is to create a .pgpass file: https://www.postgresql.org/docs/current/libpq-pgpass.html This way you never need to provide a password. __

Re: [gdal-dev] Issues specifying PostGIS connection details - possibly related to special characters in passwords?

2024-07-02 Thread Daniel Evans via gdal-dev
I think the trick there is that single quotes make most shells consider a string verbatim - I'd forgotten that part! That's probably the more desirable solution, actually. Cheers, Daniel On Tue, 2 Jul 2024, 17:13 Robin Wilson, wrote: > Hi, > > Hmm, I’m sure I tried escaping it before - but putt

Re: [gdal-dev] Issues specifying PostGIS connection details - possibly related to special characters in passwords?

2024-07-02 Thread Robin Wilson via gdal-dev
Hi, Hmm, I’m sure I tried escaping it before - but putting a \ in front of it fixed it - obviously I didn’t try properly before. Possibly I only tried quoting it in various ways. Thanks for the solution! Now the thing I’m intrigued about is why it was working with the postgresql:// connection

Re: [gdal-dev] Issues specifying PostGIS connection details - possibly related to special characters in passwords?

2024-07-02 Thread Daniel Evans via gdal-dev
Hi Robin, Is this a shell issue, rather than a GDAL one? The dollar sign makes me suspect that a Unix shell is interpreting "robin$42" as "the string 'robin' and the value of variable $42" before it gets into GDAL. My terminal would interpret it as the following: $ echo robin$42 robin and I'd nee

[gdal-dev] Issues specifying PostGIS connection details - possibly related to special characters in passwords?

2024-07-02 Thread Robin Wilson via gdal-dev
Hi, I’m using ogr2ogr to load a GeoPackage file into a PostGIS database. I initially tried using a command like this: ogr2ogr --debug ON -f PostgreSQL PG:"host= user= password=robin$42 dbname=data sslmode=require" file.gpkg -nln table_name However, this doesn’t work, and I always get an error:

Re: [gdal-dev] GDAL 3.9: How to pass negative flag values to GDALArgumentParser?

2024-07-02 Thread Even Rouault via gdal-dev
Hi Craig, this is indeed a regression. I'm on it Even Le 02/07/2024 à 06:39, Craig de Stigter via gdal-dev a écrit : A colleague has noticed a workaround: prefix the argument with a space: $ gdalwarp '-dstnodata' ' -inf' ... On Tue, 2 Jul 2024 at 16:04, Craig de Stigter wrote: While

Re: [gdal-dev] Fwd: WMTS huge difference in performance - cache issue

2024-07-02 Thread Michał Kowalczuk via gdal-dev
Great to hear:-) Thank you! Michał pon., 1 lip 2024 o 19:13 Even Rouault napisał(a): > Michał, > Le 01/07/2024 à 18:49, Michał Kowalczuk via gdal-dev a écrit : > > Did my email reached gdal mailing list? > > yes, it did. I just had a look > > There's indeed an issue in the WMTS driver which I'v