| [railML3] Extensions to the Modelling of Signals [message #3750] |
Tue, 14 October 2025 10:22  |
Georg Boasson
Messages: 24 Registered: October 2020
|
Junior Member |
|
|
We very much like to extend the modelling of signals with two more options. Both options are related to the physical location of signals.
1) One signal (or group og signals) may be valid for several tracks
One physical signal may be valid for several tracks. Example: A stop post signal may be placed between two tracks with arrows showing that this signal is valid for both tracks.
See example with a Stop post signal between two tracks (Stopping Place.pdf)
May be this scenario could be solved by using several <spotLocation> for the <signalIS>?
2) Signals belonging to different tracks (referenced to different netElements) may be located at the same mast (pole, gantry, etc)
Several different signals may be placed together due to limited space. A possible example here may be two ETCS markerboards placed at the same pole but valid for differnet tracks.
See example with two signals placed together on a single mast (Markerboards on same pole.df / Sira station)
Maybe the subelement <signalConstruction> can be extended with a possibility for different signals on the same mast as mention in Forum post #2786?
Can the pole itself be an element? Or with a reference to a @mountedTogether attribute?
See also #3097 for other related topics of the modelling of signals.
|
|
|
|