Behaviour if CRS is EPSG:4326

[m-mohr]

So if the CRS is set to EPSG:4326, do we use the bbox of the item and do not provide proj:bbox specifically? It would deduplicate quite a bit in Sentinel-3 for example.

[gadomski]

Yes, I find that proj:bbox isn't used too much in the wild anyways, and if it's duplicating makes sense to me to omit it.

@m-mohr informs me that it's used by GDAL and odc-stac which makes it a bit more complicated, but I do think duplicating the info down to proj:bbox is less than ideal.

[m-mohr]

Thanks, indeed from the best practices:

For example, the GDAL implementation requires the following fields:
proj:wkt2 or proj:projjson (one of them filled with non-null values)
Any of the following:

• proj:transform and proj:shape
• proj:transform and proj:bbox
• proj:bbox and proj:shape

We usually provide bbox, shape and epsg code in our catalog, so I was wondering whether we can usually skip proj:bbox in favor of bbox and ask those tools to consider implementing it.