2.3

This profile describes the message content for the OtherDENM use case as described by the project ECo-AT using the Situation publication. This profile distinguishes between 64 different message types in the context of traffic messages. Location referencing is done using three location containers indexed by “ItineraryByIndexedLocations”. The first location container with index “0“ uses “PointByCoordinates“, whereas the second and third location containers uses the extension “LinearByCoordinates”. In addition to “LinearByCoordinates” each location container of type “Linear” also contains an “AlertCLinear (AlertCMethod4Linear)” container. Change log: Changes from V1 to V2 (published on 05.11.2015):

• Added the data field “ClientIdentification” for the dissemination radius of the message as needed by the C-ITS-S. It is part of the exchange container.
• Added an additional location container of type “Point(PointByCoordinates)” to “ItineraryByIndexedLocations”. This represents the event position.

Changes from V2 to V3 (published on 26.11.2015):

• Added “AlertCLinear (AlertCMethod4Linear)” to each location container of type “Linear” in addition to “LinearByCoordinates”.
• Added the field “informationStatus” to differentiate between live and test data feed.

Changes from V3 to V4 (published on 27.07.2016):

• Added the situation record extension for indicating safety related traffic messages.
• Added more enumeration literals

Changes from V4 to V5 (published on 13.9.2016):

• Included "nonGeneralPublicComment" in the SituationRecord.

This profile describes the message content for the RWW use case as described by the project ECo-AT using the Situation publication. This profile distinguishes between 21 different message types in the context of roadworks, using beside the Roadwork class also the NetworkManagement or GeneralObstruction classes. Location referencing differentiates between triggerable RWW data, where a data set directly relates to a C-ITS message and augmentation RWW data, that can used to augment a RWW C-ITS message coming from a roadworks trailer. The former is done using three location containers indexed by “ItineraryByIndexedLocations”. The latter only uses one location container of type “Linear”. For location containers of type “Point“ the “PointByCoordinates“ is used, whereas for location containers of type “Linear“, the extension “LinearByCoordinates” is used. In addition to “LinearByCoordinates” each location container of type “Linear” also contains an “AlertCLinear (AlertCMethod4Linear)” container. Change log: Changes from V1 to V2 (published on 05.11.2015):

• Added the data field “ClientIdentification” for the dissemination radius of the message as needed by the C-ITS-S. It is part of the exchange container.
• Added the differentiation between triggerable RWW data and augmentation RWW data. The former one uses three location containers indexed by “ItineraryByIndexedLocations”, whereas the latter only uses one location container of type “Linear”.

Changes from V2 to V3 (published on 26.11.2015):

• Added “AlertCLinear (AlertCMethod4Linear)” to each location container of type “Linear” in addition to “LinearByCoordinates”.
• Added the field “informationStatus” to differentiate between live and test data feed.

This profile describes the location and content message for the IVI use case as described in the project ECo-AT using the VMS table publication and VMS publication. The IVI location uses the VMSTablePublication whereas the IVI content uses the VMSPublication. Location referencing is done by a level B extension which is also described in this document. The extension is named as “IviLocation”. The "IviLocation" contains two containers namely "DetectionZone" and "RelevanceZone" which uses another level B extension “LinearByCoordinates”. In addition to “LinearByCoordinates” each location container of type “Linear” also contains an “AlertCLinear (AlertCMethod4Linear)” container. Change log: Changes from V1 to V2 (published on 05.11.2015):

• Added the data field “ClientIdentification” for the dissemination radius of the message as needed by the C-ITS-S. It is part of the exchange container and only provided in the location message.

Changes from V2 to V3 (published on 26.11.2015):

• Added “AlertCLinear (AlertCMethod4Linear)” to each location container of type “Linear” in addition to “LinearByCoordinates”.
• Added the field “informationStatus” to differentiate between live and test data feed.

Changes from V3 to V4 (published on 22.12.2016):

• Added more enumeration literals to VmsDatexPictogramEnum and VmsDatexSupplementalPictogramEnum.

Changes from V4 to V5 (published on 28.02.2020):

• Updated the IviLocation container to add referencePosition with bearing

ASFINAG provides DATEX II traffic information of Austrian motorways for service providers and other interested institutions. This profile describes the message content for the Network Management. Note that the publication is two-folded: A static part (PredefinedLocationsPublication, no separate document on this) and a dynamic part (see documentation). Further note, that it is possible to omit the static part in case location referencing is done in the dynamic part (single file solution) using the Level B extension LinearByCoordinates (included in the corresponding dynamic schema).
In essence, this profile covers both the two-file and the single-file solution, as the main content does not differ between these solutions.
The static part is described in form of pictures at the end of the documentation.

ASFINAG provides DATEX II traffic information of Austrian motorways for service providers and other interested institutions. This profile describes the message content for Traffic data.

For data delivery the traffic data is split in two DATEX II files: 1. TrafficData_static: This file contains the identifiers of the traffic sensors along with the location information for all traffic sensors in different location referencing methods 2. TrafficData_dynamic: This file contains the identifiers of the traffic sensors along with the actual measurement values of the traffic sensors.