Home » railML newsgroups » railML.infrastructure » [railML3] Improvement for railML element „etcsLevelTransition" ("etcsLevelTransition" with explicit priority information and level value syntax)
[railML3] Improvement for railML element „etcsLevelTransition" [message #2742] Mon, 31 May 2021 17:52 Go to next message
Karl-Friedemann Jerosch is currently offline  Karl-Friedemann Jerosch
Messages: 11
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 #2744 is a reply to message #2742] Thu, 03 June 2021 05:47 Go to previous message
Joerg von Lingen is currently offline  Joerg von Lingen
Messages: 148
Registered: May 2011
Senior Member
Thanks for the input.

Just one remark: "level_kind" would be better "levelKind" as other attribute names in railML.

--
Regards,
Jörg von Lingen - Rollingstock Coordinator
Previous Topic: Suggested definition of <ocpVis>
Next Topic: railML 2.3 infrastructure extension proposal line sections
Goto Forum:
  


Current Time: Thu Jul 25 08:08:06 CEST 2024