IMGeluid integration development
Under the Omgevingswet (Environment and Planning Act), the national government maintains a Noise Register (Geluidregister) containing the noise data for roads, railways, industrial estates and other sources. Source managers such as central government, provinces, municipalities and water boards submit their data to the RIVM's Central Noise Data Facility (CVGG), following the Noise Information Model (IMGeluid). This is laid down in Article 12.71e of the Omgevingsregeling (Environment and Planning Regulations). Appfront builds the integration that converts your data from your own systems and calculation models into IMGeluid, validates it and prepares it for submission, so submitting no longer means manual work for every file.
What is an integration that submits your noise data according to the Noise Information Model?
An IMGeluid integration converts a source manager's noise data into the format the Noise Register expects. The register is a database within the CVGG, the system the RIVM manages on behalf of the Minister of Infrastructure and Water Management. According to IPLO, it contains, among other things, the data on noise sources, the value of the noise production ceiling or basic noise emission, and the noise attention area, for roads, railways and industrial estates, supplemented with aviation, wind turbines and shooting ranges. The data is public and can be viewed and downloaded by anyone.
The source manager is responsible for the quality and timely submission of the data. According to IPLO, this is usually within four weeks of a decision, notification or environmental permit; noise levels at noise reference points are submitted annually before 18 July for the previous year; and corrections are made immediately. Data is submitted via geluidgegevens.nl using eHerkenning. An environmental service or consultancy can do this on your behalf; since January 2026, you arrange that authorisation in the CVGG itself. In practice, the data is spread across a road management system, GIS files and the output of an acoustic calculation model, and every file is assembled by hand.
We build custom because every source manager keeps its data differently. The documentation is on the RIVM's GitHub: the exchange standard, the validation rules, example GML files for IMGeluid 3.1 and 4.0, and the release notes. Since June 2025, the RIVM has also offered a Validation API for checking files machine-to-machine, although not all validations are possible via that API. Noise maps and action plans for the European Environmental Noise Directive also go through the CVGG, but with their own GeoPackage template; we treat those as a separate flow.
From your systems
Not assembled file by file.
Validated first
Following the RIVM's rules.
In time
Deadline monitored per decision.
How we build your integration that submits your noise data according to the Noise Information Model
We start with your sources: which roads, railways or industrial estates you manage, where the data currently lives, which calculation model you use, who supplies the data and how you keep track of deadlines. Then we build the first integration for one type of source, for example your municipal roads, and validate the result in the RIVM practice environment first. Your noise specialist works with it for a while. Other sources, the annual data for noise reference points and deadline monitoring follow once that goes well. After that, we maintain the integration whenever the RIVM releases a new version of IMGeluid or its validation rules.
Data, model, deadlines.
Tested in the practice environment.
More sources and annual figures.
Go-live, monitoring, and maintenance when things change.
What an integration that submits your noise data in line with the Information Model Noise (IMGeluid) actually does
The components below appear in almost every IMGeluid integration. Which ones you need depends on your sources and on who submits the data.
Retrieving
From your asset management system and GIS.
Conversion
To IMGeluid.
Validating
Using the RIVM's rules.
Prepare
One file per submission.
Deadlines
Per decision and per year.
Log
Every submission recorded.
Who we build an integration that submits your noise data in line with the Information Model Noise for
The integration is intended for organisations that submit noise data regularly, for many sources or for several source managers. The more often there are decisions and changes, the more it pays off.
Municipalities
Local roads and railways.
Provinces
Roads and industry.
Regional environmental agencies
On behalf of source managers.
Consultancies
From your calculation model.
Technology and integrations
This page is about submitting noise data to the Geluidregister (noise register). If you are looking for environmental documents and their annotations, see our pages on the IMOW integration and the TPOD integration. For organisation-wide software, see our page on software for environmental services, and if you want to track employees' exposure to noise, see our page on software for noise and vibration exposure. You can read about how we work on building software.
Why Appfront for your integration that submits your noise data according to the Information Model Noise?
A file rejected during validation, a decision whose data is not in the register on time, or a municipality that does not know which version the environmental service submitted: any of these makes the register unreliable and costs your noise specialists time. That is what we build around: data from your own sources, validated before it is submitted, with every submission traceable by date and result.
Less manual work
Files from your systems.
Fewer rejections
Validated first.
In time
Deadlines in view.
Security and privacy for an integration that submits your noise data according to the Information Model Noise
Noise data in the register is public, but the files you work with often also contain drafts and data from ongoing decisions. The integration works with the permissions you assign: a specialist prepares, an authorised employee makes it ready. Every validation and submission is recorded with name, time and result.
The integration runs in a European data centre, with encrypted connections and storage and daily backups. Submission to the CVGG is done with eHerkenning by the source manager or an authorised representative; an API key for the Validation API is stored separately and encrypted.
Frequently asked questions about an integration that submits your noise data according to the Information Model Noise
Questions that noise specialists at municipalities, provinces, environmental services and consultancies ask before they get started.
An integration that converts a source manager's noise data from their own systems and calculation models into the Information Model Noise, validates it and prepares it for submission to the Geluidregister in RIVM's CVGG.
The source manager: central government, provinces, municipalities and water boards, for the sources they manage. They are responsible for quality and timely submission. They can authorise an environmental service or consultancy to do this on their behalf.
According to IPLO, usually within four weeks of a decision, notification or environmental permit. For noise at noise reference points, you submit annually before 18 July for the previous year, and corrections immediately. The rules in Article 10.42a of the Omgevingsbesluit (Environment and Planning Decree) apply to your situation; check any doubtful cases with your legal adviser or RIVM.
Submission goes through geluidgegevens.nl with eHerkenning. RIVM offers a Validation API for checking files machine-to-machine, but we did not find a public API for the submission itself in the documentation. The integration therefore prepares a validated file.
RIVM publishes sample files and an explanation for IMGeluid 3.1 and 4.0 on GitHub. Which version you may use is set out in RIVM's manual and release notes. The integration follows that version and is updated when a new one is released.
Noise exposure maps and action plans for the European Environmental Noise Directive are also submitted to the CVGG, but using their own GeoPackage template. That is a separate flow from the Noise Register (Geluidregister). We can build that in too, as a separate integration.
For source managers with many sources or decisions, and for regional environmental services and consultancies that submit data for several source managers. If you only submit a single file now and then, submitting via the portal is often enough.
Your noise data in the register without manual work?
Tell us which sources you manage, where the data currently lives and who submits it. We'll show you how an integration can handle that.