Profiles Situation Publications
In Situation Publications “on occurrence” (as soon as available) data is provided regarding situations on the road and the statuses of objects. The Situation Publications are divided into the following profiles:
- Current Situation
- Planned Roadworks & Events Feed
- Temporary Traffic Management Measures - Closures
- Temporary Traffic Management Measures - Speed Limits
- Safety-Related Traffic Information (SRTI)
- Advance Notices for Scheduled Roadworks & Events
The location of events displayed within status data is often dynamic, and the applied location reference is therefore not predefined. In the status data product, the location reference is included with the situation information, and there is no separate configuration file. Within the Dutch profile DATEX II, agreements that apply to all status data have been made regarding the coding of the location and how to handle object statuses.
This type of message is described in DATEX II using the class SituationPublication.
To properly process or deliver the situation publications, agreements have been made regarding the semantics of the information. For this, see the separate section Semantics.
Further elaboration on road works
For describing road works, an IRS (Interface Requirements Specification) has been established. The functional agreements relating to the Dutch Profile DATEX II are explained in detail here. Further elaboration and examples of these agreements can be found under Semantics.
SituationPublication
A SituationPublication contains a collection of events on the road. Events can be standalone, consist of multiple events that together represent the situation, or of multiple events that have a causal relationship. In all cases, events are described using the element situation.
Situation
The element situation is a container for one or more events. For each event, an element situationRecord is included.
SituationRecord
The element situationRecord contains detailed information about the event, divided into the following categories.
Meta-information
Each described event is provided with meta-information that allows it to be identified (ID, version, version time) and traced back to the origin of the information.
Situation Identification
id
A situation receives an id from the data provider that is unique in time. This means that when a situation occurs, it gets an id that has not been assigned to any other active or past situation. The id remains the same as long as the situation is active. The id attribute is filled in a format that only indicates the unique situation. Including additional information in the id is not allowed.
Situation Record Identification
A situationRecord has a time-unique identification within the context of the situation. This means that a situation component receives an identification upon occurrence that has not been assigned to an active or already completed component of that situation. The situation component retains this identification until completion. The identification always begins with the id of the situation followed by an '_' and a contextually unique additional identification.
Location Reference (locationReference)
As described, in situation publications the location reference is included with the event information, and thus there is no separate configuration file. Each situation is provided with a location reference so that the location of the event can be inferred.
The location can refer to a:
- Point: A point on the road, e.g. a vehicle standing still at 1 location;
- Segment: A section of road, such as a traffic jam or a closed section of road such as a bridge or exit;
- Area: An area.
- Subsequent locations (route): A sequential list of locations.
- Collection of locations: A list of multiple locations that are related but do not have a sequential relationship.
For status data, a geographical location reference is always included, see also location reference based on x,y coordinates. Optionally, a [location reference based on OpenLR]](../../../locatiereferentie/locatiereferentie-openlr.md) can also be included. If VILD is present at the location, [ALERT-C location reference based on VILD locations]](../../../locatiereferentie/vild/locatiereferentie-vild-sts.md) can be used.
In addition to the description of the location on the road, additional information must also be included. This refers to situations that occur on specific lanes or specific parts of the road such as a parallel road, bridge or tunnel. This additional location reference is described separately.
The abstract element locationReference is used to describe one or more physically separated locations. When multiple locations are described within a locationReference, they can be related, such as in a travel route (or route), but they can also be unrelated.
For route locations, itineraryByIndexedLocations must be used as a concrete implementation of locationReference. The first element locationContainedInItinerary is given index value 0 and contains the mandatory geographical location reference. Any subsequent locationContainedInItinerary elements will have an index value of 1 or higher and contain ALERT-C location reference based on VILD locations.
See the following links for more information regarding the various location reference systems:
Event Information
The following information can be included about the actual event:
Validity
Whether and how long an event is valid is described using the element validity.
Other Information
Clarification on the event can be described in the form of a free text comment or URL-links.