Home » railML newsgroups » railML.infrastructure » [railML 3.2] Modelling of Routes
[railML 3.2] Modelling of Routes [message #3392] Tue, 19 November 2024 07:49 Go to previous message
David Lichti is currently offline  David Lichti
Messages: 51
Registered: December 2020
Member
Dear Community,

In the context of a new railML 3.2 infrastructure export, we need to add some information about the construction aspects of blocks. railML already has the route element. But this element does not seem to have suitable attributes for the following properties:

  • Approach Signal Distance: The (nominal) distance of the approach signal from the route's destination signal.
  • Line of Sight: The maximum distance from which the route's exit signal can be recognized. This may be different for each route ending at a particular main signal. So the sightDistance property of interlocking signals is not suitable.
  • Linear Location: Exact limits of a route in the microscopic infrastructure. This may differ from the area enclosed by the entry and exit signals, if those are not located exactly on the block boundaries.
Is there any suitable alternative for modelling this data in railML 3.2? Or should we design an extension? It seems to me that this would best be solved by a routeIS element in the infrastructure sub-schema. This would be similar to the modelling of signals and switches.

Best regards

David
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML 3.2] Modelling of Routing Rules
Next Topic: [railML 2] Semantic Constraint at trackBegin and trackEnd
Goto Forum:
  


Current Time: Sat Jul 12 18:59:49 CEST 2025