LEVEL 2 USER
A situation publication can group several situations.
Situation definition: An identifiable instance of a traffic/travel situation comprising one or more traffic/travel circumstances which are linked by one or more causal relationships. Each traffic/travel circumstance is represented by a Situation Record.
Warning
Each situation has a unique versioned identifier. This versioned identifier comprises a part established when the situation is first created in a DATEX II system database and kept within that system for all its life. The second part (“version”) is established at every new version of the situation.
Such mechanism allows having several versions of the same situation in the same publication The situation severity on traffic can be indicated: “overallSeverity”.
If this situation relates to another situation, its reference can be indicated: “relatedSituation” (this reference is the “versioned identifier” of the corresponding situation object).
With this publication, attributes can be given in the InformationHeader which provide clients with information management details (area of interest, confidentiality, urgency, information status) relating to this situation.
Note
Special case: when the Supplier sends SituationPublication to Clients in Operating Mode 1 “Publisher Push on occurrence”, the situation management has to follow different rules.
A situation may be composed of one or more situation records.
Situation record definition: An identifiable instance of a single record/element within a situation.
This class is abstract.
Each situation record has a unique versioned identifier. This first part of this identifier is established when the situation record is first created in the DATEX II system database. It is completed by a version part. The first part is kept within that system for all its life. The subsequent versions of this situation record must differ by their version part of the identifier. If the situation record is forwarded down a supply chain, each DATEX II system within that chain will assign its own unique identifier to the record when it first creates a corresponding record in its database, but the (compound) identifier created by the original supplier in the chain may optionally be forwarded in the record’s situationRecordCreationReference attribute.
In DATEX Version 3.0, the SituationRecord class and adds the attribute “safetyRelatedMessage” of type Boolean. This attribute indicates, whether the corresponding SituationRecord specifies a safety-related message according to the Commission Delegated Regulation (EU) No 886/2013 with regard to data and procedures for the provision, where possible, of road safety-related minimum universal traffic information free of charge to user. A subset of DATEX II elements, which should be used to meet the requirements of the delegated regulation, can be found in the document “Safety related message sets –Selection of DATEX II Codes, TPEG2-TEC-Causes and TMC-Events for EC high level Categories” from the ITS Directive Working Group.
It is located with one group of locations.
It can have one cause.
It can have one impact on the traffic (when the record type is “TrafficElement” or “OperatorAction”), qualified with:
Source information can be given (country, identifier, name, type, if reliable or not)
A situation record has a validity composed of:
Remarks for forecasts:
There are 3 main categories of situation records:
These 3 categories are detailed in the following paragraphs.
This class is abstract.
There are 6 kinds of traffic elements:
Obstruction
Any stationary or moving obstacle of a physical nature (e.g. obstacles or vehicles from an earlier accident, shed loads on carriageway, rock fall, abnormal or dangerous loads, or animals etc.) which could disrupt or endanger traffic.
This class is abstract.
For each obstruction type, the number of obstructions can be given.
For each obstruction type, details can be given of:
There are 5 kinds of obstructions:
Details can be given: type, number of vehicles waiting, queue length, relative traffic flow, traffic flow characteristics, traffic trend type.
Accident
Accidents are events in which one or more vehicles lose control and do not recover. They include collisions between vehicle(s) or other road user(s), between vehicle(s) and any obstacle(s), or they result from a vehicle running off the road.
Details can be given:
Equipment or system fault
Equipment or system which is faulty, malfunctioning or not in a fully operational state that may be of interest or concern to road operators and road users. The type of equipment or system and the type of fault must be given.
The type of equipment or system and the type of fault must be given.
Activities
Deliberate human actions external to the traffic stream or roadway which could disrupt traffic. Details must be given in term of: types of authority operations / disturbance / public event, and possibly in term of mobility(mobile/stationary).
Conditions
Any conditions which have the potential to degrade normal driving conditions. A general indicator can be given with 8 possible values “drivingConditionType”:
There are 3 conditions categories:
For each operator action type, details can be given of:
There are 4 kinds of operator actions:
Roadworks
Highway maintenance, installation and construction activities that may potentially affect traffic operations.
This class is abstract.
Details can be given of:
Network management
Changes to the configuration or usability of the road network whether by legal order or by operational decisions. It includes road and lane closures, weight and dimensional restrictions, speed limits, vehicle restrictions, contra-flows and rerouting operations.
There are 6 types of network management:
Information on whether the network management instruction or the control resulting from a network management action is advisory or mandatory shall be given.
Other details can be given:
Roadside assistance
Details of roadside assistance required.
The roadside assistance type can be given: food delivery, helicopter rescue, vehicle repair …
There are 3 kinds of Service information: