Re: [gdal-dev] Motion: approve RFC 101 "Raster dataset read-only thread-safety"

+1 -Jukka Rahkonen- -Alkuperäinen viesti- Lähettäjä: gdal-dev Puolesta Even Rouault via gdal-dev Lähetetty: keskiviikko 11. syyskuuta 2024 22.27 Vastaanottaja: gdal-dev@lists.osgeo.org Aihe: [gdal-dev] Motion: approve RFC 101 "Raster dataset read-only thread-safety" Hi, I move to app

Re: [gdal-dev] Motion: Renew Even Rouault GDAL Maintainer Contract

+1 -Jukka Rahkonen- -Alkuperäinen viesti- Lähettäjä: gdal-dev Puolesta Howard Butler via gdal-dev Lähetetty: torstai 12. syyskuuta 2024 5.24 Vastaanottaja: gdal dev Aihe: [gdal-dev] Motion: Renew Even Rouault GDAL Maintainer Contract PSC, I am motioning to renew Even's maintainer con

Re: [gdal-dev] Motion: Renew Even Rouault GDAL Maintainer Contract

+1 Javier On Thu, 12 Sept 2024, 06:31 Kurt Schwehr via gdal-dev, < gdal-dev@lists.osgeo.org> wrote: > +1 KurtS > > On Wed, Sep 11, 2024 at 7:24 PM Howard Butler via gdal-dev < > gdal-dev@lists.osgeo.org> wrote: > >> PSC, >> >> I am motioning to renew Even's maintainer contract through the GDAL >>

Re: [gdal-dev] Motion: Renew Even Rouault GDAL Maintainer Contract

+1 KurtS On Wed, Sep 11, 2024 at 7:24 PM Howard Butler via gdal-dev < gdal-dev@lists.osgeo.org> wrote: > PSC, > > I am motioning to renew Even's maintainer contract through the GDAL > Sponsorship Program that is hosted by NumFOCUS for another year. > > /me starts with a +1 > > Howard > __

Re: [gdal-dev] Motion: Renew Even Rouault GDAL Maintainer Contract

Only a year? Someone chain him to his desk already. You can't be too cautious. ;) Scott On 9/11/24 19:23, Howard Butler via gdal-dev wrote: PSC, I am motioning to renew Even's maintainer contract through the GDAL Sponsorship Program that is hosted by NumFOCUS for another year. /me starts wi

Re: [gdal-dev] Motion: Renew Even Rouault GDAL Maintainer Contract

+1! Daniel On 2024-09-11 22:23, Howard Butler via gdal-dev wrote: PSC, I am motioning to renew Even's maintainer contract through the GDAL Sponsorship Program that is hosted by NumFOCUS for another year. /me starts with a +1 Howard ___ gdal-dev ma

[gdal-dev] Motion: Renew Even Rouault GDAL Maintainer Contract

PSC, I am motioning to renew Even's maintainer contract through the GDAL Sponsorship Program that is hosted by NumFOCUS for another year. /me starts with a +1 Howard ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/li

Re: [gdal-dev] Ignore content-length in vsicurl?

The server seems to have been fixed, but on reflection, I won't merge the workaround PR as this is (thanksfully) quite an unusual case. At least the PR is there if someone badly needed to patch their build with such a workaround. Le 10/09/2024 à 17:11, thomas bonfort a écrit : I'm not sure tha

Re: [gdal-dev] Motion: approve RFC 101 "Raster dataset read-only thread-safety"

+1 KurtS On Wed, Sep 11, 2024 at 12:27 PM Even Rouault via gdal-dev < gdal-dev@lists.osgeo.org> wrote: > Hi, > > I move to approve RFC 101 "Raster dataset read-only thread-safety": > https://github.com/OSGeo/gdal/pull/10676 > > Starting with my +1, > > The candidate implementation is available in

Re: [gdal-dev] Extending GDAL Color Interpretation enumeration for infra-red bands (+ band wavelength) ?

Le 03/09/2024 à 19:02, Even Rouault via gdal-dev a écrit : Le 02/09/2024 à 19:07, Javier Jimenez Shaw a écrit : Based on the last email I am not sure if you want to include the CentralWavelenght and FWHM or not. yes, candidate implementation in https://github.com/OSGeo/gdal/pull/10721 Whi

[gdal-dev] Motion: approve RFC 101 "Raster dataset read-only thread-safety"

Hi, I move to approve RFC 101 "Raster dataset read-only thread-safety": https://github.com/OSGeo/gdal/pull/10676 Starting with my +1, The candidate implementation is available in https://github.com/OSGeo/gdal/pull/10746. While fine tuning it, I realized there were subtleties, related to the

Re: [gdal-dev] STACIT driver and iten collections and origin / pixel size

And I'll highlight that the separate `geometry` and `bbox` fields in the STAC item do explicitly have to be projected in WGS84 (as required by the GeoJSON spec): https://github.com/radiantearth/stac-spec/blob/master/item-spec/item-spec.md#geometry (Although I suspect the original mistake was takin

Re: [gdal-dev] STACIT driver and iten collections and origin / pixel size

Thanks for the clarification! Mike -- Michael Smith Remote Sensing/GIS Center US Army Corps of Engineers From: Even Rouault Date: Wednesday, September 11, 2024 at 9:19 AM To: Michael Smith , Subject: Re: [gdal-dev] STACIT driver and iten collections and origin / pixel size

Re: [gdal-dev] STACIT driver and iten collections and origin / pixel size

Le 11/09/2024 à 16:17, Michael Smith a écrit : The proj:bbox is in geodetic. Is that the issue, the bbox needs to be in the projected coords? I have proj:projjson and proj:wkt2 defined but the bbox is geodetic. Per the spec, yes, this is wrong. Cf https://github.com/stac-extensions/proje

Re: [gdal-dev] STACIT driver and iten collections and origin / pixel size

The proj:bbox is in geodetic. Is that the issue, the bbox needs to be in the projected coords? I have proj:projjson and proj:wkt2 defined but the bbox is geodetic. Mike From: Even Rouault Date: Wednesday, September 11, 2024 at 9:11 AM To: Michael Smith , Subject: Re: [gdal-dev] S

Re: [gdal-dev] STACIT driver and iten collections and origin / pixel size

Michael, can you paste the definition of such STAC Json item ?  Guess: "proj:epsg" is present, but "proj:bbox" or "proj:transform" are using WGS84 coordinates ? Even Le 11/09/2024 à 15:59, Michael Smith via gdal-dev a écrit : Using gdal 3.9.2: I’m using pystac to create stac json item col

[gdal-dev] STACIT driver and iten collections and origin / pixel size

Using gdal 3.9.2: I’m using pystac to create stac json item collections. I’m setting the srs of using the projection extension and gdalinfo returns the correct srs that I am setting. gdalinfo STACIT:13459.json Driver: VRT/Virtual Raster Files: /vsicurl/https://noaa-nos-coastal-lidar-pd