b.v. https://api.pdok.nl/kadaster/bgt/ogc/v1/
zie conformance class https://api.pdok.nl/kadaster/bgt/ogc/v1/conformance
https://api.pdok.nl/kadaster/bgt/ogc/v1/collections/spoor

basic-spatial-functions
basic-spatial-functions
└── S_INTERSECTS (punt en bbox)
basic-spatial-functions-plus
└── S_INTERSECTS
+ extra geometrietypen
spatial-functions
├── S_INTERSECTS
├── S_CONTAINS
├── S_CROSSES
├── S_DISJOINT
├── S_EQUALS
├── S_OVERLAPS
├── S_TOUCHES
└── S_WITHIN
https://api.pdok.nl/kadaster/bgt/ogc/v1/collections/spoor/schema
Zonder datum
Met datum
Allen-relaties voor tijdsintervallen kunnen worden uitgedrukt met CQL2-operatoren.
Voorbeelden: before → T_BEFORE, after → T_AFTER, equals → T_EQUALS en overlaps → T_INTERSECTS
SELECT *
FROM read_parquet('provinciegebied_parquet_0')
where naam like '%Holland'
https://app.pdok.nl/cloud-demo-viewer/
Demo run: https://app.pdok.nl/cloud-demo-viewer/demo/
SELECT spoor.* FROM read_parquet(‘spoor_parquet_1’) spoor WHERE ST_Intersects( spoor.geom, ST_GeomFromText(‘POLYGON((82186 454735, 82329 455235, 82663 455446, 82997 455235, 83140 454735, 82997 454235, 82663 454024, 82329 454235, 82186 454735))’) ) AND spoor.functie = ‘trein’
### Combinatie maken met andere datasets
#### recept volg het spoor
```sql
SELECT spoor.*
FROM read_parquet('spoor_parquet_1') spoor
JOIN read_parquet('gemeentegebied_parquet_2') gemeente
ON ST_Intersects(
spoor.geom,
gemeente.geometry
)
WHERE gemeente.naam = '''s-Gravenhage'
AND spoor.functie = 'trein'
AND spoor.eind_registratie IS NULL
zie ook Leermodule: https://pdok.github.io/leermodule-location-api/
JSON: https://api.pdok.nl/kadaster/location-api/v1/api?f=json
HTML: https://api.pdok.nl/kadaster/location-api/v1/api?f=html
Alle collecties:
https://api.pdok.nl/kadaster/location-api/v1/collections
Specifieke collection (generiek endpoint):
https://api.pdok.nl/kadaster/location-api/v1/collections/{collectionId}
Voorbeelden:
Collectie selectie is relevant:
https://api.pdok.nl/kadaster/location-api/v1/search?q=damrak (minimal een collectie met versie verplicht)rond nederland:
rond centrum nederland:
| Dataset / Product | Tiles‑endpoint | Tile‑type |
|---|---|---|
| BGT – Basisregistratie Grootschalige Topografie | https://api.pdok.nl/lv/bgt/ogc/v1/tiles | Vector Tiles |
| BAG – Basisregistratie Adressen en Gebouwen | https://api.pdok.nl/kadaster/bag/ogc/v2/tiles | Vector Tiles |
| BRK – Bestuurlijke Gebieden | https://api.pdok.nl/kadaster/brk-bestuurlijke-gebieden/ogc/v1/tiles | Vector Tiles |
| BRK – Kadastrale Kaart | https://api.pdok.nl/kadaster/brk-kadastrale-kaart/ogc/v1/tiles | Vector Tiles |
| BRT – TOP10NL | https://api.pdok.nl/brt/top10nl/ogc/v1/tiles | Vector Tiles |
| BRT – Achtergrondkaart | https://api.pdok.nl/kadaster/brt-achtergrondkaart/ogc/v1/tiles | Vector Tiles |
| Category | Description | Examples |
|---|---|---|
| OGC Services | XML-based standards using HTTP for remote procedure calls | WMS, WFS, CSW |
| OGC APIs | RESTful, resource-centric APIs using modern web practices, building on legacy OGC services | OGC API – Features, Tiles, Records |
| Summary | Regulation (EU) 1089/2010 Data model | Regulation (EC) 976/2009 Service model |
|---|---|---|
| Full Title | Interoperability of spatial datasets and services | Network services for spatial data |
| Focus Area | Data content and structure | Access and delivery of data via services |
| Purpose | Ensure harmonized data models across Member States | Define how services like WMS, WFS, and discovery work |
| Applies To | Spatial datasets (Annex I, II, III themes) | Discovery, view, download, transformation, invoke services |
| Examples | How a cadastral parcel or road is modeled | How a WMS responds to a GetMap request |
| Technical Scope | Data schemas, code lists, feature types | Service interfaces, protocols, metadata accessibility standards |
| Target Audience | Data producers, harmonization experts | IT service providers, geoportal developers |
| INSPIRE Annex Coverage | Annex I, II, III themes | All services supporting INSPIRE datasets |
| Legal Basis | Commission Regulation (EU) No. 1089/2010 | Commission Regulation (EC) No. 976/2009 |
Technical Guidance for the implementation of INSPIRE Discovery Services) Source:
Harvesters CSW:
Non Inspire Dutch API harvest:
The Aanmerkingsregister is a Dutch national register that tracks dataset designations related to various European data obligations, primarily:
Definition CP:
Cadastral parcels Netherlands (European Data Portal search)

Conformance to INSPIRE Legislation
| Field | Value | |
|---|---|---|
| Specification | Commission Regulation (EC) No. 976/2009 – implementing Directive 2007/2/EC as regards network services | |
| Specification | Technical Guidance for INSPIRE Download Services | |
| Explanation | Conformant with the technical specification, validated using the ETF Validator for INSPIRE view and download services version 1.4.1 |
| Field | Value |
|---|---|
| Specification | Commission Regulation (EU) No. 1089/2010 https://eur-lex.europa.eu/eli/reg/2010/1089/oj/eng – implementing Directive 2007/2/EC on interoperability of spatial datasets and services |
| Specification | Interoperable conformance class |
| Explanation | The service complies with the requirements of the interoperable conformance class - |
| Specification | WFS 2.0 conformance class |
| Explanation | The service complies with the requirements of the WFS 2.0 conformance class |

Conformance to INSPIRE
| Conformance Class | Description | Abstract test | ||
|---|---|---|---|---|
| Metadata – Baseline | Metadata for datasets and dataset series | Metadata (TG) | Metadata for network services | ats-invocable-sds |
| Data – Interoperability | Harmonized data models for Annex I–III themes | Interoperability-metadata | ||
| Network Services – View | WMS services conforming to INSPIRE requirements | View-service | ||
| Network Services – Download | WFS/ATOM services for data access | Download | ||
| Network Services – Discovery | CSW services for metadata search | Discovery-service | ||
| Network Services – Transformation | Services for schema transformation | |||
| Data-Service Linking | Linking datasets to services in metadata | |||
| Registers – Core | Basic structure and descriptors for INSPIRE registers | |||
| Registers – Automatic Harvesting | Descriptor rules for automated register updates | |||
| Registers – Content | Validation of register content and structure |
item 30055097-28f2-590d-94e3-0fcad842b27c uit perceel collectie van deze API
![]()
![]()
PDOK smaakje (Geen RCE)
| Kastelen Landhuizen kasteel | ruïne |
![]()
zie ook Leermodule: https://pdok.github.io/leermodule-ogc-api/
##
flowchart LR
A[GIS-tijdperk]
A --> B["1999<br/>WMS<br/>Kaarten als afbeelding"]
A --> C["2002<br/>GML<br/>Uitwisseling van geodata in XML"]
A --> D["2005<br/>WFS<br/>Geografische objecten via XML"]
A --> E["2007<br/>CSW<br/>Metadata catalogi"]
A --> F["2007<br/>WPS<br/>Geo-processen"]
A --> G["2010-2015<br/>SOA<br/>XML domineert"]
A --> H["2010+<br/>REST groeit explosief<br/>JSON wordt standaard op het web"]
A --> I["2011<br/>Swagger<br/>API-documentatie en interactief testen"]
A --> J["2015<br/>OpenAPI Specification<br/>Industriestandaard voor API-beschrijving"]
A --> K["2017<br/>OGC API Features Part 1<br/>Eerste OGC API generatie"]
A --> L["2020+<br/>OGC API Tiles<br/>OGC API Maps<br/>OGC API Records<br/>OGC API Processes"]
A --> M["Nu<br/>API-first<br/>OpenAPI<br/>Swagger UI<br/>JSON<br/>Cloud-native<br/>STAC<br/>GeoParquet"]
U[INSPIRE-ontwikkelingen]
U --> V["2007<br/>INSPIRE-richtlijn<br/>Europese infrastructuur voor ruimtelijke informatie"]
U --> W["2010-2013<br/>Implementatieregels<br/>Metadata, dataspecificaties en netwerkdiensten"]
U --> X["2013+<br/>INSPIRE-data en -services<br/>Geharmoniseerde Europese geodata"]
U --> Y["Nu<br/>Open data en API's<br/>Modernisering en hergebruik"]
N[Ontwikkelingen buiten het GIS-domein]
N --> O["1998-2005<br/>XML en SOAP<br/>Webservices voor systeemintegratie"]
N --> P["2005-2010<br/>SOA en ESB<br/>Centrale gegevensuitwisseling"]
N --> Q["2010+<br/>Einde van het SOAP-tijdperk<br/>REST en JSON worden dominant"]
N --> R["2010-2015<br/>Big data<br/>Hadoop en grootschalige data-analyse"]
N --> S["2015+<br/>Streaming en cloud<br/>Realtime data-analyse en microservices"]
N --> T["Nu<br/>Data mesh<br/>Lakehouse<br/>AI en machine learning"]
G -. parallel .-> P
H -. sluit aan op .-> Q
M -. convergentie .-> T
J -. Europese context .-> U
U -. doorontwikkeling .-> M
%% Hoofdonderdelen van links naar rechts: GIS, INSPIRE en buiten het GIS-domein.
A ~~~ U ~~~ N