OGC API - Features overview

Requires: the discovery endpoints are anonymous, but listing collections and reading features needs an API key, and OGC access is a Team / Enterprise plan capability.

The OGC API root

Topolab implements OGC API - Features Part 1: Core, a standard HTTP interface that serves geospatial features as GeoJSON, rooted at https://api.topolab.nl/v1/ogc. Because the contract is standardized, any OGC-compatible client can discover everything it needs at runtime and present Topolab datasets as live layers.

https://api.topolab.nl/v1/ogc

Three discovery endpoints are anonymous (no key): the landing page (/ogc), the conformance declaration (/ogc/conformance), and the OpenAPI document (/ogc/api). Everything beyond discovery needs a key, and OGC access is a Team / Enterprise plan capability.

List collections

A collection is a Topolab dataset exposed as features; each collection's id is the dataset table, so the same data you reach over REST is reachable here. Listing returns each collection's id, title, spatial extent, and links to its items.

curl -H "X-API-Key: tlb_prod_..." \
  "https://api.topolab.nl/v1/ogc/collections"

Coordinates are WGS84

The extent.spatial.bbox and all feature geometry are WGS84 (EPSG:4326), ordered [minLon, minLat, maxLon, maxLat] — the OGC declares this as CRS84, longitude-first, matching GeoJSON. Follow a collection's items link to read its features.