Re: [gdal-dev] GDAL 3.8.3 RC2 is available, and motion to approve it (Re: GDAL 3.8.3 RC1 is available, and motion to approve it)

2024-01-03 Thread Rahkonen Jukka via gdal-dev
+1 -Jukka Rahkonen- -Alkuperäinen viesti- Lähettäjä: gdal-dev Puolesta Even Rouault via gdal-dev Lähetetty: keskiviikko 3. tammikuuta 2024 22.46 Vastaanottaja: gdal-dev@lists.osgeo.org Aihe: [gdal-dev] GDAL 3.8.3 RC2 is available, and motion to approve it (Re: GDAL 3.8.3 RC1 is availa

[gdal-dev] COG via HTTP POST

2024-01-03 Thread Korver, Mark via gdal-dev
Hi Javier, A POST url to COG content only makes sense if the intent is to support full download of the file. POST is normally for adding/updating data. I took a quick look and yes no way to directly access the COGs other than use the search UI and get a list. We see this many times, the good ne

Re: [gdal-dev] GDAL 3.8.3 RC2 is available, and motion to approve it (Re: GDAL 3.8.3 RC1 is available, and motion to approve it)

2024-01-03 Thread Javier Jimenez Shaw via gdal-dev
+1 Javier On Wed, 3 Jan 2024, 21:46 Even Rouault via gdal-dev, < gdal-dev@lists.osgeo.org> wrote: > Hi, > > I've issued a 2nd release candidate for 3.8.3 with the following > additional fixes: > - ogr2ogr: do not use ArrowArray interface if -clipsrc, -clipdst, -gcp > or wrapdateline are specified

[gdal-dev] GDAL 3.8.3 RC2 is available, and motion to approve it (Re: GDAL 3.8.3 RC1 is available, and motion to approve it)

2024-01-03 Thread Even Rouault via gdal-dev
Hi, I've issued a 2nd release candidate for 3.8.3 with the following additional fixes: - ogr2ogr: do not use ArrowArray interface if -clipsrc, -clipdst, -gcp or wrapdateline are specified (#9013) - GPKG driver: disable by default multi-threaded ArrowArray interface. Make it opt-in with the OGR

Re: [gdal-dev] Error when importing GeoPackage into PostgreSQL database ("Worker thread task has not expected m_iStartShapeId value")

2024-01-03 Thread Even Rouault via gdal-dev
OK, I'm submitting https://github.com/OSGeo/gdal/pull/9018 to disable the multi-threaded mode by default, as I want to have reliable working in the 3.8.3 release ASAP. But I'm still interested in having that issue diagnose, to potentially re-enable multi-threading later. In 3.8.3, multi-threadi