| Re: [railML3] Extensions to the Modelling of Signals [message #3753 is a reply to message #3750] |
Wed, 15 October 2025 10:02   |
Mathias Vanden Auweele
Messages: 167
Registered: February 2025
Location: Brussels
|
Senior Member |
|
|
Hello Georg,
1) Yes, for a signal that is applicable on several tracks, you need to create 2 SpotLocations for that one signal. The modelling of RTM allows for this. There is an example in the RTM wiki, look for "clearing post":
https://wiki.railtopomodel.org/wiki/Object_positioning_in_th e_network
2) I think it's a good idea to extend railML to support your use case. I can think of some alternatives on how to model this in railML 3.4:
- option 1: a new type 'Gantry' can be added to the <overCrossing> element and an optional @overCrossingRef added to <signalConstruction>, that would also allow a <SignalIS> to be linked to a <signalConstruction> linked with a bridge.
- option 2: a new element <supportConstruction> with a similar @supportConstructionRef added to <signalConstruction>
- option 3: add the ability to use <designators> in <signalConstruction> and use external designators
- option 4: add a @genericAreaRef to <signalConstruction>
Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium
|
|
|
|
Members
Search
Help
Login
Home
