Home » railML newsgroups » railML.infrastructure » [railML3] Regular and a track of the opposite direction (Add new attribute or reuse an old one)
[railML3] Regular and a track of the opposite direction [message #3321] Fri, 13 September 2024 13:00
Larissa Zhuchyi is currently offline  Larissa Zhuchyi
Messages: 49
Registered: November 2022
Member
Dear all

track/@mainDirection has unsufficient definition "predominant direction of operation on this track; use this attribute to define the default direction of train operations, especially on double track lines".

We need to add a reference direction as in railML2 track/@mainDir [2] or spotLocation/@applicationDirection.

Currently there are two suggestions:

1) track/@mainDirection is a predominant direction of operation on this track "in relation to the first of the specified associatedNetElements and then continued over the following associatedNetElements independent of the orientation of the those following netElements" [1].

2) track/@mainDirection is a predominant direction of operation on this track related to the linearPositioningSystem (reference to which, can be presumably found at the linearCoordinateBegin child).

Moving reference direction from netElement to external system (linearPositioningSystem) can allow to use this attribute to represent the regular and track of the opposite direction (Regel- and Gegengleis in German) as defined in [3, 4].

Alternatively, for representing Regel- and Gegengleis we could add a new element e.g. trackOperation with attributes @positioningSystemRef and enumeration values "default, contraflow, undefined".

Which approach for modeling track/@mainDirection and Regel- and Gegengleis do you prefer?

[1] https://www.railml.org/forum/index.php?t=msg&th=964& goto=3302&#msg_3302
[2] https://wiki2.railml.org/wiki/IS:track
[3] https://www.tf-ausbildung.de/BahnInfo/gegengleis.htm
[4] https://www.sh1.org/eisenbahn/rgwb.htm

Sincerely,


Larissa Zhuchyi – Ontology Researcher
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

[Updated on: Fri, 13 September 2024 14:17]

Report message to a moderator

Previous Topic: [railML3] Need for modelling Lineside Electronic Unit
Next Topic: Level crossing with extended information
Goto Forum:
  


Current Time: Fri Sep 27 00:24:13 CEST 2024