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 photos and address autocomplete available. This way you work with up-to-date, authoritative data from the Kadaster (the Dutch land registry), largely open data, with no 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 geodatasets available. It is managed by the Kadaster and provides data from organisations such as the Kadaster itself, Statistics Netherlands (CBS), Rijkswaterstaat and the RIVM. Among other things, you will find the BAG (addresses and buildings), the BGT (detailed large-scale topography), the BRT (topographic maps), up-to-date aerial photos and the Locatieserver for geocoding and address suggestions.
The data is offered through standardised geo web services: WMS for map images, WMTS for fast background tiles, WFS for querying features and their attributes, and the newer OGC APIs (Features and Tiles), to which the Kadaster is migrating its most widely used registers. The Locatieserver also offers REST endpoints for address autocomplete (suggest), lookup, free-text search (free) and reverse geocoding. The vast majority is open data that 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 at peak usage. This gives you an integration that grows with your application and that your own team can understand and manage.
Authentic base registries
BAG, BGT and BRT come straight from the Dutch government's national base registries. You work with current, reliable data on addresses, buildings and topography, maintained by the Kadaster (the Netherlands' Land Registry), not 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. With 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 follow a proven method that removes uncertainty early and delivers a stable integration. From an initial analysis of the datasets, services and map functionality you need through to go-live and ongoing maintenance, every step is aimed at an integration your team can understand and trust.
We map out which PDOK datasets and services you need (BAG, BGT, BRT, aerial photos or the Locatieserver) and which map functionality, zoom levels and queries your application requires.
We choose the right services (WMS, WMTS, WFS or OGC APIs), handle 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.
A controlled go-live with validation of map layers and queries, followed by ongoing maintenance, monitoring and migration to newer OGC APIs where it makes sense.
What a PDOK integration delivers in practice
Every PDOK integration is set up specifically for your datasets, mapping needs and adjacent systems. Below are the features we deliver most often for organisations that use open government geodata in their applications and portals.
Background maps & tiles
Fast BRT background maps and aerial photos via WMTS as the base layer of your application. Pre-rendered tiles load quickly at every zoom level, with the right projection and styling for a sharp, recognisable map in your own branding.
Address autocomplete (Locatieserver)
Error-free address entry with suggestions as the user types, via the Locatieserver's suggest and lookup endpoints. Selected addresses immediately return the BAG identifier and coordinates, so forms and requests arrive clean and validated.
Object queries via WFS
Query buildings, parcels, cables and 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 analyses.
Coordinate transformation
Seamless conversion between the Dutch RD 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 photos and your own data layered on top of each other. With legends, 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 that your application does not query PDOK directly with every map movement. This keeps maps fast, absorbs peaks and protects against a service being temporarily unavailable.
Typical use cases in practice
A PDOK integration turns out very differently for each organisation. We see a number of patterns come up often, and for each of them we have a working setup that pays 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 reports
Apps in which residents report an issue, such as a broken streetlight, litter or a dangerous paving slab, and pinpoint 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.
Real estate, energy & infrastructure
Organisations that use location intelligence: a real estate company that analyses buildings and plots using BAG and cadastral data, an energy company that projects networks onto the BGT, or an infrastructure company that maps out areas. WFS queries supply the objects and attributes for well-founded analyses.
Water authorities & route and area analysis
Water authorities and outdoor space managers who map work areas, inspection rounds and risk zones. PDOK provides the current base map and topography; your own data forms the operational layer on top. Also see custom software for water authorities.
Technology we use
We build PDOK integrations with the standardised OGC services and the newer OGC APIs, combined with the mapping and backend stack that suits you. The exact choice depends on your datasets, performance requirements and existing application, so that your own team can manage and further develop the integration.
If you want to use the open agricultural parcels, with the crop grown per area and per year, in your own systems, take a look at our BRP Crop Parcels integration.
If you need to convert RD and NAP coordinates to ETRS89, or back again, there's our RDNAPTRANS integration.
If you want to exchange urban water data in line with the GWSW, see our page on a GWSW integration.
For using the Kadaster's topography in your own application, see our page on a BRT integration.
Why 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, because an integration must not only be technically sound 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. That keeps communication lines short, prevents miscommunication and speeds up decisions when choices have to be made during the build.
Also see 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
- Specialist in map applications with Leaflet, OpenLayers and MapLibre
- Correct coordinate transformation between RD (EPSG:28992) and WGS84
- Structured error handling and retry mechanisms
- Extensive logging and monitoring from day one
- Clear documentation that your team can read and maintain
- A single point of contact, no passing you between account managers
- Ongoing maintenance and proactive further development
- An approach tailored to your existing IT landscape
Security and privacy in PDOK integrations
PDOK largely provides open geodata, which in itself contains no personal data. Privacy becomes a concern as soon as you combine that data with your own, for example residents' or customers' addresses. Appfront builds in line with the OWASP ASVS: encrypted traffic over TLS, least-privilege access to your own data, and separate permissions per integration. Where you expose PDOK through your own proxy, we secure and monitor that layer too.
When geodata is combined with personal data, we document the data flows so your record of processing activities is complete and you can demonstrably comply with the GDPR. We apply data minimisation — only the fields you genuinely need — and, for government organisations, we take account of the applicable information security standards, such as logging and access control.
More about our approach to security: information security policy and CVD policy.
- GDPR-compliant data processing and minimisation
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access and least-privilege principles
- Caching and proxy for robust availability
- Error handling for temporary service interruptions
- Monitoring and alerting on map and query layers
- Secrets management following best practices
- 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 (Publieke Dienstverlening Op de Kaart), the platform managed by the Kadaster. Through 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 right source when you want to use open, authoritative government geodata: current addresses and buildings from the BAG, the detailed BGT, BRT topographic maps or recent aerial photographs. It is largely open data with no API key required. If you need transactions or attribute queries on one specific basic registry, a direct source API may be a better fit. PDOK, for example, makes the BAG available as an open map and feature service, while the Kadaster also offers a separate BAG API for object-oriented queries. We will look at what suits you best together.
A simple integration — for example 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 generally take more time. After an intake conversation, we give you 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 map side we use libraries such as Leaflet, OpenLayers or MapLibre; on the back end, whichever stack suits you — 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 and GML, and in tile formats such as PNG and JPEG.
The cost depends on 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 maintenance and monitoring also play a part. The PDOK data itself is largely open data with no licence fees. We always provide a clear quote after a no-obligation analysis of your situation.
PDOK makes largely open geodata available, which in itself contains no personal data. Even so, Appfront pays close attention to privacy: as soon as you combine PDOK data with your own data — for example residents' addresses in a municipal portal — you create processing that 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 your record of processing activities stays complete and you can demonstrably comply with the GDPR.
Yes. Appfront regularly takes over the management of existing PDOK integrations, even if 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 draw up improvement proposals. Because PDOK is migrating its services from classic OGC services to newer OGC APIs, we also help future-proof existing integrations.
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 for location intelligence and area analyses; and software makers 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 unlock and in which map, portal or application PDOK should play a role — we're happy to advise on the right services, datasets, coordinate transformation and performance. A no-obligation first conversation quickly gives you a clear picture of what's possible. Whether it's a simple address autocomplete or a full geo-portal: we're glad to help.