View source for IS:track

{{ElementDocu|
elementName = track

|parent = {{IS:Tag|tracks}}

|childs = {{IS:Tag|additionalName|track}} {{Intro|2.1}}, {{IS:Tag|any}}, {{statesWithLength}}, {{IS:Tag|trackDescr}} {{Depr|2.4}}, {{IS:Tag|trackTopology}}, {{IS:Tag|trackElements}}, {{IS:Tag|ocsElements}}, {{IS:Tag|infraAttrGroupRefs}}, {{tag|is|impairmentSections}} {{intro|2.5}}, {{tag|is|propPassengerInfo|track}} {{intro|2.5}}
|minocc=0
|maxocc=∞
|semantics =
A {{IS:Tag|track}} represents one of possibly multiple tracks (= "pair of rails") that make up a line. The {{IS:Tag|track}} and its child elements contain all information about the track's topology and the trackside elements associated with that track.

|inheritedAttributes =
{{InheritIdName
|id =
|code =
|name =
|description =
}}

|ownAttributes =
* {{Attr|type}}: This is a classification of the track. Possible values are: 
:* {{Enum|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 operational points).
:* {{Enum|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.
:* {{Enum|connectingTrack}}: Connecting tracks 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.
:* {{Enum|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.
:* {{Enum|stationTrack}}: {{depr|2.4}}This is a track in a station, possibly with platforms.
:For individual countries, we have provided a [[#National_usage_of_track.40type|description of national designations]] in order to simplify the mapping of the common designations for {{rml}} naming.<br/>{{Deu|Für einzelne Länder haben wir eine [[#National_usage_of_track.40type|Beschreibung nationaler Benennungen]] bereitgestellt, um die Abbildung der üblichen Bezeichnungen zur {{rml}}-Benennung zu vereinfachen.}}
:* {{OtherEnum
|notes_en =
|notes_de =
}}

* {{Attr|mainDir}}: This is the preferred usage direction on that track.
:* {{Enum|up}} This track is mostly used in the track definition direction (from trackBegin to trackEnd).
:* {{Enum|down}} This track is mostly used opposite the track definition direction (from trackEnd to trackBegin).
:* {{Enum|none}} There is no preferred driving direction for the track.
{{note|'''Please note:''' This attribute only indicates the standard direction of travel according to the operating rules or the direction of travel of a track predominantly used in regular operation. This does not allow conclusions to be drawn about the safety equipment or operational capacity of a track, especially since modern safety systems usually allow both directions of travel to be used in the same or similar way.<br>{{deu|'''Hinweis:''' Dieses Attribut gibt nur die Regelfahrtrichtung nach Betriebsregelwerk oder die im regulären Betrieb überwiegend benutzte Fahrtrichtung eines Gleises an. Rückschlüsse auf die sicherungstechnische Ausstattung oder betriebliche Kapazität eines Gleises können daraus nicht gezogen werden, vor allem auch, weil unter modernen Sicherungssystemen meist beide Fahrtrichtungen gleich oder ähnlich benutzbar sind.}}}}

{{InheritRef
|attributeName = infraAttrGroupRef
|contextLink = {{IS:Tag|infraAttributes}}
|notes_en ={{depr|2.2}}, it specifies a basic set of common parameters for the {{IS:Doc|track}}.
}}

|constraints =
{{InheritIdNameConstraints}}

* {{Attr|infraAttrGroupRef}} {{RailMLType|tGenericRef}}, optional

* {{Attr|mainDir}} optional

* {{Attr|type}} optional

|bestpractice = 

=== {{Attr|code}} attribute of a {{IS:Tag|track}} ===

It is recommended to fill {{Attr|code}} with a number of track in a schematic track plan documentation of a station, line section (track between station, freie Strecke in Germany).

=== Modelling of station tracks (macro view) ===

For modelling stations with their tracks without the need for modelling the complete track network, the following principles shall be taken into account:
* The OCP references the tracks that belong to the station within the sub element {{IS:Tag|propEquipment}}.
* The station tracks are modelled as tracks that are not connected to each other, but that reference the OCP they belong to as {{IS:Tag|macroscopicNode}} both, in {{IS:Tag|trackBegin}} and in {{IS:Tag|trackEnd}}.
* The station tracks should have a length (difference of {{Attr|pos}} in {{IS:Tag|trackEnd}} and {{IS:Tag|trackBegin}}) that corresponds to their usable length. If the usable length of the station track is not known or not relevant for the particular usecase, the {{Attr|pos}} attributes of {{IS:Tag|trackEnd}} and {{IS:Tag|trackBegin}} shall be both set to "0".
* Information about platforms shall be represented by a separate {{IS:Tag|platformEdge}} element within the {{IS:Tag|track}} structure. The name of the platform known by the passengers (that differs from the track name) can be indicated by the attribute {{Attr|name}}, the internal name by the attribute {{Attr|code}}.

[[file:2023-09-04 railML loop ocp.svg|400px|thumb]]

The following code ({{rml}} 2) describes an OCP in the virtual Simple Example. The OCP (''ocp01'') references two station tracks (''tr01, tr02''):
<syntaxhighlight lang="xml">
  <operationControlPoints>
    <ocp id="ocp01" name="Bf Arnau" xml:lang="de" type="operationalName">
      <additionalName name="Adamov" xml:lang="cz" type="localName"/>
      <propOperational operationalType="station" trafficType="passenger"/>
      <propService passenger="true" service="true"/>
      <propEquipment>
        <trackRef ref="tr01"/>
        <trackRef ref="tr02"/>
      </propEquipment>
      <propOther status="operational"/>
      <geoCoord coord="52.1234 15.6789" 
                epsgCode="urn:ogc:def:crs:EPSG::4326"/>
      <designator register="RL100" entry="OAR"/>
    </ocp>
  </operationControlPoints>
</syntaxhighlight>

The referenced tracks are defined under {{IS:Tag|tracks}}, and their begin and end reference the OCP ''ocp01'':
<syntaxhighlight lang="xml">
  <tracks>
    <track id="tr01" code="401" name="1">
      <trackTopology>
        <trackBegin pos="0" id="tr01_tb">
          <macroscopicNode ocpRef="ocp01"/>
        </trackBegin>
        <trackEnd pos="450" id="tr01_te">
          <macroscopicNode ocpRef="ocp01"/>
        </trackEnd>
      </trackTopology>
      <trackElements>
        <platformEdges>
          <platformEgde id="pe01" code="X1" name="1 West" pos="0" />
        </platformEdges>
      </trackElements>
    </track>
    <track id="tr02" code="402" name="2">
      <trackTopology>
        <trackBegin pos="0" id="tr02_tb">
          <macroscopicNode ocpRef="ocp01"/>
        </trackBegin>
        <trackEnd pos="450" id="tr02_te">
          <macroscopicNode ocpRef="ocp01"/>
        </trackEnd>
      </trackTopology>
    </track>
  </tracks>
</syntaxhighlight>
* The first track with the internal name "401" and the public name "1" has a platform with the internal designation "X1". The name for passengers of this platform is "1 West".

* The internal name of the second track is "402", its public name is "2". It has no platform.


With this approach, the tracks can be considered being inside a (macroscopic) node e.g. the station. The operational identifier of the track shall be in {{Attr|code}}. Such a track inside a station does not count for the distance between two ''macroscopic'' {{IS:Doc|ocp}} elements.

See [[dev:How to define track usage of a train in stations|How to define track usage of a train in stations]] for further information about the indication of station track usage. 
===National usage of track@type===
The following table reflects the usage of [[#type|@type]]:

{{includeTable}}
|notes =
All tracks in {{rml}} and the connections make up a graph. But different to many other data models, {{rml}} does NOT require points, signals and other elements to be on ''vertices'' of that graph. In {{rml}}, such elements can be located everywhere along the track (''edge'') and the number of elements a track can hold is not limited. Therefore, {{rml}} uses "long" tracks which typically cover the complete length of a line in a single {{IS:Tag|track}}.

But to ease conversion from other data sources, it is of course possible to concatenate many "short" {{IS:Tag|track}}s to one "long" track of a line. There are no syntactical or semantical reasons why that solution would be no valid {{rml}}.

The attribute {{Attr|mainDir}} is usually not very useful for single-track railway lines with regular traffic in both directions. In that case, please use value "none" in order to mark that there is no preferred driving direction on that track.

The value {{enum|unknown}} of {{@|mainDir}} has been '''removed''' with version 2.5. {{enum|unknown}} has the same meaning as a missing {{@|mainDir}}. Despite the value {{enum|unknown}} still exists in older schemas, consider it deprecated retroactively.
|semcon={{semcon|Single track railway lines shall have main driving direction {{@|mainDir}}&#61;"none" if they are used in both directions|status=proposed|proposed=2019-06-17|id=IS:004}}
}}