Custom PDOK integration development
Appfront builds custom PDOK integrations that bring the Dutch government's open geodata into your maps, portals and applications. Through the OGC services (WMS, WMTS, WFS), the newer OGC APIs and the Locatieserver, we make BAG, BGT, BRT, aerial imagery and address autocomplete available. This way you work with current, authentic data from the Land Registry (Kadaster), largely open data and without vendor lock-in.
What is a PDOK integration?
PDOK stands for Publieke Dienstverlening Op de Kaart (Public Services On the Map) and is the central platform through which the Dutch government makes open geodata sets available. It is managed by the Kadaster (Land Registry) and provides data from organisations including the Kadaster itself, Statistics Netherlands (CBS), Rijkswaterstaat and the RIVM. Among other things, it offers the BAG (addresses and buildings), the BGT (detailed large-scale topography), the BRT (topographic maps), current aerial imagery and the Locatieserver for geocoding and address suggestions.
The data is offered via standardised geo web services: WMS for map images, WMTS for fast background tiles, WFS for querying objects and their attributes, and the newer OGC APIs (Features and Tiles) to which the Kadaster is migrating the most-used registrations. The Locatieserver also provides REST endpoints for address autocomplete (suggest), lookup, free-text search and reverse geocoding. The vast majority is open data you can use without an API key.
Appfront builds on the official PDOK documentation and the OWASP ASVS security standard. For each use case we choose the right service, handle coordinate transformation between RD (EPSG:28992) and WGS84 where needed, and set up caching so maps load quickly even under peak use. The result is an integration that grows with your application and that your own team can understand and manage.
Authentic base registers
BAG, BGT and BRT come directly from the national government's basic registries. You work with up-to-date, reliable data on addresses, buildings and topography, managed by the Kadaster rather than from a derived copy.
Address autocomplete & geocoding
The Locatieserver delivers lightning-fast address suggestions as users type, plus geocoding and reverse geocoding. This lets you fill in forms without errors and convert an address to coordinates, or the other way round, without an external geocoding service.
Open data without lock-in
Most of PDOK is open data that you can largely use without an API key. Built on open OGC standards, you are not tied to a single supplier, and your mapping solution stays future-proof and interchangeable.
Our development process for PDOK integrations
We work to a proven methodology that resolves uncertainty early and delivers a stable integration. From an initial analysis of the required datasets, services and map functionality through to go-live and ongoing management, every step is aimed at an integration your team can understand and trust.
We map out which PDOK datasets and services you need, whether BAG, BGT, BRT, aerial imagery or the Locatieserver, and which map functionality, zoom levels and queries your application requires.
We select the right services (WMS, WMTS, WFS or OGC APIs), arrange coordinate transformation, and define the caching and proxy strategy for reliable performance.
We implement the map and query layer with automated tests, structured logging and monitoring. You see working builds along the way.
Controlled go-live with validation of map layers and queries, followed by ongoing management, monitoring and migration to newer OGC APIs where this makes sense.
What a PDOK integration concretely delivers
Every PDOK integration is set up specifically for your datasets, mapping needs and adjacent systems. Below are the features we most often deliver for organisations using government open geodata in their applications and portals.
Background maps & tiles
Fast BRT background maps and aerial imagery via WMTS as the base layer beneath your application. Pre-rendered tiles load quickly at every zoom level, with the correct projection and styling for a clean, recognisable map in your own corporate identity.
Address autocomplete (Locatieserver)
Error-free address entry with suggestions as the user types, using the Locatieserver's suggest and lookup endpoints. Selected addresses immediately provide the BAG identifier and coordinates, so forms and applications arrive clean and validated.
Object querying via WFS
Query buildings, parcels, pipelines or other objects with their attributes via WFS and OGC API Features. Filter by area or attribute and retrieve exactly the features you need as GeoJSON or GML, ideal for selections, lists and analysis.
Coordinate transformation
Seamless conversion between the Dutch RD coordinate system (EPSG:28992) and WGS84, so PDOK data lines up correctly with locations from your own systems, GPS or external sources. No more shifted maps or incorrect distances.
Map layers & thematic data
Combine multiple WMS and WFS layers into a rich map view: BGT detail, BRT topography, aerial imagery and your own data overlaid. Includes a legend, scale-dependent visibility and interaction such as click-for-info on objects.
Caching, proxy & performance
For high volumes, we set up a tile cache or proxy so your application does not query PDOK directly with every map movement. This keeps maps fast, absorbs peaks and protects against temporary service outages.
Typical use cases in practice
A PDOK integration looks very different from one organisation to the next. We see a number of patterns recur, and for each we have a working setup with attention to the right services, datasets and performance.
Municipal portals with map layers
Municipalities that show residents and civil servants map layers, such as zoning plans, public space, waste or permits, on a BRT or aerial photo base map from PDOK. Often combined with address autocomplete in application forms. Also read about building a municipal website and software for municipalities.
Public space reporting
Apps where residents report issues, such as a broken street lamp, litter or a dangerous paving stone, and mark the location on a PDOK map. Address autocomplete and reverse geocoding turn the click into an exact address and coordinate. See our public space reporting software service.
Property, energy & infrastructure
Organisations using location intelligence: a property firm analysing buildings and plots via BAG and cadastral data, an energy company projecting networks onto the BGT, or an infrastructure company mapping areas. WFS queries deliver the objects and attributes for well-founded analyses.
Water boards & route and area analysis
Water boards and managers of outdoor spaces who map working areas, inspection rounds and risk zones. PDOK provides the up-to-date base map and topography; your own data forms the operational layer on top. See also custom water board software.
Technology we use
For PDOK integrations we use the standardised OGC services and the newer OGC APIs, combined with the map and back-end stack that suits you. The exact choice depends on your datasets, performance requirements and existing application, so your own team can manage and further develop the integration.
If you want to exchange urban water data under the GWSW standard, see our page on a GWSW integration.
For Kadaster topography in your own application, see our page on a BRT integration.
Why choose Appfront for your PDOK integration?
Appfront has extensive experience building API integrations for a wide range of organisations in the Netherlands. We always start with a thorough analysis of your existing systems and processes. An integration should not only work technically, but also add practical value to the way you work.
With every integration we write clear documentation and make sure your own team, or a future supplier, can understand and manage it. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance.
You work with a dedicated point of contact who understands both the technical and the functional side. This keeps communication short, prevents misunderstandings and speeds up decisions when choices need to be made during development.
See also our broader services around custom software, software for municipalities and AI for government. Many clients combine a PDOK integration with a BAG API integration or a ZGW API integration.
- Experience with PDOK services: WMS, WMTS, WFS and the newer OGC APIs
- Familiar with BAG, BGT, BRT, aerial photography and the Locatieserver
- Specialists in map applications with Leaflet, OpenLayers and MapLibre
- Accurate coordinate transformation between RD (EPSG:28992) and WGS84
- Structured error handling and retry mechanisms
- Comprehensive logging and monitoring from day one
- Clear documentation your team can read and manage
- A fixed point of contact, no account managers passed around
- Ongoing maintenance and proactive further development
- A way of working aligned with your existing IT landscape
Security and privacy in PDOK integrations
PDOK mainly provides open geodata, which in itself contains no personal data. Privacy becomes a concern once you combine that data with your own records, for example residents' or customers' addresses. Appfront builds to the OWASP ASVS: encrypted traffic over TLS, least-privilege access to your own data, and separate permissions per integration. Where you serve PDOK through your own proxy, we also secure and monitor that layer.
For combining geodata with personal data, we document the data flows so your processing register is complete and you can demonstrably comply with the GDPR. We apply data minimisation, using only the fields you genuinely need, and for public sector organisations we take account of the applicable information security standards, such as logging and access control.
More on our security approach: information security policy and CVD policy.
- GDPR-compliant data processing and data minimisation
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access and least-privilege principles
- Caching and proxying for robust availability
- Error handling for temporary service interruptions
- Monitoring and alerting on map and query layers
- Secrets management in line with best practice
- Documentation for your record of processing activities
Frequently asked questions about PDOK integrations
Answers to the questions we get asked most often about PDOK integrations.
A PDOK integration is a technical connection between your application and the open geodata of PDOK (Public Services On the Map), the platform managed by the Kadaster. Using OGC services such as WMS, WMTS and WFS, the newer OGC APIs and REST endpoints such as the Locatieserver, you retrieve map layers, addresses and location data from national registers such as BAG, BGT and BRT. An integration can be simple (a background map or address autocomplete) or extensive (map layers, area analyses and location intelligence in a portal).
PDOK is the designated source when you want to use open, authoritative government geodata: current addresses and buildings from the BAG, the detailed BGT, topographic BRT maps or recent aerial imagery. It is largely open data and requires no API key. If you instead need transactions or attribute queries against one specific base register, a direct source API may be more suitable. For example, PDOK makes the BAG available as an open map and feature service, while the Kadaster also offers a separate BAG API for object-level queries. We will work out together what best suits your needs.
A simple integration, such as a PDOK background map or address autocomplete via the Locatieserver, can be delivered relatively quickly. More extensive scenarios with multiple map layers, WFS queries, area analyses and location intelligence in a portal usually take longer. After an intake meeting we give a realistic estimate, tailored to the datasets and services you need.
We work with the PDOK OGC services (WMS, WMTS, WFS), the newer OGC APIs (OGC API Features and Tiles) and REST endpoints such as the Locatieserver (suggest, lookup, free and reverse). On the mapping side we use libraries such as Leaflet, OpenLayers or MapLibre; on the back end, the stack that suits you, be it Node.js, Python, PHP or .NET. PDOK supplies geodata in the Dutch RD coordinate system (EPSG:28992) and in WGS84, in formats such as GeoJSON, GML, and tile formats such as PNG and JPEG.
The cost is determined by the number of datasets and services you want to expose, the complexity of the map functionality, any caching or a dedicated tile proxy for high volumes, and the amount of custom work in the query logic. Ongoing management and monitoring also play a part. The PDOK data itself is largely open data with no licence fees. We always provide a clear quotation following a no-obligation analysis of your situation.
PDOK mainly provides open geodata, which in itself contains no personal data. Appfront still pays close attention to privacy: once you combine PDOK data with your own records, for example residents' addresses in a municipal portal, the processing falls under the GDPR. We build to the OWASP ASVS standard, with encrypted data traffic (TLS), least-privilege access and logging. We document the data flows so that your record of processing activities stays complete and you can demonstrate GDPR compliance.
Yes. Appfront regularly takes over existing PDOK integrations, even when they were originally set up by another party. We review the services, map layers, coordinate transformations, caching and error handling in use, document the current setup and propose improvements. As PDOK migrates its services from classic OGC services to newer OGC APIs, we also help make existing integrations future-proof.
A PDOK integration suits any organisation that works with locations and maps. Municipalities, provinces and water boards use PDOK for portals and map layers; property, energy and infrastructure companies use it for location intelligence and area analysis; and software companies use it for address autocomplete and maps in their apps. Wherever you need reliable, up-to-date government geodata, from simple address validation to a full geo portal, a PDOK integration adds value.
Ready to build your PDOK integration?
Tell us which geodata you want to make available and in which map, portal or application PDOK should play a role. We're happy to help you choose the right services, datasets, coordinate transformation and performance. A no-obligation first conversation will quickly give you a clear picture of what's possible. Whether it's a simple address autocomplete or a full geo-portal, we're happy to help you move forward.