[gdal-dev] unsubcribe

___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev

Re: [gdal-dev] [EXTERNAL] Re: How to determine which creation options are supported by a driver?

Thanks everyone, and congratulations on the 3.8 release. Best, Jesse From: Rahkonen Jukka Date: Thursday, November 30, 2023 at 3:32 PM To: "Meyer, Jesse R. (GSFC-618.0)[SCIENCE SYSTEMS AND APPLICATIONS INC]" , Even Rouault via gdal-dev Subject: [EXTERNAL] Re: How to determine which creation

Re: [gdal-dev] [External] : Re: GDAL driver Open() calls

ok, that should be fixed per https://github.com/OSGeo/gdal/pull/8885 (and factorization of similar code of gdal_translate_lib.cpp and gdaldriver.cpp) Le 30/11/2023 à 20:59, Fengting Chen a écrit : Hi Even, Here is what found out from debugging: There are two Open() calls. Your fix skipped

Re: [gdal-dev] How to determine which creation options are supported by a driver?

Le 30/11/2023 à 21:19, Meyer, Jesse R. (GSFC-618.0)[SCIENCE SYSTEMS AND APPLICATIONS INC] via gdal-dev a écrit : Hi, I have gdal 3.8.1 installed via Brew which includes liblerc and zstd as part of their formulae, so I assumed I could use the creation options “COMPRESS=LERC_ZSTD” and

Re: [gdal-dev] How to determine which creation options are supported by a driver?

Hi, Run ”gdalinfo –format GTiff”. For me it prints: NONE LZW PACKBITS JPEG CCITTRLE CCITTFAX3 CCITTFAX4 DEFLATE ZSTD So my GDAL build does not support LERC. -Jukka Rahkonen- Lähettäjä: gdal-dev Puolesta Meyer, Jesse R. (GSFC-618.0)[SCIENCE SYSTEMS AND

[gdal-dev] How to determine which creation options are supported by a driver?

Hi, I have gdal 3.8.1 installed via Brew which includes liblerc and zstd as part of their formulae, so I assumed I could use the creation options “COMPRESS=LERC_ZSTD” and “MAX_Z_ERROR=x” as documented on the GTIFF page when creating a new gtif image. But when I do GDAL states: “Warning 6:

Re: [gdal-dev] [External] : Re: GDAL driver Open() calls

Hi Even, Here is what found out from debugging: There are two Open() calls. Your fix skipped one. Here is the stack trace of the second one: [cid:image001.png@01DA239D.5F51E090] Thanks! From: Even Rouault Date: Thursday, November 30, 2023 at 8:40 AM Le 30/11/2023 à 04:47, Fengting Chen a

Re: [gdal-dev] "RFC 98: Build requirements for GDAL 3.9" available for review

No further comments on this ? If not, I'll submit it to vote tomorrow. Le 24/11/2023 à 12:15, Even Rouault via gdal-dev a écrit : Hi, Please find "RFC 98: Build requirements for GDAL 3.9" in https://github.com/OSGeo/gdal/pull/8802 for review & comments Summary: The document updates RFC68

[gdal-dev] GDAL 3.8.1 is released

Hi, On behalf of the GDAL/OGR development team, I am pleased to announce the release of the GDAL/OGR 3.8.1 bug fix version. All users that had already updated to 3.8.0 are strongly encouraged to update to 3.8.1, which addresses a few 3.8.0 specific regressions (particularly for ogr2ogr

Re: [gdal-dev] GDAL 3.8.1RC3 is available & motion to approve it

Motion passed with +1 from PSC members JukkaR, HowardB, JavierJS, SeanG and me. Le 28/11/2023 à 16:32, Even Rouault via gdal-dev a écrit : Hi, well, another annoying 3.8.0 regression related to ogr2ogr GPKG -> Shapefile when field names are longer than 10 characters (ah Shapefile!!!) popped

Re: [gdal-dev] [External] : Re: GDAL driver Open() calls

Le 30/11/2023 à 04:47, Fengting Chen a écrit : This doesn’t seem to fix the problem. How do I print out the stack trace in the driver? This is not something the driver can do. You have to use the interactive debugger of your dev environment, attach it to your gdal_translate command, set a

Re: [gdal-dev] How do GCP's in a VRT file work?

Joe Lovick via gdal-dev writes: >        What is the recommended processing paradigm for slightly > off-nadir imagery where their is a need for a full [3x3] matrix > mapping to take it to a consistent projection? ie the images have at a > minimum perspective effects. > >     the reason i ask, is