Design software architecture for OGC API Maps

[j08lue]

OGC API Maps is the successor to good old WMS and on the roadmap for implementation in EOEPCA 2.0 data access services.

Its target behaviour is very similar to OGC API Tiles, except that clients request a bounding box instead of tile matrix coordinates. As such, it shares a lot of backend logic with TiTiler, too.

This ticket is to explore how we can provide OGC API Maps on top of TiTiler and/or TiTiler-PgSTAC.

Initial considerations were to use pygeoapi to implement the standard-compliant API and use TiTiler-PgSTAC as a provider.

Note on demoing / validation

OGC API Maps has a few clients already: https://github.com/opengeospatial/ogcapi-maps/blob/master/implementations.adoc, among others for Leaflet, which could be used in a demo of the capabilities.

Acceptance criteria

• Reviewed different viable options
• Documented final architecture design
• Planned implementation