Custom NDW integration development for traffic data
The Nationaal Dataportaal Wegverkeer (National Road Traffic Data Portal), NDW, collects traffic data from road authorities across the Netherlands: traffic volumes, speeds, journey times, roadworks, closures and bridge openings. Much of it is open data. Appfront builds integrations with NDW, so that this data ends up in your own planning, dashboard or app in the form you need.
What is an integration with NDW traffic data?
An NDW integration retrieves traffic data from the Nationaal Dataportaal Wegverkeer and converts it into something your systems understand. A haulier sees in the route planning where traffic is at a standstill, a contractor sees what their closure does to journey times in the surrounding area, and a municipality sees on a dashboard the traffic volumes on its own roads alongside those of the national government. The data comes from one source instead of from separate websites.
NDW delivers much of its data in DATEX II, the European standard for traffic data, in versions 2.3 and 3. It is an extensive XML format with its own concepts for locations, measurements and situations. If you want to use it yourself, you have to translate it into road sections, times and alerts that suit your own work, and make sure it keeps coming in continuously. In practice, that is where most of the time goes.
We build custom because everyone needs different data. A planner wants journey times on their regular routes, a road authority wants traffic volumes per measurement location, a builder wants the alerts around their project. With open data, NDW gives no guarantee of availability, so the integration monitors the feed and shows when data drops out, so your system doesn't silently keep running on old figures. And because NDW changes its services and formats over time, we maintain the integration, so a new version of DATEX II or a changed source doesn't bring your planning to a halt unnoticed.
One source
Traffic data from NDW.
Translated to fit
For your own work.
Monitored
Visible when it fails.
How we build your integration with NDW traffic data
We start with your question: which data you need, for which area or routes, how current it has to be, and where it needs to end up. Then we build a first integration on the most important type of data, so you can quickly see whether it's useful. You work with it for a while. More data types, historical storage, analysis and monitoring follow if that goes well. After that, we maintain the integration as NDW or your usage changes.
Data, area, usage.
The most important source.
History and analysis.
Go-live, monitoring, and maintenance when things change.
What an integration with NDW traffic data actually does
The components below appear in almost every NDW integration. Which ones you need depends on what you want to do with the data.
Live data
Traffic volume and speed.
Journey times
On your own routes.
Notifications
Roadworks and closures.
Bridge openings
Where they are reported.
History
Stored for analysis.
Monitoring
Alert on outage.
Who we build an integration with NDW traffic data for
The integration is intended for organisations that want to use traffic data in their own work rather than checking separate websites. The more often the data influences decisions, the more it delivers.
Road authorities
Your own roads in view.
Transport operators
Journey time in your planning.
Road construction
Impact of closures.
Mobility services
Data in your own app.
Technology and integrations
This page is about using NDW data in your own systems. For planning roadworks, see our page on an app for traffic plans for roadworks, for parking our page on parking management software, and for an overview of all our integrations the integrations page. You can read about our approach at custom software development.
Why Appfront for your integration with NDW traffic data?
Planning based on yesterday's journey times, a dashboard quietly running on old figures, or a team that checks three websites every morning costs an organisation time and leads to wrong choices. That's what we build against: traffic data from a single source, translated to fit your own work, and an integration that tells you itself when something is missing.
Up to date
Data from the source.
Usable
In your own format.
Reliable
Outages are detected.
Security and privacy for an integration with NDW traffic data
NDW traffic data is largely public, but what you combine it with often isn't: your routes, your trips or your projects. These stay in your own environment, access is set up per role and every change is logged.
The integration runs in a European data centre, with encrypted connections and storage. Keys for NDW subscriptions are kept secure and are not shared with those who use the dashboard or the app.
Frequently asked questions about an integration with NDW traffic data
Questions organisations ask before they start using NDW data.
The National Road Traffic Data Portal (Nationaal Dataportaal Wegverkeer), a partnership of road authorities that collects and makes available traffic data from Dutch roads, such as traffic volumes, speeds, journey times, roadworks, closures and bridge openings.
Much of the data is available as open data, via an API and as downloads. For some data you work with a subscription and a key. We look at which route suits your question in the first step.
Much of the data comes in DATEX II, the European standard for traffic data, in versions 2.3 and 3. The integration converts it into road sections, times and notifications that your systems can use.
Yes. NDW offers historical data, and the integration can store live data itself so you can see trends, for example before and after a closure.
With open data, NDW gives no guarantee of availability. The integration therefore monitors the feed, shows when data is missing and makes sure your system shows this too, instead of quietly carrying on with outdated figures.
Yes. Travel times and incident notifications can be sent to your planning system or transport software, so a planner can see where traffic is stuck while planning. Which integration fits depends on your software package.
For organisations that use traffic data structurally in planning, management or their own service. If you only want to check now and then how busy it is, a public map will do.
Traffic data in your own systems?
Tell us which traffic data you need and where it should end up. We will show you how an integration with NDW can handle that.