Add route description
Description
This ticket was raised by Norway as part of the standardization in Norway and shall be used commonly in the future.
This element is a new high-level grouping element introduced in raiLML2.4nor.
A route is defined as a configured piece of infrastructure, which allows a train to pass a set railway path safely and legally. The routes are described with their properties independently from one another. Routes are currently not represented in railML2.4.
A route can be grouped into four parts:
- The path of the route and the route properties
- If applicable, the approach speed in front of the route
- If applicable, the overlap behind the route
- Its release groups: Grouping of track sections to allow a partial release
For more details see document “railML2.4nor Infrastructure Documentation“, version 1.3, 03.07.2020 (https://www.jernbanedirektoratet.no/railML), point 4.8.
Which of the existing elements can be used?
- none
Sub-elements:
- (#399)
- (#398)
- (#400)
- (#417 (closed))
For description of sub-elements and attributes see document above, point 4.8.2.
The sub-element has the following optional sub-elements:
Background
The Norwegian use cases "capacity planning" and "routes for timetable simulation" have a need to model routes without interlocking.
The ISO “railDAX” project uses these elements as well.
Links
- Forum discussion:
- Torben Brand, 02.03.2017: [https://www.railml.org/forum/index.php?t=msg&goto=1520&#msg_1520]
- Trac tickets:
- #391
- Wiki documentation:
- none
Proposed solution in railML 2.6
tbd
Proposed solution in railML 3.2
The existing scheme Interlocking shall be used.