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

[Michael Smith]

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-pds.s3.us-east-1.amazonaws.com/dem/WA_King_DEM_2016_8589/./kingcounty_delivery4_block2_be.tif

       /vsicurl/https://noaa-nos-coastal-lidar-pds.s3.us-east-1.amazonaws.com/dem/WA_King_DEM_2016_8589/./kingcounty_delivery4_block1_be.tif

Size is 74182, 79467

Coordinate System is:

COMPOUNDCRS["NAD83(HARN) / Washington North (ftUS) + NAVD88 height (ftUS)",

    PROJCRS["NAD83(HARN) / Washington North (ftUS)",

 

 

But when I look at the origin / pixel size / bounding box, its in geodetic coordinates. Is this how it should be reported? I was also doing some conversions from stac to vrt to support arcpro users and the vrt then inherits the bbox/pixel size/origin of the geodetic values from stac. Trying to see how I can get these values in actual projected coordinates.

 

Mike

 

 

-- 

Michael Smith

Remote Sensing/GIS Center

US Army Corps of Engineers

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20240911/8af75f19/attachment.htm>