OGC API - Maps

[vincentsarago]

OGC API - MAPS

The OGC API - Maps draft specification describes an API that can serve spatially referenced and dynamically rendered electronic maps. The specification describes the discovery and query operations of an API that provides access to electronic maps in a manner independent of the underlying data store. The query operations allow dynamically rendered maps to be retrieved from the underlying data store based upon simple selection criteria, defined by the client.

https://ogcapi.ogc.org/maps/

https://docs.ogc.org/DRAFTS/20-058.html

Same as OGC Tiles and Coverage, we won't support the spec to the letter but there might be endpoints we can create in an extension.

I need to look a bit more but to me the specs looks like the IIIF spec which we played with in https://github.com/developmentseed/titiler-image

[jerstlouis]

@vincentsarago The standard is very modular and the requirements for the "Core" class are very few (.../map returns a map with a Content-Bbox: header, and Content-Crs: if not in OGC CRS84), so it should be easy to conform to "Core".

Then you could gradually implement the additional requirement classes you care about (e.g, adding support for query parameters like bbox= and width=/height=).