Traffic messages

Traffic messages


The data service Traffic reports belongs to the product group situation messages. This service is an important data source for current traffic information. The data service contains messages about traffic jams, wrong-way drivers, closures, detours and weather conditions on main roads (HWN) and partial secondary road networks (OWN). These messages are drawn up in the traffic centers. The data is validated by the Traffic Center Netherlands (VCNL). VCNL is, as part of Rijkswaterstaat, responsible for traffic information and national traffic management. VCNL aims for uniform and user-oriented traffic management in the Netherlands. Traffic messages (traffic jam and closure messages) are supplied with location information, length of the problem and a cause.

In this explanation of the data service the structure and content are described and if necessary the description is supplemented with an example for clarification.

Exchange of the data

The data service traffic messages is part of the situation messages. The situation messages are in the case of traffic messages formed by the situation on the road. The exchange within the NDW data service traffic messages is based on DATEX II. DATEX II is the European standard regarding the registration and exchange of traffic data. This is done using the DATEX II class D2LogicalModel. A push and pull mechanism available for the service. More information about system interfaces and the DATEX II class D2LogicalModel is available in the English version of Dutch Datex II profile. The exchange takes place based on situationPublication as part of the Datex II standard.

The exchange of the information of traffic messages is based on the situationPublication of the Datex II standard.

The NDW data service is published on as gebeurtenisinfo.xml.

Structure and content of the data service

The above is described in Datex II in situations. There are three types of specializations of situations within the data service traffic messages:

  1. Actions or instructions from the road operator (operatorAction)
  2. Data on situations on the road (trafficElement)
  3. Non-road related information (nonRoadEventInformation)

The further elaboration in Datex II takes place in situationRecords. As far as actions or directions of the road authority are concerned, this is done as follows.

Actions or directions from the road operator (operatoraction)

Subject Datex II name
Speed limits SpeedManagement
Restrictions or opening up of lanes RoadOrCarriagewayOrLaneManagement
Instructions to the user of the road GeneralInstructionOrMessageToRoadUsers
Description of dynamic traffic situations GeneralNetworkManagement
Description of redirects ReroutingManagement
Required or given help along the way RoadSideAssistance
Emergency work MaintenanceWorks

Data on situations on the road (trafficElement)

Subject Datex II benaming
traffic jam AbnormalTraffic
Accident situations Accident
Driving conditions of the road surface related to the weather WeatherRelatedRoadConditions
Influenced driving conditions due to the surface of the road NonWeatherRelatedRoadConditions
Driving conditions made difficult by weather conditions PoorEnvironmentConditions
Traffic disruption caused by animals on the road AnimalPresenceObstruction
Traffic nuisance on the road GeneralObstruction
Traffic nuisance due to infrastructure damage InfrastructureDamageObstruction
Traffic nuisance by a vehicle on the road VehicleObstruction
Traffic nuisance due to the influence of nature EnvironmentalObstruction
Traffic disruption due to police activity AuthorityOperation
Traffic disruption due to (planned) event PublicEvent
Traffic disruption due to (unplanned) event DisturbanceActivity
Traffic nuisance due to defective traffic-related system EquipmentOrSystemFault

Non-road related information (nonRoadEventInformation)

Subject Datex II name
Availability of public transport and information departure times TransitInformation
Disruption of a service along the way RoadSideServiceDisruption
Status of one or more parking facilities CarParks

Specific examples

Examples have been added of a number of specific situations and / or the interpretation of elements which are relevant to this data service.

Go to example use of point location based on VILD.

Go to example use of impact element impact in combination with subelements.

Go to example status cycle with specialization OperatorAction.