Element situation

Element situation

A situation element is used for describing a situation on the road, or a group of logically linked situations, or the status of an object (for example a bridge or a rush-hour lane).

A situation has two mandatory attributes, id and version. A situation also contains the mandatory elements overallSeverity, situationVersionTime, headerInformation and one or more instances of a situationRecord. The relatedSituation element (which can also occur multiple times) is optional.

../../_images/element_situation.png

More information on the situationRecord element and underlying attributes and elements can be found here.

Attributes

id

A situation is allocated an ID number by the data provider that is unique over time. This means that a situation is given an ID when it arises that has never previously been used for designating another active or former situation. The ID remains the same for as long as the situation is active.

The ‘id’ attribute should be filled in, using a form that refers uniquely to this specific situation. Including additional information in the ID is not allowed.

Warning

Agreements have been made within the Dutch DATEX II Profile that this name is always determined in consultation with NDW.

Type: Required Domain
String Yes See above

version

A situation may be modified multiple times while it continues to exist. Each amendment is given a version number that is at least 1 greater than the previous version number.

The initial version of a situation is normally version 1. In specific cases for roadworks, it is possible that the starting version number will be greater.

Type: Required Domain
String Yes >= 1

Voorbeeld

<situation version="4" id="NLRWS_NLSIT002133332">
  ..
</situation>

Elements

The overallSeverity element

This element lets the road authority indicate the extent to which a situation is causing (severe) disruption to traffic.

Type: Required Domain
SeverityEnum Yes
highest
high
medium
low
lowest
none
unknown

Voorbeeld

<situation version="3" id="NLRWS_NLSIT002133328">
  <overallSeverity>lowest</overallSeverity>
  ..
</situation>

The relatedSituation element

There may sometimes be relationships between different situations, for example when associated roadworks are being carried out at various locations. These kinds of situations can refer to each other using this non-required element. This element is not an expression of any hierarchy: all situations that are related to one another refer to each other using one or more relatedSituation elements.

Note

Agreements have been made within the Dutch DATEX II Profile that both related situations will always refer to each other. This also applies even if a causal relationship has already been defined between the underlying situationRecords using the cause element.

This element does not have any subelements; the relationships are expressed in the form of three required attributes.

Attributes

id

ID of the situation in question

Type: Required Domain
String Yes Valid id

version

The version attribute refers to the version of the situation that is related to the current situation. This makes it possible to create direct links between the specific versions of the situation.

If the cross-reference is only used to create the link between the situation, then the value “last” should be used. This value means that the most recent version of the related situation should be used.

Type: Required Domain
String Yes Reference to the version of the situation or value “last”. See description above

targetClass

Value used to name the class that is being referred to.

Type: Required Domain
String Yes Situation

Example

<situation version="3" id="NLRWS_NLSIT002133328">

  <relatedSituation targetClass="Situation" id="RWS01_NLSIT0021433235" version="2"/>
  ..
</situation>

The situationVersionTime element

The UTC timestamp when the version in question became active according to the provider.

Type: Required Domain
DateTime Yes Date and time in UTC (Zulu notation)

Example

<situation version="1" id="NLRWS_NLSIT002133327">
  ..
  <situationVersionTime>2017-04-07T09:06:30Z</situationVersionTime>
  ..
</situation>

The headerInformation element

The headerInformation element contains two mandatory elements, confidentiality and informationStatus.

Subelements of headerInformation

The confidentiality element

This field can be used to define the confidentiality of the data.

Type: Required Domain
ConfidentialityValueEnum Yes
noRestriction
restrictedToAuthorities
The informationStatus element

The status of the information provided.

Type: Required Domain
InformationStatusEnum Yes real

Example

<situation version="3" id="NLRWS_NLSIT002133328">
  ..
  <headerInformation>
       <confidentiality>noRestriction</confidentiality>
       <informationStatus>real</informationStatus>
  </headerInformation>
  ..
</situation>