OGC API report

OGC API report

Major changes

All the old API will be rewritten, major changes:

• Based on OpenAPI
• Return (Geo)JSON or images (or binary like pbf)
• Have a Browsable API (Landing pages)

New naming:

• WMS -> OGC API Map
• WFS -> OGC API Feature
• WMTS -> OGC API Tiles
• ...

Status:

OGC API Map: Draft OGC API Feature:

• Part 1: Accepted
• Part 2 (CRS): Accepted
• Part 3 (Filtering): Draft
• Part 4: (CURD): Draft OGC API Tiles: Accepted OGC API Common:
• Part 1: Accepted
• Part 2 (Collections): Draft OGC API Styles: Draft OGC API Precesses: Accepted

Regressions:

• It's not possible to add extra parameters like the Map (especially because of the landing page)
• The returned GeoJSON doesn't contain the related layer name.
• The returned GeoJSON doesn't contain the srs event if it's possible to get a geometry in a local srs.
• It's not possible to do a query on OGC API Feature multiple layers.
• It's not possible to do a query on OGC API Map on multiple layers (it should be verified, it can be a performance issue).

Implementation changes:

• On QGIS server we have URL prefix with a project id (it's like a hash, but it does look to change when we modify the project). This mean that in GeoMapFish we take care on that in the mapserv_proxy -Y change the OGC server structure.

Echosystem status

Required and Optional changes in GeoMapFish