Reference · built on requestCommons signalTransit, roads & mobility

NDW Open Data

Minute-level Dutch road traffic, travel times, incidents, roadworks, bridge openings, and truck parking from NDW's open data portal.

Request accessPricing ↗

About

Nationaal Dataportaal Wegverkeer (NDW) is a joint body of Rijkswaterstaat, the twelve provinces, the four largest municipalities, Vervoerregio Amsterdam, and Metropoolregio Rotterdam Den Haag. Its open data portal at opendata.ndw.nu serves gzipped DATEX II files: speeds and intensities per lane and vehicle category, travel times over predefined sections, the Actueel beeld situation feed, planning feeds for roadworks, events, and bridge openings, temporary closures and speed limits, truck parking status, and charging point locations.

Through Fibric, an operator reads the sections and situation records on your routes and proposes an ETA change, a rest stop, or a detour for your approval. Every proposal cites the DATEX II record and its timestamp.

This is a reference listing. It documents what Fibric would read from NDW Open Data and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Speeds and intensities: snelheden_en_intensiteiten_meetgegevens.xml.gz, minute data per lane and vehicle category, delivered by second 60 after the measurement minute
  • Travel times: reistijden_meetgegevens.xml.gz, average travel time in whole seconds over predefined measurement sections, with a configuration file for the sections
  • Actueel beeld: actueel_beeld.xml.gz, unvalidated situation records for accidents, incidents, road condition, weather, queues, and rush-hour lanes
  • Planning feeds: planningsfeed_wegwerkzaamheden_en_evenementen.xml.gz for roadworks and events; planningsfeed_brugopeningen.xml.gz for bridge openings
  • Temporary measures: tijdelijke_verkeersmaatregelen_afsluitingen.xml.gz for closures and tijdelijke_verkeersmaatregelen_maximum_snelheden.xml.gz for speed limits
  • Truck parking: Truckparking_Parking_Table.xml for locations and Truckparking_Parking_Status.xml for occupancy, updated every minute
  • Charging points: charging_point_locations.geojson.gz and the OCPI JSON files for locations and tariffs

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Send an ETA from measured travel time

    The travel time for the sections on a driver's route, in seconds, sets the delay. The operator proposes an ETA notice with the section names and the minute it read.

    With ETA Notice

  • Route around a closure or bridge opening

    A closure in tijdelijke_verkeersmaatregelen_afsluitingen or a planned opening in planningsfeed_brugopeningen ahead of a truck lets the operator propose a detour before the driver reaches it.

    With Route Deviation

  • Pick a rest stop with free spaces

    Truckparking_Parking_Status shows occupancy each minute. When a driver nears a rest limit, the operator proposes the nearest parking with space and records the status it read.

    With Driver Hours

  • Plan a charging stop

    charging_point_locations.geojson and the OCPI tariff file give an electric van its options on route. The operator proposes a stop and tariff for your approval.

    With Charge Readiness

Requirements

  • A fetch schedule per file; the portal lists Last modified and Size for each file and offers no push
  • A DATEX II v3 parser for the Verkeersdata NL profile, plus v2.3 for the files that remain in that version
  • The measurement section or site identifiers on your routes, matched from the configuration files or the shapefile
Authentication
None. The files on opendata.ndw.nu are downloaded over HTTPS without a key or account.

Limits

  • The DATEX II v2.3 traffic files (measurement.xml.gz, trafficspeed.xml.gz, traveltime.xml.gz) stop on 9 February 2027; v3 files replace them
  • Actueel beeld is unvalidated: NDW passes supplier records through before its own validation
  • Speeds above 255 km/h are usually not passed on, and a value of 256 or more marks a measurement error
  • The docs give no refresh interval for the situation and planning feeds; the file listing's Last modified is the timing signal

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request NDW Open Data ↗

Questions and answers

Which formats does NDW use?
DATEX II v3 for the situation, planning, and new traffic data files under the Verkeersdata NL profile; DATEX II v2.3 for the older traffic files until 9 February 2027; GeoJSON, CSV, and OCPI JSON for charging points and traffic signs; plain XML for truck parking.
How fresh are the traffic measurements?
Speeds, intensities, and travel times are minute data delivered by second 60 after the measurement minute. Truck parking status updates every minute. The portal shows a Last modified time for each file.
Under what terms can the data be used?
The NDW site states that, unless noted otherwise, the Creative Commons Zero (CC0) declaration applies to its content, with photos, video, and other images excepted. The open data portal itself carries no separate licence page.
Ask about NDW Open Data

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by Nationaal Dataportaal Wegverkeer (opendata.ndw.nu). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy