Custom geo standards integration
Anyone exchanging geo-information with government will encounter the geo standards: NEN 3610, GML, GeoPackage, the metadata profiles and the OGC APIs. They are on the Forum Standaardisatie's comply-or-explain list, and Geonovum maintains them. Appfront builds the integration that provides and imports your own data according to those standards: objects that match an information model, exports that pass validation and services that consumers can use without custom work.
What is a geo standards integration?
A geo-standards integration makes your system exchange geographic data in the form the Dutch government prescribes. Geonovum develops and maintains this basic set of geo-standards, which is based on international standards from OGC, ISO and W3C. The basic set consists of the NEN 3610 basic model for geo-information, GML, GeoPackage, the metadata profiles for datasets and services, and OGC API Features and OGC API Tiles. The Standardisation Forum (Forum Standaardisatie) has placed these geo-standards on the comply-or-explain list for exchanging geographic information where the spatial dimension is of significant importance. This applies to central government, provinces, municipalities, water boards and the (semi-)public sector. Suppliers to those organisations will therefore encounter them too.
NEN 3610 is the common foundation beneath the geo-information models. It sets out terms, definitions, relationships and general rules for spatial objects, and sector-specific models build on it. The standard is maintained by the NEN Standards Committee for Geo-information; Geonovum is the point of contact and also carries out a conformity test. The NEN 3610:2022 version is aligned with MIM, the metamodel for information modelling. GML is the accompanying exchange format, an XML encoding that is also used within WFS. For services, OGC API Features and OGC API Tiles have been on the list since 2024, as successors to WMS and WFS. During the transition, those two are on the list of recommended standards, and PDOK will keep them running alongside the OGC APIs for the time being.
We build custom solutions because your own data is rarely already in the form of an information model. A management system has its own object types, its own attribute names and often its own coordinate system. The integration maps these onto the right information model, converts geometry to the standard coordinate system, creates exports in GML or GeoPackage with metadata included, and offers the data through an OGC API, optionally alongside WMS or WFS for consumers who have not yet switched. An object that fails validation is caught before it leaves the building.
Compliant
Mapped to NEN 3610.
Interoperable
GML, GeoPackage and OGC API.
Documented
Metadata according to the profile.
How we build your geo-standards integration
We start with your data and your consumers: which objects you manage, in which system, which information model or request applies, and who uses the data. Then we map your objects and attributes onto the information model and discuss the choices involved. We first build one exchange, for example a GML export or an OGC API Features service for one object type, and check it against the validation rules. Other object types, metadata and services follow once that works well. After that, we keep the integration up to date when the information model or the list of standards changes.
Objects, models, consumers.
Your own fields mapped to the model.
Validated against the rules.
Go-live, monitoring, and maintenance when new versions arrive.
What a geo-standards integration actually does
The components below feature in almost every integration based on the geo-standards. Which ones you need depends on your data and on what your consumers ask for.
Information model
Mapping to NEN 3610.
GML and GeoPackage
Exports and imports.
OGC API
Features and Tiles offered.
WMS and WFS
Alongside the new APIs.
Metadata
According to the Dutch profile.
Validation
Errors caught before delivery.
Who we build a geo-standards integration for
The integration is intended for organisations that supply geo-information to the government, or provide it themselves as a government body, and currently do so with separate exports and manual work. The more object types and consumers you have, the more it delivers.
Municipalities
Your own geodata as an open service.
Engineering firms
Deliveries according to the request.
Network operators
Objects according to a model.
Software builders
Standards in your software package.
Technology and integrations
This page is about exchanging your own data in line with the geo standards. If you mainly want to use national open geodata, such as maps and aerial photographs, see our page on the PDOK integration. For the Large-Scale Topography Base Register (BGT) there is the BGT integration, for addresses and buildings the BAG API integration, and for excavation work and cables and pipelines the KLIC notification integration. You can read about our approach on building software.
Why Appfront for your geo standards integration?
An export that the recipient rejects, a service that only works with your own viewer, or attributes that are named differently in every delivery cost time on both sides and raise questions in a tender. That is what we build around: one mapping onto the information model, validation before delivery, and services that follow the standard so every recipient can use them.
By the book
The standards that are asked for.
Reusable
The same service for every recipient.
Checked
Validation before delivery.
Security and privacy in a geo standards integration
Geo-information may look harmless, but it can be sensitive: the location of vulnerable assets, data about owners, or the whereabouts of people. The integration only delivers the object types and attributes you release, keeps internal fields out of exports and open services, and logs every exchange with its time and scope. Where personal data is involved, the GDPR applies.
The integration runs in a European data centre, with encrypted connections and storage. Services that are not public are accessed using protected keys or certificates. We agree with you in advance which data may be open, which is only for certain recipients, and who may approve a new delivery.
Frequently asked questions about a geo standards integration
Questions that municipalities, engineering firms and software suppliers ask before they get started.
The Dutch core set of standards for geo-information, maintained by Geonovum: the NEN 3610 basic model for geo-information, GML, GeoPackage, the metadata profiles for datasets and services, and OGC API Features and OGC API Tiles. They make geo-information findable, exchangeable and reusable.
The geo standards are on the Forum Standaardisatie's comply-or-explain list. Dutch government bodies and the (semi-)public sector require them when exchanging geographic information where the spatial dimension is of significant importance. As a supplier to those organisations, you will therefore see them in tenders.
The basic model for geo-information, the common foundation beneath the Dutch geo-information models. It contains terms, definitions, relationships and general rules for spatial objects. NEN 3610:2022 is aligned with MIM. Geonovum carries out a conformity test for information models.
OGC API Features and OGC API Tiles are the successors to WFS and WMS and have been on the comply-or-explain list since 2024. During the transition, WMS and WFS remain on the list of recommended standards. Geonovum advises anyone who currently offers WMS or WFS to keep offering them alongside the OGC APIs for a while.
Geography Markup Language, an XML encoding for exchanging and storing geo-information such as geometry and topography. It is the exchange format that goes with NEN 3610, and it is also used within WFS. The ISO version, ISO 19136, is on the comply-or-explain list.
A PDOK integration pulls national open geodata from PDOK into your own application, such as maps, BAG or aerial photos. A geo-standards integration is about your own data: mapping it to an information model and exchanging or publishing it in line with the standards. The two often go together.
For organisations that regularly supply geo-information in response to a data request, that want to offer their own data as an open service, or that build a software package that exchanges geodata with government bodies. If you only deliver a file once, an export from your GIS package is often enough.
Exchange your geo-information in line with the standards?
Tell us which data you manage and who uses it. We'll show you how an integration delivers and publishes it in line with the geo-standards.