PDOK Geoservices Wrapper 🇳🇱

Welcome to the EXPERIMENTAL wrapper for Dutch national geoservices from PDOK (Publieke Dienstverlening Op de Kaart). The wrapper turns PDOK's WMS/WFS services and the Locatieserver into Linked Data: every feature gets a dereferenceable URI with GeoJSON(-LD), RDF/XML, and Turtle representations, queryable via SPARQL.

Start here

• Interactive map for the Netherlands — pan the map, pick a WMS background, load WFS features by bounding box or ID, search the Locatieserver, and follow the RDF links from the feature panel.
• Frequently Asked Questions — what the wrapper does (bbox format, WMS image size, rate limits).

Object identifiers

Every object with a stable national registry key has a content-negotiated name /id/{type}/{key} — browsers get an HTML view with a map, API clients get GeoJSON-LD/Turtle/RDF-XML/GML (Accept header or .json/.ttl/.rdf/.nt/.gml suffix). Types: pand, ligplaats, standplaats, verblijfsobject, woonplaats (BAG identificatie), perceel (kadastraal lokaal ID), gemeente, wijk, buurt (CBS codes).

• id/pand/0363100012066258 · Turtle — pand, Amsterdam (built 1883)
• id/verblijfsobject/0599010000012752 — verblijfsobject (dwelling), Rotterdam
• id/ligplaats/0363020000818150 — ligplaats (houseboat mooring), Amsterdam
• id/standplaats/0363030011957689 — standplaats, Amsterdam
• id/woonplaats/3594 — woonplaats, Amsterdam
• id/perceel/11440066370000 — perceel (cadastral parcel), Amsterdam
• id/gemeente/GM0363 · Turtle — gemeente, Amsterdam
• id/wijk/WK0363AG — wijk, Grachtengordel-Zuid
• id/buurt/BU0363AG04 — buurt, Spiegelbuurt

One building, four registries

An 1883 house at Vondelpark-Oost, Amsterdam, as it appears in each source this wrapper covers — same building, different registry, different key:

• id/pand/0363100012066258 — BAG, the legal/administrative record (the authoritative building registration)
• features?collection=pand&bbox=… — BGT, the topographic footprint: a separately surveyed geometry that carries its own bag_pnd attribute back to this BAG identificatie
• id/perceel/11550033370000 — Kadastrale kaart, the parcel the building stands on
• id/buurt/BU0363KD01 · id/gemeente/GM0363 — CBS wijken en buurten, the statistical buurt/gemeente it falls in

Vondelpark splits a neighbourhood in two

That same house sits a few steps from the edge of Vondelpark, Amsterdam's best-known city park — and the park is large enough that CBS treats it as a boundary, not a place: it sits between two separately coded buurten rather than inside either one:

• id/buurt/BU0363KD01 — buurt, Vondelpark-Oost (our house's side, east of the park)
• id/buurt/BU0363KC01 — buurt, Vondelpark-West, the other side
• features?collection=begroeidterreindeel&bbox=… — BGT vegetation cover inside the park itself, the two buurten's shared border (no single "Vondelpark" object exists in any of these registries — it is only ever the sum of its BGT parcels)

Buildings and addresses (BAG WFS)

Every /wfs response is available as GeoJSON-LD (default), or Turtle/RDF-XML/GML via suffix (.ttl/.rdf/.gml) or Accept: header — the links below are all GeoJSON-LD.

• wfs?id=pand.3b6d26fa-… — a building (pand) in Amsterdam, by ID
• wfs?id=verblijfsobject.362af314-… — a dwelling (verblijfsobject) in Rotterdam, by ID
• wfs?typenames=bag:pand&bbox=… — all buildings in a bounding box (Amsterdam centre)
• wfs/describe?s=…bag… — feature types and properties of the BAG WFS

Cadastral parcels (Kadastralekaart WFS)

• wfs?typenames=kadastralekaart:Perceel&bbox=… — parcels in a bounding box
• wfs/describe?s=…kadastralekaart… — feature types of the Kadastralekaart WFS

Statistical areas (CBS wijken en buurten WFS)

• wfs?typenames=wijkenbuurten:buurten&bbox=… — neighbourhoods (buurten) in a bounding box
• wfs/describe?s=…wijkenbuurten… — feature types of the wijkenbuurten WFS

Large-scale topography (BGT, OGC API Features)

The BGT has no WFS upstream; /features proxies PDOK's OGC API Features endpoint (cursor paging followed server-side). Same formats as /wfs: GeoJSON-LD (default), or Turtle/RDF-XML/N-Triples via suffix or Accept header. Add datetime=… to exclude terminated (historical) objects.

• features?collection=wegdeel&bbox=… — road segments (wegdeel) in a bounding box (Amsterdam centre)
• features?collection=pand&bbox=… — buildings (pand)
• features?collection=waterdeel&bbox=… — water (waterdeel)
• features?collection=begroeidterreindeel&bbox=… — vegetation (begroeidterreindeel)
• https://api.pdok.nl/lv/bgt/ogc/v1/collections — all 49 BGT collections at the upstream API

Place search (PDOK Locatieserver)

• pdok?q=Amsterdam&type=woonplaats — search by name (woonplaats)
• pdok?q=Utrecht&type=gemeente — search by name (gemeente)
• pdok?q=Binnenhof&type=weg — search by name (weg)
• pdok?id=wpl-… — lookup by Locatieserver ID, Amsterdam (with owl:sameAs to the canonical BAG URI)

Map images (WMS)

• wms.png?layer=gebouw&bbox=… — TOP10NL buildings over Amsterdam centre (append ?legend for the legend graphic)

Map tiles (Web-Mercator XYZ)

Any registered WMS layer is also addressable as a standard 256×256 Web-Mercator z/x/y tile — the same grid Leaflet/OSM use, so a cell id is comparable across the linked-* family. The same URI content-negotiates a Turtle/RDF description of the tile's footprint and ground resolution (&f=ttl or an RDF Accept).

• tile?s=…top10nl…&layer=gebouw&z=14&x=8414&y=5384 · Turtle — TOP10NL buildings over Amsterdam centre (this layer is registered in EPSG:4326, so the tile is reprojected — see X-Tile-Reprojection on the response)
• tile?s=…luchtfotorgb…&layer=Actueel_orthoHR&z=15&x=16829&y=10769 — current high-resolution aerial imagery over Amsterdam centre

Status

Every configured WFS/WMS/OGC API Features source, region-grouped, with live reachability and the same capability detail as their own describe/collections views — JSON, HTML, or RDF (Turtle/RDF-XML/N-Triples) via suffix or Accept header.

• status.html · JSON · Turtle — every upstream source and its current reachability

Query

• Query page — DESCRIBE queries with map display
• SPARQL endpoint form — SELECT/ASK/CONSTRUCT/DESCRIBE over graphs loaded with FROM </wfs?…>, GeoSPARQL functions included

Vocabularies

• vocab/bag.rdf — BAG, generated RDF vocabulary backing the property/type URIs
• vocab/kadastralekaart.rdf — Kadastralekaart, generated RDF vocabulary backing the property/type URIs
• vocab/wijkenbuurten.rdf — Wijken en buurten, generated RDF vocabulary backing the property/type URIs
• vocab/bgt.rdf — BGT, generated RDF vocabulary backing the property/type URIs