It would be desirable to use the poorEnvironmentTypeEnum within a MeasuredDataPublication (specifically to distinguish between Fog/Haze/Smoke).
Currently the only way (without using model extensions) of providing this information appears to be via a SituationPublication.
The Class SpeedPercentile is connected by a 0..1 multiplicity to TrafficSpeed.
Wouldn't it make sense to use a 0..* multiplicity here to be able to define more than one SpeedPercentile, for example speed of 85% of vehicles and speed of 30% of vehicles?
There is uncertainty in the usage of the literal "suspended" in "validityStatusEnum":
Is there still an obstruction for the road user or not?
Example: A road work situation that is suspended - is it an implemented road work with lane deviations etc. that is suspended for winter for example (but lane deviations still active)? Or is the roadwork deconstructed, i.e. no obstruction for the user any longer? (Shouldn't it be removed in that case?)
The Enum-attribute constructionWorkType in class ConstructionWorks is optional, but it is the only attribute in this class.
It should be considered to change it to mandatory, as it does not make any sense to omit it.
(Furthermore, this enumeration has got a general literal named "construcionWorks", i.e. there is no need to submit an empty class to keep information general).
Common set of restrictions on the road are weight, width, speed,height and length.
Speed is covered by the SpeedManagemt class, no problem.
For the others I found it not so obvious how to do it in DATEX II.
All will work if you say RoadOrCarrigewayOrLaneManagment and RoadClosed and then indicate via forVehiclesWithCharacteristicsOf for what vehicles height, Length, Width etc. for what vheicles the road is closed.
We have received a couple of request for suppport for bicycle in DATEX II.
There seams to be a lack in some areas so we propose to add
bicycleLane to LaneEnum
bicycleRoad (or path) to CarrigewayEnum.
Backgrund info from request
To allow Alert C Location Referencing to manage encoding to several Location Table, e.g. to allow encoding to multiple contries Location Tables or several versions in the same country for different Clients using different versions of the Location Table, it should be needed to update the molteplicity of relations among
Point and AlertCPoint
Linear and AlertCLinear
from 1 to 0..1 to 1 to 0..n
The following specific data types are defined in DATEX, but nowhere used in the model:
Bug in model: In two attributes of type VersionedReference, the mandatory tagged value "targetClass" is missing:
(both in VmsMessage class)
An inconsistency has been found in documentation provided on website, since version 1.0 in example messages and User Guide about Alert C Location coding Country Code
In Alert C Method for AlertCLinear, AlertCPoint and AlertCArea Classes the same attribute alertCLocationCountryCode has definition "EBU country code"
The UserGuide ( DATEXIIv2.0-UserGuide.pdf ) for Alert C report to use 'F' for France