Definition for different track types
Description
The definitions of track types in the railML 2 wiki differ from the consensus in the forum and the best practices from the wiki. Definitions should be consolidated and harmonized in the wiki.
Background
Different types of tracks have already been defined and documented in the wiki as "Best practices". National usage in different countries has been synchronized.
However, the definitions of the different track type enumeration values have not been adapted in parallel and still need to be modified.
Links
- Forum discussion:
- Vasco Paul Kolmorgen, 06.06.2017: [https://www.railml.org/forum/index.php?t=msg&th=521&start=0&]
- Thomas Langkamm, 20.12.2019: [https://www.railml.org/forum/index.php?t=msg&th=697&start=0&]
- Trac tickets:
- Wiki documentation:
- (railML 2) IS:Track: [https://wiki2.railml.org/index.php?title=IS:track]
Proposed solution railML 2
The following definitions of the different track types have been proposed:
-
mainTrack: A main track is either an open track between operational points or the extension of an open track within an operational point. It typically connects stations and is used for planned train journeys (trains in commercial operation or trains being moved between opera-tional points).
-
secondaryTrack: A secondary track is a track used for planned train journeys running in commercial operation or trains being moved between operational points, but it is not an open track between operational points or the extension of an open track.
-
sidingTrack: Siding tracks are tracks that are not used for planned train journeys, except at the start and end of a train journey if the train is shunted to or from a parking spot.
-
connectingTrack: Connecting tracks are tracks that do not fall into any of the above cate-gories. They are typically very short and connect other tracks. Examples are short track sections connecting two tracks where switches allow to move from one track to the other.
Proposed solution railML 3
Use same definitions like for railML 2 and bring them into the railML 3 UML.