Feature requests for OGC GDC

[clausmichele]

I put here some possible improvements that could be useful to better support OGC GDC API:

For GET /coverage

• [ ] Support subset: currently the bbox + datetime selection is reflected in the bbox + datetime parameters. Allow to choose if the user wants to use the subset parameter instead, with the same content. datetime=loTime/hiTime&bbox=loLon,loLat,hiLon,hiLat becomes subset=Lat(loLat:hiLat),Lon(loLon:hiLon),time(["loTime":"hiTime"]) maybe a switch to select if using subset or bbox + datetime?
• [x] Support f parameter to select the requested file format.
• [x] Optionally support other possibly useful parameters like scale, crs etc. https://m-mohr.github.io/geodatacube-api/#tag/OGC-API-Coverages/operation/describe-coverage

[m-mohr]

Support subset: currently the bbox + datetime selection is reflected in the bbox + datetime parameters. Allow to choose if the user wants to use the subset parameter instead, with the same content. datetime=loTime/hiTime&bbox=loLon,loLat,hiLon,hiLat becomes subset=Lat(loLat:hiLat),Lon(loLon:hiLon),time(["loTime":"hiTime"]) maybe a switch to select if using subset or bbox + datetime?

What's the advantage we gain? Looks like the same to me. Generally, subset seems impossible to implement in a general matter as the domainsets are not described well enough by the Coverage API. I can't detect which axis is spatial (neither do I know whether it is x or y), which axis is temporal etc.

Support f parameter to select the requested file format.

Is already supported. You need to specify mutliple coverage links with different media types to enable it. The href needs to include the f parameter. It then allows to select from them.

Optionally support other possibly useful parameters like scale, crs etc. https://m-mohr.github.io/geodatacube-api/#tag/OGC-API-Coverages/operation/describe-coverage

Good idea, but here as well. Some of them are not discoverable, so from a UI perspective it's not clear where to get the allowed values from... crs can probably be read from the crs property (do you expose that?), scale may also work with the corresponding metadata, but properties I'm not sure how that could be made available in a user-friendly way.

• scale-factor could be supported. Not sure about allowed values though
• crs has just been implemented
• subset: see above
• bbox-crs, subset-crs, properties, scale-axes, scale-size are currently not planned

[m-mohr]

CRS is available:

Scale factor is also available.