3.0 Version

Traffic management response evaluation extension

Submitted by iancornwell on Monday, 19 November, 2018 - 18:10
Status definition refers to ISO 14817
Extension object
The objective is publication of quantitative evaluation of traffic management plans.
The primary extension objects are of class EvaluatedActionsPublication and EvaluationResultsPublication.
Extension information

This is a DATEX II extension model for the publication of quantitative evaluation of traffic management plans.

The model can express results from an evaluation service, for example a predictive evaluation service with short-term traffic prediction and what-if scenario modelling.

Although the model has not been implemented and tested in software in this precise form, it is based on a similar (non-DATEX) model that has been implemented and shown to support integration of systems.

Organization name
Mott MacDonald
Contact name
Ian Cornwell
Organization description

Company with team specialising in transport technology, including traffic management systems and DATEX II.

Contact mail
United Kingdom
Centre type
PDF Documentation

Issues with PositionConfidenceElipse

Submitted by Josef Kaltwasser on Friday, 3 August, 2018 - 13:51

The v3.0 Level A model contains a new class PositionConfidenceEllipse. The definition property of this class states that it describes an ellipsoidal shape that describes the positional accuracy of the point corresponding to "a predefined confidence level (e.g. 95 %)". This confidence value is not stated anywhere in the model! Knowing an ellipsoidal confidence area without knowing the corresponding confidence level seems useless.

1) Add an attribute to the class to specify the corresponding confidence level in %.

venue of public event

Submitted by iancornwell on Monday, 28 August, 2017 - 13:16
Datex stakeholder

It would be very valuable to have a new String attribute "venueName" in PublicEvent.

That has been in place for years in the UK traffic management system specification UTMC, and has been heavily used. But it is surely valuable in all countries.

GenericSitutionRecord is abstract

Submitted by jaderberg on Thursday, 29 September, 2011 - 09:09

GenericSituationRecord is abstract in the model. It should have been concrete. This makes is impossible to use the class as a hook class for levelB extensions. It is correct on GenericPublication.
The problem is fixed by unchecking the static checkbox on the GenericSituationRecord class.

This meens that we have, according to me, a severe bug in 2.0 and also in the standard part 3.

In practise, this meens for us in Sweden, that we have to continue to create some level C sevices instead of level B.