Extending the <speedProfile> element
The current implementation of speed profiles in railML 3.1 is insufficient w.r.t. parameters required by the ETCS specification. railML use case working group "ETCS" agrees on modifying the implementation in railML 3.x.
- Forum discussion:
- Thomas Nygreen, 24.12.2018: [https://www.railml.org/forum/index.php?t=msg&th=627&goto=2053&#msg_2053]
- Thomas Nygreen, 25.12.2018: [https://www.railml.org/forum/index.php?t=msg&th=627&goto=2054&#msg_2054]
- Christian Rahmig, 01.11.2019: [https://www.railml.org/forum/index.php?t=msg&th=686&start=0&]
- Trac tickets:
- Wiki documentation:
- use case "ETCS Track Net": [https://wiki2.railml.org/index.php?title=UC:IS:ETCS_track_net]
Proposed solution railML 3.2
basic speed profile
It is suggested to define a new boolean attribute @isBasicSpeedProfile in order to identify basic speed profiles. If the speed profile is not a basic one, further information has to be provided using child elements.
maximum cant deficiency
The maximum cant deficiency shall be modelled with a new attribute @maxCantDeficiency (integer, 80..300 mm). At the same time, the existing attribute @cantDeficiency shall be marked DEPRECATED.
The enumeration attribute @type values shall be adapted: values "mixed" and "all" shall be added; value "tiltingPassenger" shall be removed.
As requested in the forum the railML model shall allow for multiple train types to be included in one element. Thus, the multiplicity of shall be changed from 0..1 to 0..*
The ETCS train category number modelled with attribute @etcsTrainCategoryNumber shall not be used as "leading" information, but only as "derived" information. The parameters that define its value are: