Definition of a track
Description
The current definition of a track to be used for railML 3.1 is too strict as it allows tracks only to be limited by buffer stops, switches and crossings. This strict definition shall be revised and adapted in order to allow for very long and very short tracks.
Background
In railML 2.x, the railway track network topology is based on the element <track>. For a functioning data exchange it is necessary that there is a common understanding of the topology. However, the definition of a track in railML 2.x is rather weak: A <track> represents one of possibly multiple tracks (= "pair of rails") that make up a line. (see railML wiki).
For railML 3.x a more strict definition of a track has been chosen: A Track is defined by a railway section between two switches/crossings or between a switch/crossing and a buffer stop. Since the railway network topology in railML 3.x is based on RailTopoModel elements <netElement> and <netRelation>, the <track> has no topologic dimension. Considering the <track> as a pure NetEntity derived object that is placed on top of a topology, the track does not have to be defined that strictly. It is possible to allow for a weaker definition, too.
Links
- Forum discussion:
- Stefan Hubrig, 02.10.2019: [https://www.railml.org/forum/index.php?t=msg&th=684&goto=2252&#msg_2252]
- Trac tickets:
- Wiki documentation:
- (railML 2.x) IS:track: [https://wiki2.railml.org/index.php?title=IS:track]
- IS:track: [https://wiki3.railml.org/wiki/IS:track]
Proposed solution railML 3.2
Weaken the definition of a track in railML 3.x. In order to group short tracks to longer tracks, the reference attribute <track>@belongsToParent can be used.
Proposal for a definition of Track: A track is a railway section that can be traversed by a train in a continuous motion.
Adapted documentation in model (exported to wiki and schema).