OGC API

These routes expose MapServer and MapCache-backed geospatial services for single datasets and multi-dataset compositions.

WMS

Method	Path	Purpose	Notes
GET	/wms/{dataset_id}	single-dataset WMS dispatch	may use MapCache first for GetMap when enabled
GET	/wms/multi	multi-dataset WMS via query parameters	builds one combined mapfile
POST	/wms/multi	multi-dataset WMS via request body	useful for larger dataset lists
GET	/mapcache/wms	browser-friendly proxy into MapCache WMS	avoids direct CORS exposure
GET	/mapcache/{dataset_id}	dataset-specific MapCache WMS route	useful when inspecting cache-backed behavior directly

WCS

Method	Path	Purpose
GET	/wcs/{dataset_id}	single-dataset WCS dispatch
GET	/wcs/multi	multi-dataset WCS dispatch
POST	/wcs/multi	multi-dataset WCS dispatch with request body

WFS

Method	Path	Purpose
GET	/wfs/{dataset_id}	expose dataset footprint/features through WFS
GET	/wfs/multi	multi-dataset WFS dispatch via query parameters

Support and Test Routes

Method	Path	Purpose
GET	/mapfiletest	serve a hardcoded test mapfile for client validation
GET	/styles/{dataset_id}/{style_id}.sld	publish an SLD style document for external clients

Operational Notes

• wms_use_mapcache determines whether eligible GetMap requests try MapCache before direct MapServer rendering.
• Native projected requests can be cached when the generated MapCache config includes a matching grid and extent restriction.
• If MapCache rejects a request, the API falls back to direct render rather than returning the cache-layer failure to the client.
• Use Swagger for parameter details, and use Request Flows for the cache-first handoff sequence.