| [railML3] Improvement for railML element „etcsLevelTransition" [message #2742] |
Mon, 31 May 2021 17:52  |
Karl-Friedemann Jerosch
Messages: 12
Registered: May 2020
|
Junior Member |
|
|
With railML 3.2 beta1 (=alpha2 of March 2021) the new element "etcsLevelTransition" required for use case "ETCS Track Net" has been added, modelled as following:
<railML>
<infrastructure>
<functionalInfrastructure>
<etcsLevelTransitions>
<etcsLevelTransition>
<switchToLevel value="Level 2" lengthOfAcknowledgement="50"/>
<switchToLevel value="Level NTC 6" lengthOfAcknowledgement="50"/>
<switchToLevel value="Level 0" lengthOfAcknowledgement="50"/>
</etcsLevelTransition>
</etcsLevelTransitions>
</functionalInfrastructure>
</infrastructure>
</railML>
Improvement 1:
In the current modelling, the sequence of the listed levels in railML provides implicitly the "Table of Priority" according to UNISIG SUBSET-026 (versions 2.3.0/3.4.0/3.6.0) section 5.10.2.3 .
Not strictly considering of the sequence during the export of a railML-file results in an incorrect data file.
To avoid this problem, the suggestion is to add a new attribute "priority" providing explicitly the priority of each level for to the "Table of Priority".
Improvement 2:
The possible entries for attribute "value" consist always of a text part and a non-negative-integer part. To avoid problems during data exchange due to missing syntax requirements for attribute "value" (for example: "ETCS Level NTC 6" or "NTC_6" or "NTC 06" and so on), the suggestion is to divide the information into two attributes:
- attribute "level_kind" to provide the text string with values "level", "level_ntc" and "unknown"
- attribute "value" to provide a non-negative-integer value.
Conclusion:
With improvements 1 and 2 the example will now look like:
<railML>
<infrastructure>
<functionalInfrastructure>
<etcsLevelTransitions>
<switchToLevel level_kind="level" value="2" priority="1" lengthOfAcknowledgement="50"/>
<switchToLevel level_kind="level_ntc" value="6" priority="2" lengthOfAcknowledgement="50"/>
<switchToLevel level_kind="level" value="0" priority="3" lengthOfAcknowledgement="50"/>
</etcsLevelTransitions>
</functionalInfrastructure>
</infrastructure>
</railML>
Note: level_kind="unknown" can be used if the information about the ATP equipment of the neighboring track section is currently missing and will be determined later.
|
|
|
|
|
|
| Re: [railML3] Improvement for railML element âetcsLevelTransition" [message #3274 is a reply to message #2744] |
Thu, 08 August 2024 14:17  |
christian.rahmig
Messages: 474
Registered: January 2016
|
Senior Member |
|
|
Dear all,
within the ETCS use case working group we discussed an extension of the etcsLevelTransition element. In particular, the following changes have been agreed on:
* @levelValue should be of type non-negative integer in order to allow for value "0"
* improve documentation of @priority values: "0" corresponds to the highest priority
* add new enumeration attribute @transmittedBy with values "RBC", "Balisegroup", "Euroloop", "RIU" to provide information about the transmission medium
* add new enumeration attribute @levelTransitionType with values "conditionalOrder" and "unconditionalOrder"
Are there any comments from the community?
Thank you very much and best regards
Christian
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
