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

[Daniel Evans]

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 taking the values for those
and dropping them into the `proj:...` fields, which I've done before)

Cheers,
Daniel


On Wed, 11 Sept 2024 at 15:21, Michael Smith via gdal-dev <
gdal-dev at lists.osgeo.org> wrote:

> Thanks for the clarification!
>
>
>
> Mike
>
>
>
>
>
> --
>
> Michael Smith
>
> Remote Sensing/GIS Center
>
> US Army Corps of Engineers
>
>
>
>
>
> *From: *Even Rouault <even.rouault at spatialys.com>
> *Date: *Wednesday, September 11, 2024 at 9:19 AM
> *To: *Michael Smith <michael.smith.erdc at gmail.com>, <
> gdal-dev at lists.osgeo.org>
> *Subject: *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/projection/?tab=readme-ov-file#projbbox:
> "Bounding box of the assets represented by this Item in the asset data CRS.
> Specified as 4 or 6 coordinates based on the CRS defined in the proj:code,
> proj:projjson or proj:wkt2 fields. [...]"
>
>
>
> --
>
> http://www.spatialys.com
>
> My software is free, but my time generally not.
>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/gdal-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20240911/7bda3c42/attachment.htm>