Home » railML newsgroups » railML.infrastructure » [railML 3.4 bèta 3] BaliseGroup attribute validityDirection
Re: [railML 3.4 bèta 3] BaliseGroup attribute validityDirection [message #4050 is a reply to message #4040] Wed, 17 June 2026 14:02 Go to previous messageGo to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 583
Registered: January 2016
Senior Member
Dear Mathias,

the attribute //baliseGroup/functionalType/@validityDirection defines the direction of train movement for which the certain balise telegram is valid. This refers to ETCS variable Q_DIR allowing for values "normal", "reverse" and "both". The assumption was that a balise group can submit different types of telegrams with different validity directions. Basically, @validityDirection replaces @mileageDirection, but not //baliseGroup/spotLocation/applicationDirection.

The complete modelling background is documented in Gitlab issue #684 [1]. The related forum discussion can be found in [2].

Maybe someone from the ETCS use case working group can confirm the balise group model as implemented in railML 3.4 beta 3 is sufficient or whether changes have to be considered.

[1] https://development.railml.org/railml/version3/-/issues/684
[2] https://www.railml.org/forum/index.php?t=msg&th=1068& ;start=0&

Thank you very much and best regards
Christian

Christian Rahmig – Infrastructure schema coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Previous Topic: [railML 3.4 bèta 3] PlatformEdge's new attribute "lateralDistance"
Next Topic: Interpreting "begin" and "end" in the sub elements <linearCoordinateBegin> and <linearCoordinateEnd>
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Tue Sep 15 10:28:19 CEST 2026