Collections

A collection is a Topolab dataset exposed as a set of geospatial features. Each collection's id is the dataset table (for example transport_infrastructure_bushaltes), so the same data you reach over REST as a dataset is reachable here as a collection. For how these terms relate, see Concepts: datasets vs collections.

Unlike the anonymous landing page and conformance endpoints, both /collections and /collections/{collectionId} require an organization API key with the GIS_ACCESS addon, sent in the X-API-Key header. Calling them without a key returns 401 API key is required. See Authentication.

List collections

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

The response lists each collection with its id, title, spatial extent, and links to its items. Only datasets your organization is licensed for appear here.

{
  "links": [
    {
      "rel": "self",
      "type": "application/json",
      "href": "https://api.topolab.nl/v1/ogc/collections"
    }
  ],
  "collections": [
    {
      "id": "transport_infrastructure_bushaltes",
      "title": "Dutch Bus Stops",
      "description": "Bus stop locations across the Netherlands.",
      "extent": {
        "spatial": {
          "bbox": [[3.36, 50.75, 7.23, 53.55]],
          "crs": "http://www.opengis.net/def/crs/OGC/1.3/CRS84"
        }
      },
      "crs": ["http://www.opengis.net/def/crs/OGC/1.3/CRS84"],
      "links": [
        {
          "rel": "items",
          "type": "application/geo+json",
          "title": "Features",
          "href": "https://api.topolab.nl/v1/ogc/collections/transport_infrastructure_bushaltes/items"
        },
        {
          "rel": "self",
          "type": "application/json",
          "href": "https://api.topolab.nl/v1/ogc/collections/transport_infrastructure_bushaltes"
        }
      ]
    }
  ]
}

The extent.spatial.bbox is in WGS84 (EPSG:4326), ordered [minLon, minLat, maxLon, maxLat]. CRS84 is the OGC URI for WGS84 with longitude-first axis order, which matches GeoJSON.

Get a collection

Fetch metadata for a single collection by its collectionId (the dataset table):

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

{
  "id": "transport_infrastructure_bushaltes",
  "title": "Dutch Bus Stops",
  "description": "Bus stop locations across the Netherlands.",
  "extent": {
    "spatial": {
      "bbox": [[3.36, 50.75, 7.23, 53.55]],
      "crs": "http://www.opengis.net/def/crs/OGC/1.3/CRS84"
    }
  },
  "crs": ["http://www.opengis.net/def/crs/OGC/1.3/CRS84"],
  "itemType": "feature",
  "links": [
    {
      "rel": "items",
      "type": "application/geo+json",
      "title": "Features",
      "href": "https://api.topolab.nl/v1/ogc/collections/transport_infrastructure_bushaltes/items"
    },
    {
      "rel": "self",
      "type": "application/json",
      "href": "https://api.topolab.nl/v1/ogc/collections/transport_infrastructure_bushaltes"
    }
  ]
}

Follow the items link to read the features. See Items for paging and bbox and filtering for narrowing results.

Errors

Status	Meaning
401	Missing or invalid API key (API key is required).
403	Key is valid but the organization lacks the GIS_ACCESS addon.
404	Unknown collectionId, or a dataset your organization is not licensed for. The two cases return the same 404.
429	Rate limit exceeded.

Next

• Items, page through a collection's features.
• Single feature, fetch one feature by id.
• Need GIS_ACCESS? Contact us.