2.2 Version
In the DATEX Tool, you cannot deselect roles with an index qualifier.
The Tool treats them as mandatory. This is because of the 1-1 relation, which determines – in these special cases - in fact the size of the qualified subitems.
I think, in the resulting XSD, this is no problem, the field is not set mandatory.
In Vehicle class there is vehicleCountryOfOrigin attribute with type MultilingualString. According to description it should be CountryEnum or maybe even better just String for accepting cars outside of EU, eg. Russia.
(reported on behalf of Jan Mynarík).
In CountryEnum there is a 'cs' = Serbia and Montenegro. But Serbia and Montenegro are two separate states, Serbia (rs) and Montenegro (me).
(reported on behalf of Jan Mynařík)
Important information:
The Parking Publications are already part of the most current DATEX Version 2.3.
Thus, there is no need to use the extension provided here, unless you use a version < 2.3.
Important version information:
Version 1.0 needed to be updated to Version 1.0a on 10th of October due to a small bugfix. All information on this site refers to the most current version 1.0a now. You can find the description of this latest change in the change-history document in the zip file.
This is version 1.0a of the Level B extension for three publications publishing parking information (ParkingTablePublication, ParkingStatusPublication and ParkingVehiclesPublication).
Topics covered by this extension are:
and many more details.
This extension will be part of the upcoming DATEX 2.3 version and is in progress to become standardised in CEN-TS 19157 part 6.
AlbrechtConsult is a consulting company specialised on planning, realisation and operation of systems related to traffic engineering. Within the last 10 years it has developed to become the leading independent IT and organisation consultant in the segment of road traffic systems, traffic management and telematics.
During the TG meeting in Firence a feature to verify that nothing has been changed in level A part of the model was requested.
One solution would be to store how a version of a specific version shoudl look like. When loading a model, and the same version, check will be made to ensure that nothing has been changed in the model.
With this extension, it is possible to label DATEX II traffic messages (i.e. SituationRecords) as safety related 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, which is enclosed in the documentation of this package.
AlbrechtConsult is a consulting company specialised on planning, realisation and operation of systems related to traffic engineering. Within the last 10 years it has developed to become the leading independent IT and organisation consultant in the segment of road traffic systems, traffic management and telematics.
In Level A, the following two attributes exist:
They seem to adress the same issue. I suggest to harmonize them (i.e. using the upper one for points, too).
Furthermore, nowhere is explained, that degree 0 means 'true north'. I suggest to add this to the definition(s).
The two attributes roadName and roadNumber are part of the LinearElement class. Their definition is specific for Linears, which makes it impossible to reuse these attributes elsewhere. Newertheless, these two attributes are valueable in a more general context.
Proposals:
* change both definitions to more general terms
* consider to move these attributes into a higher place of hierarchy, for example into the NetworkLocation class or into the SupplementaryPositionalDescription class (note that a Point for example is also usually located on a road).
The definition of TPEC LOC attribute 'height' is not generic.
This prevents the possibility to reuse it.
Proposal: Change the definition to make it generic or rename the attribute.
CEN 278 WG8 decided not to introduce a huge number of currency enum-literals but to use a String instead an to refer to the standard instead.
The same should be done with the Country enum (i.e. removing the enumeration, change to String, referring to standard).
Maybe other enumerations have to be checked as well for this issue.