2.3

2.3 Version

Austrian Elementary Profile UNPLANNED EVENTS

Status definition refers to ISO 14187
Card
Profile object
SituationPublication
Profile information

ASFINAG provides DATEX II  traffic data feeds in real time with 24/7/365 availability of all Austrian highways and motorways. Principal contractors for the data would be service providers for mobile transmission to vehicles. Please visit https://services2.asfinag.at/web/trafficdata/ for registration and to acquire a contract.

Austria promotes the idea of Elementary Profiles to be provided in the same form by every EU member starte. Any necessary filtering or aggregation would be performed by the contractor.

This section describes the Austrian Elementary Profile "Unplanned Events". It uses SituationPublication to describe the unplanned events content. Location referencing is done using Points and Linear elements in the form of coordinates and ALERT-C. OpenLR location referencing is also supported. It also uses few B level extensions in addition to the approved extensions, which are also documented. One of the important extension is the extension for “Graph Integration Platform (GIP)”. The GIP provides a digital map of Austria’s transport network to all authorities.

Change log

Changes from v1.0 to v2.0 (published on 11.03.2019):

  • Renamed the profile from "AustrianTrafficMessages" to "AustrianUnplannedEvents"
  • Added level B extensions for GIP location referencing
  • Included exchange related data elements (such as keepAlive and subscription)

Changes from v2.0 to v2.1 (published on 04.06.2019):

  • Added the relative location referencing method "DistanceFromLinearElementReferent"
  • Added the element "capacityRemaning" to the "Impact" class
  • Added the element "situationRecordCreationReference" to the "SituationRecord" class
  • Added the elements "commentDateTime" and "commentType" to the "Comment" class

The older version "v2.0" of the AustrianUnplannedEvents is provided inside the attachment "http://datex2.eu/sites/default/files/d2-profile/AustrianUnplannedEventsProfile_2.zip".

 

Organization name
ASFINAG
Organization description

ASFINAG acts as an economically responsible motorway operator. We are convinced that modern and sustainably developed infrastructure is essential both for the mobility requirements of every single person and for Austria as a location for business. By using new technologies and innovations, we want to make Austria's motorways and expressways amongst the safest in Europe – in the interest of our customers and to strengthen the country as a place in which to do business.

Website
http://www.asfinag.at/
Country/Region
AT
Centre type
TMC
Contact name
Dipl.-Ing. Gottfried Allmer
Contact mail
gottfried.allmer@asfinag.at
XMI file
Selection file

Austrian Elementary Profile PLANNED EVENTS

Status definition refers to ISO 14187
Card
Profile object
SituationPublication
Profile information

ASFINAG provides DATEX II  traffic data feeds in real time with 24/7/365 availability of all Austrian highways and motorways. Principal contractors for the data would be service providers for mobile transmission to vehicles. Please visit https://services2.asfinag.at/web/trafficdata/ for registration and to acquire a contract.

Austria promotes the idea of Elementary Profiles to be provided in the same form by every EU member starte. Any necessary filtering or aggregation would be performed by the contractor.

This section describes the Austrian Elementary Profile "Planned Events". It uses SituationPublication to describe the planned events content. Location referencing is done using Points and Linear elements in the form of coordinates and ALERT-C. OpenLR location referencing is also supported. It also uses few B level extensions in addition to the approved extensions, which are also documented. One of the important extension is the extension for “Graph Integration Platform (GIP)”. The GIP provides a digital map of Austria’s transport network to all authorities.

Change log

Changes from V1.0 to V2.0 (published on 15.03.2019):

  • Renamed the profile from "AustrianRoadworks" to "AustrianPlannedEvents".
  • Added level B extensions for GIP location referencing.
  • Marked the currently used data elements in the Profile by ASFINAG in green.
  • Update the documentation with a detailed description of the lane restrictions in case of some planned events such as construction works. 
  • Included exchange related data elements (such as keepAlive and subscription).

Changes from V2.0 to V2.1 (published on 03.10.2019):

  • Added the relative location referencing method "DistanceFromLinearElementReferent"
  • Added the element "capacityRemaning" to the "Impact" class
  • Added the element "situationRecordCreationReference" to the "SituationRecord" class
  • Added the elements "commentDateTime" and "commentType" to the "Comment" class

