Today's Messages (off)  | Unanswered Messages (on)

Forum: railml.interlocking
 Topic: [railML3.1] Modelling of a double slip switch
[railML3.1] Modelling of a double slip switch [message #2413] Fri, 03 April 2020 06:05
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 29
Registered: March 2016
Junior Member
Dear all,

there seems to be a general issue when transforming a track plan into railML:

1) For an 'ordinarySwitch' we have in IS the elements 'leftBranch' and 'rightBranch'. Just from the netRelations it
seems not really possible to decide which is one of the both branches. How would you solve the issue?

2) For a 'doubleSwitchCrossing' we have in IS the elements 'straightBranch' and 'turningBranch' but in IL we need to
split into two normal switches which again have 'leftBranch' and 'rightBranch'. Could this be solved just from the
topology information? How would you do this trick?

--
Regards,
Jörg von Lingen - Interlocking Coordinator
Forum: railml.infrastructure
 Topic: [railML3.1] Modelling of a double slip switch
[railML3.1] Modelling of a double slip switch [message #2412] Fri, 03 April 2020 06:05
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 29
Registered: March 2016
Junior Member
Dear all,

there seems to be a general issue when transforming a track plan into railML:

1) For an 'ordinarySwitch' we have in IS the elements 'leftBranch' and 'rightBranch'. Just from the netRelations it
seems not really possible to decide which is one of the both branches. How would you solve the issue?

2) For a 'doubleSwitchCrossing' we have in IS the elements 'straightBranch' and 'turningBranch' but in IL we need to
split into two normal switches which again have 'leftBranch' and 'rightBranch'. Could this be solved just from the
topology information? How would you do this trick?

--
Regards,
Jörg von Lingen - Interlocking Coordinator



Current Time: Thu Apr 09 02:27:48 CEST 2020