Custom BGT integration
Appfront builds integrations with the Basisregistratie Grootschalige Topografie (BGT), the detailed base map of the Netherlands covering buildings, roads, water, railways and land parcels. Via PDOK, the data is available as an API and as change files. We make sure the BGT is in your own systems, stays up to date by fetching only the changes, and is linked to your own objects and asset management.
What is a BGT integration?
The Basisregistratie Grootschalige Topografie (BGT) is the detailed digital base map of the Netherlands. It contains the location of physical objects such as buildings, roads, water, railways and vegetation. Data custodians, such as municipalities, provinces and water boards, each maintain their own part, and the data comes together in a national facility. Via PDOK it is available as an API and as change files, so others can keep their own copy up to date.
Many organisations use the BGT as a base layer: for managing roads and green spaces, for calculating surface areas in a maintenance specification, for network management or for design. Often a large file is downloaded now and then and imported by hand. The asset management system then falls behind, and a road that has been rerouted or a green area that has been paved is still recorded incorrectly in your own system.
We build custom because every use case is different: which area you need, which object types, which system the data has to live in, and how it is linked to your own asset objects. With an initial load followed by only the changes, your copy stays current without reloading everything each time. We look at which PDOK and Kadaster products and routes fit in the first step.
The base map in your systems
BGT objects for your area in your own asset management or design system, with the right object types.
Only what changes
An initial load and then only the changes, so your copy stays up to date.
Linked to your asset management
BGT objects linked to your road sections, green spaces or assets, with alerts when something changes.
How we build your BGT integration
We start with your use case: which area, which objects, in which system, and how they are currently loaded.
Your area, object types, systems and your own asset objects.
The BGT for your area in your system, via API or delivery.
Pulling in only the changes, and linking them to your asset objects.
Alerts for changes that affect your asset management, and ongoing maintenance after that.
What a BGT integration actually does
The components below appear in almost every BGT integration. Which ones you need depends on your use case.
Objects
BGT objects for your area of interest.
Mutations
Only the changes since the previous delivery.
Integration
BGT objects linked to your asset objects.
Quantities
Areas and lengths for asset management and specifications.
Alerts
An alert when a change affects your asset management.
Map
The BGT in your own map or viewer.
Who we build a BGT integration for
The integration is intended for those who use the BGT in their own systems.
Municipalities
Management of roads, greenery and water. The link with asset management is the core.
Network operators
Cables and pipes beneath public space. An up-to-date base map matters most.
Contractors and consultants
Specifications and design. The quantities are what you need.
Software suppliers
Asset management or design software. The mutations are the core.
Technology and integrations
This page is about integrations with the BGT. For addresses and buildings, see our page on a BAG API integration, for keeping the BAG up to date see our page on BAG mutation management, and for maps in apps see our page on a geographic app. You can read about our approach on building software.
For asset objects and their properties according to the CROW model, there is our IMBOR integration.
For using objects from NLCS drawings, there is our page on an NLCS integration.
Why Appfront for your BGT integration?
An asset management system running on an outdated map calculates with areas that are no longer correct. That is what we build on: the BGT in your systems, pulling in only the changes, and integration with your own asset management.
Always up to date
Changes come in automatically.
No large downloads
Only what changes is processed.
Asset management stays accurate
Areas and locations follow the base map.
Security and privacy in a BGT integration
The BGT is public, but the integration with your asset objects and the data in your systems often are not. Access is set up per role, and every delivery is logged.
The integration runs in a European data centre or in your own environment, with encrypted storage and daily backups.
Frequently asked questions about a BGT integration
Questions that asset managers and suppliers ask before they get started.
The Basisregistratie Grootschalige Topografie (Large-Scale Topography Key Register) is the detailed digital base map of the Netherlands, showing the location of buildings, roads, water, railways and land. Data custodians each maintain their own part, and the data is available via PDOK.
With an initial delivery for your area, and after that with only the changes. PDOK offers an API and mutation files for this. We look at which route suits your use case in the first step.
Because the full BGT is large, and your copy stays up to date faster and more reliably with only the changes. That way a large file does not have to be downloaded and loaded every time.
Yes. BGT objects are linked to your road sections, green areas or assets. If a BGT object changes, you can see which asset objects it affects, and you can update your asset management.
Yes. Areas and lengths per object type and per management area are calculated from the BGT, so a maintenance specification rests on the current map. After a change in the BGT, the new quantities are visible straight away, along with the difference from the specification currently in use.
This page is about using the BGT in your own systems. Source holders who maintain the BGT work with their own software for submitting mutations; we can connect to that as well.
For organisations that use the BGT in asset management, design or network management systems and currently rely on large downloads and manual work. We usually start with one area and the object types used most often, and expand from there.
The base map always up to date in your own systems?
Tell us which area and which objects you need, in which system and how you currently load them. We'll show you what the integration looks like.