The older version "v2.0" of the AustrianPlannedEvents is provided inside the attachment "http://datex2.eu/sites/default/files/d2-profile/AustrianPlannedEventsPr…".  For any other information related to the older versions please contact "gottfried.allmer@asfinag.at".

 

Organization name
ASFINAG
Organization description

ASFINAG acts as an economically responsible motorway operator. We are convinced that modern and sustainably developed infrastructure is essential both for the mobility requirements of every single person and for Austria as a location for business. By using new technologies and innovations, we want to make Austria's motorways and expressways amongst the safest in Europe – in the interest of our customers and to strengthen the country as a place in which to do business.

Website
http://www.asfinag.at
Country/Region
AT
Centre type
TMC
Contact name
Dipl.-Ing. Gottfried Allmer
Contact mail
gottfried.allmer@asfinag.at
XMI file
Selection file

Literal for "People throwing things on the road"

Submitted by Joerg Freudenstein on Wednesday, 21 January, 2015 - 10:38
Source
Website

TMC Event code 897 says "People throwing objects onto the road. Danger". In DATEX II, the best match is "attackOnVehicle" (a DisturbanceActivity), which is semantically not the same (you can think of throwing stones without attacking a vehicle as well as an attack on a vehicle without throwing stones).

Proposal is to add a literal like "throwingObjects" to DisturbanceActivity.

Aquaplaning

Submitted by Joerg Freudenstein on Wednesday, 21 January, 2015 - 10:37
Source
Website

TMC Event codes distinguish between "danger of aquaplaning" (1002) and "surface water hazard" (1041), DATEX II does not. Proposal is to add "aquaplaning" to  WeatherRelatedRoadConditionTypeEnum.

VehicleCharacteristics for TrafficElements

Submitted by Joerg Freudenstein on Wednesday, 21 January, 2015 - 10:36
Source
Website

For some TrafficElements, it is not possible to define specific VehicleCharacteristics.

Concrete example is the safety related message "Strong winds affecting high-sided vehicles". "StrongWinds" is a PoorEnvironmentCondition (thus a TrafficElement), where you cannot attach the vehicleType "highSidedVehicle".
(Note: For Accidents and VehicleObstructions, such a link exists).

Information Owner / Resposable Organization

Submitted by Fabrizio.Paoletti on Tuesday, 30 December, 2014 - 17:16
Source
Datex stakeholder

Single DATEX elementary  Information may be related to some organization which is responsible of the data which is delivered among centres

i.e. the Road Owner which directly manages Traffic Management Centres, or Police Centres which manage information for public national or regional road 

the organization which is responsible of this information should be clearly identified in DATEX, which thing is not explicitly and completely covered in the current model as we have

Parking: Issues for version 3.0 and technical note

Submitted by Joerg Freudenstein on Friday, 12 December, 2014 - 11:52
Source
Website

These are bug fixes, improvements and proposals for changes on the Parking model for DATEX II version 3.0.
A technical note for migration of the ParkingPublications to Level A is also included.

Bug fixes
- ParkingTypeOfGroup must end with ‘Enum’
- parkingOccupanyDetectionType: Typo in attribute name (missing ‘c’) (two times, in ParkingSpaceBasics and in ParkingRecord!)

Improvements

Parking: Imporvements on definitions

Submitted by Joerg Freudenstein on Friday, 12 December, 2014 - 11:48
Source
Website

These are some slight improvements for Parking definitions:

  • Definition of numberOfChargingPoints: Typo in ‘charing’ (missing ‘g’)
  • Definition of InterUrbanParkingSiteLocationEnum is wrong, must not focus on trucks
  • Definition of parkingLastMaximumOccupancy: use ‘parked’ instead of ‘parking’

Datex II v2.3 PIM unreadable in Enterprise Architect v7

Submitted by Anonymous (not verified) on Monday, 8 December, 2014 - 13:16
Source
Website

I have downloaded the PIM for v2.3 and am unable to open the zipped EAP file. I am getting the error "It is already opened exclusively by another use, or you need permission yo view its data". See attached file.

It is possible that this is because I am using EA version 7.1, however the previous version of the PIM was readable in this version.