IS:track

From railML 2 Wiki
Revision as of 16:44, 21 July 2017 by RailML Coord Documentation (talk | contribs) (intro- und depri-Tags vor 2.2 entfernt)
Jump to navigation Jump to search


track
 


Scheme description / Schemenbeschreibung

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

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 elements contain all information about the track's topology and the trackside elements associated with that track.

Attributes of track / Attribute von track

  • id: XML-file-wide unique, machine-interpretable identity, required for later referencing that element internally. For a detailed explanation see Dev:identities.
    XML-Datei-weit eindeutige, maschineninterpretierbare Identität, die für die spätere interne Referenzierung dieses Elements erforderlich ist. Für eine detaillierte Erklärung siehe Dev:identities.
  • code (introduced with version 2.1): Machine-interpretable string (e.g. an abbreviation) used for identification of the object across exchange partners, usecase specific uniqueness constraints may apply. Please see our description of the differences between id, code and human-readable identifiers.
    Maschineninterpretierbare Zeichenkette (z.B. Abkürzung), die zur Identifizierung des Objekts auch bei Austauschpartnern verwendet wird, wobei spezifische Eindeutigkeitsbeschränkungen gelten können. Bitte beachten Sie unsere Erläuterung zu den Unterschieden zwischen id, code and menschenlesbaren Kennzeichnungen.
  • name: Established, human-readable short string, giving the object a name. Not intended for machine interpretation, please see our notice on human interpretable data fields.
    Etablierte, menschenlesbare kurze Zeichenkette, die das Objekt benennt. Nicht zur maschinellen Interpretation bestimmt, siehe Hinweise zu menschenlesbaren Datenfeldern.
  • description: Human-readable, more detailed description as addition to the name. It should give additional explanations or hints to the contents of this element. Not intended for machine interpretation, please see our notice on human interpretable data fields.
    Menschenlesbare, detailliertere Beschreibung als Ergänzung zu name. Sie soll zusätzliche Erläuterungen oder Hinweise auf den Inhalt dieses Elements geben. Nicht zur maschinellen Interpretation bestimmt, siehe Hinweise zu menschenlesbaren Datenfeldern.
  • xml:lang (introduced with version 2.1): This is a unique identifier of language. It uses basically the language standard IETF BCP 47 (external link) which may be different to ISO 639-1 (external link) or ISO 639-2 (external link). For mapping hints see relation to other standards (external link).
    This defines the language used for name and description. Use <additionalName> to provide a name and/or description in other languages.
  • type: This is a classification of the track. Possible values are:
  • mainTrack: This is a regular track a of line used for frequent passenger and freight transport.
    Deutschland: durchgehendes Hauptgleis; üblicherweise 1 bei eingleisigen und 2 bei zweigleisigen Strecken
  • secondaryTrack: This is a track not frequently used (e. g. loops for overtaking and/or crossing in stations).
    Deutschland: Nebengleis
  • connectingTrack: This is a transfer track from one to another track e. g. in branches, points or cross overs.
    Deutschland: Verbindungsgleis
  • sidingTrack: This is a siding.
    Deutschland: Abstellgleis
  • stationTrack: This is a track in a station, possibly with platforms.
    Deutschland: Bahnhofsgleis (Hauptgleis im Bahnhof)
  • other:anything: Any value that does not fit any value from the previous enumeration list, fulfilling the constraint: at minimum two characters, whitespace is not allowed. Please, apply Dev:usingAny accordingly.
  • mainDir: This is the preferred driving direction on that track.
  • up This track is mostly used in the track definition direction.
  • down This track is mostly used opposite the track definition direction.
  • unknown The preferred driving direction of the track is not known.
  • none There is no preferred driving direction for the track.

Syntactic Constraints / Syntaktische Beschränkungen

  • id: xs:ID, required
    a string, starting with a letter (a..zA..Z) or an underscore (_),
    followed by a non-colonized and non-spaced string consisting of letters, digits, points (.), dashes (-) or underscores (_)
  • code: xs:string, optional
  • name: xs:string, optional
  • description: xs:string, optional
  • xml:lang: xs:language, language identification, optional
  • mainDir optional
  • type optional

Best practice & Examples / Empfohlene Anwendung & Beispiele

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 <propEquipment>.
  • The station tracks are modelled as tracks that are not connected to each other, but that reference the OCP they belong to as <macroscopicNode> both, in <trackBegin> and in <trackEnd>.
  • The station tracks should have a length that corresponds to their usable length.
  • The name of the platform known by the passegers would be in the attribute name (if not defined as element <platformEdge>)

The following code describes an OCP in the virtual Simple Example. The OCP (ocp01) references two station tracks (tr01, tr02):

  <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="PLC" entry="DE-67543"/>
    </ocp>
  </operationControlPoints>

The referenced tracks are defined under <tracks>. They are marked as "stationTrack" and their begin and end reference the OCP ocp01:

  <tracks>
    <track id="tr01" name="1" code="401" type="stationTrack">
      <trackTopology>
        <trackBegin pos="0" id="tr01_tb">
          <macroscopicNode ocpRef="ocp01"/>
        </trackBegin>
        <trackEnd pos="450" id="tr01_te">
          <macroscopicNode ocpRef="ocp01"/>
        </trackEnd>
      </trackTopology>
    </track>
    <track id="tr02" name="2" code="402" type="stationTrack">
      <trackTopology>
        <trackBegin pos="0" id="tr02_tb">
          <macroscopicNode ocpRef="ocp01"/>
        </trackBegin>
        <trackEnd pos="450" id="tr02_te">
          <macroscopicNode ocpRef="ocp01"/>
        </trackEnd>
      </trackTopology>
    </track>
  </tracks>

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 code and the name of the platform known by the passengers can be placed in the attribute name (if not explicitly defined via <platformEdge> elements). Such a track inside a station does not count for the distance between two macroscopic ocp elements.

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>.

But to ease conversion from other data sources, it is of course possible to concatenate many "short" <track>s 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.