Home » railML newsgroups » railML.infrastructure » [railML v3.3 wiki] Ambiguous reference direction of track@mainDirection
Re: [railML v3.3 wiki] Ambiguous reference direction of track@mainDirection [message #4101 is a reply to message #4085] Mon, 17 August 2026 13:03 Go to previous messageGo to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 592
Registered: January 2016
Senior Member
Dear Mathias,

thank you for the extensive elaboration on this topic. I agree with you in the following points:
* //track/@mainDirection is not to be mixed with //track/linearLocation/@applicationDirection
* //track/@mainDirection linking with the orientation of topological netElements is unambiguous as soon as the track covers more than one netElement
* the idea of linking @mainDirection with a specific //track/linearLocation would be already an (intermediate) improvement.

Before I set up another Gitlab issue, I would like to ask the community: what are your requirements and expectations for the definition of a track's "main direction of usage"?

Best regards
Christian


Christian Rahmig – Infrastructure schema coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
 
Read Message
Read Message
Read Message
Previous Topic: [railML3] Texts on boards
Next Topic: [railML 3.4 bèta 3] BaliseGroup attribute validityDirection
Goto Forum:
  


Current Time: Fri Oct 16 16:33:19 GMT+2 2026