IS:track

track
 

Scheme description / Schemenbeschreibung

Position of track in the XML-Tree / Position von track im XML-Baum

• Parent: tracks
• Children: trackDescr, trackTopology, trackElements, ocsElements <states><states>

Multiplicity / Anzahl

[1..1]

Semantics / Bedeutung

A <track> represents one of possibly multiple tracks (= "pair of rails") that make up a line. The <track> and its child element contain all information about the track's topology and the trackside elements associated with that track.

Attributes of track / Attribute von track

see tElementWithIDAndName

• type: a classification of the track (xs:string, optional). Possible values:
  • mainTrack: a regular track a of line used for frequent passenger and freight transport (German: "Hauptgleis")
  • secondaryTrack: a track not frequently used (e. g. for overtaing only) (German: "Nebengleis")
  • connectingTrack: a transfer track to another track e. g. in branches, points or cross overs
  • sidingTrack: a siding (German: "Abstellgleis")
  • stationTrack: a track in a station, possibly with plattform (German: "Bahnhofsgleis")

• mainDir: preferred driving direction on that track (tDirValidity, optional; follow link for further explanations)

• infraAttrGroupID: reference to an <infraAttrGroup>-element which specifies a basic set of common parameters for the track (Template:DocCO, optional)

Syntactic Constraints / Syntaktische Beschränkungen

Not yet described. / Noch nicht beschrieben.

Best practice & Examples / Empfohlene Anwendung & Beispiele

Not yet described. / Noch nicht beschrieben.

Notes / Anmerkungen

All tracks in RailML and the connections make up a graph. But different to many other data models, RailML does NOT require points, signals and other elements to be on vertices of that graph. In RailML, such elements can be located everywhere along the track (edge) and the number of elements a track can hold is not limited. Therefore, RailML uses "long" tracks which typically cover the complete length of a line in a single <track>-element.

But to ease conversion from other data sources, it is of course possible to concatenate many "short" <track>-elements to one "long" track of a line. There are no syntactical or semantical reasons why that solution would be no valid RailML.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.