Filter features with a bounding box

Requires: an API key sent in the X-API-Key header. OGC access is a Team / Enterprise plan capability.

Filter by bounding box

The bbox parameter restricts results to a box in WGS84, ordered minLon,minLat,maxLon,maxLat — you read it longitude-then-latitude, matching GeoJSON. Only features whose geometry falls inside the box are returned. This example covers roughly central Amsterdam.

curl -H "X-API-Key: tlb_prod_..." \
  "https://api.topolab.nl/v1/ogc/collections/nl-domino-poi/items?bbox=4.85,52.34,4.95,52.40"

Filter by attribute

Restrict by category, city, or country, each matching the feature property of the same name. Filters combine with logical AND — a feature must satisfy every parameter you supply — and numberMatched in the response reflects the filtered total.

curl -H "X-API-Key: tlb_prod_..." \
  "https://api.topolab.nl/v1/ogc/collections/nl-domino-poi/items?city=Rotterdam&country=nl"

Combine filters and page

Filters and paging compose. Add limit (default 100, max 1000) and offset to walk the filtered set, or simply follow the response's next link. This pulls the second page of restaurants inside the Amsterdam box.

curl -H "X-API-Key: tlb_prod_..." \
  "https://api.topolab.nl/v1/ogc/collections/nl-domino-poi/items?bbox=4.85,52.34,4.95,52.40&category=restaurant&limit=100&offset=100"

Tip · GIS clients do this for you

QGIS, ArcGIS, and other OGC clients pointed at https://api.topolab.nl/v1/ogc issue these same item requests under the hood — bbox is driven by the map extent and attribute filters map to the client's filter UI.