https://stactools.readthedocs.io/en/stable/api.html#stactools.core.utils.raster_footprint.RasterFootprint.footprint
currently our "footprints" are actually bounding boxes which I am uncertain whether we are reading from metadata or calculating with our stac-item-create script in https://github.com/NewGraphEnvironment/stac_dem_bc/blob/main/stac_create_item.qmd
we actually would prefer to exclude the nodata values
this actually does not matter in QGIS currently though as it appears to be using "bounding boxes" as the "footprint" (vs the "geometry")
tested by altering the geometry of a couple of json manually using above function (takes almost a minute per raster with code in the file linked here!!!)
Changing the "geometry" did not change the "footprint" in QGIS (yet).
this is actually a diff area but you get the idea
doesn't matter if we update the native crs properties either...
If the cogs have overviews it would make getting the footprints remotely much faster
https://stactools.readthedocs.io/en/stable/api.html#stactools.core.utils.raster_footprint.RasterFootprint.footprint
currently our "footprints" are actually bounding boxes which I am uncertain whether we are reading from metadata or calculating with our
stac-item-createscript in https://github.com/NewGraphEnvironment/stac_dem_bc/blob/main/stac_create_item.qmdwe actually would prefer to exclude the nodata values
this actually does not matter in QGIS currently though as it appears to be using "bounding boxes" as the "footprint" (vs the "geometry")
tested by altering the geometry of a couple of json manually using above function (takes almost a minute per raster with code in the file linked here!!!)
Changing the "geometry" did not change the "footprint" in QGIS (yet).
this is actually a diff area but you get the idea
doesn't matter if we update the native crs properties either...
If the cogs have overviews it would make getting the footprints remotely much faster