IS:stopPost

From railML 2 Wiki
Revision as of 20:52, 10 July 2018 by RailML Coord Governance (talk | contribs) (Constraints for ocpRef fixed, constraints for controllerRef removed)
Jump to navigation Jump to search


stopPost
 


Scheme description / Schemenbeschreibung

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

Multiplicity / Anzahl

[1..1]

Semantics / Bedeutung

The element <stopPost> is used to mark a position on a track, where a train, which fulfills certain criteria, needs to stop in order to change passengers or because of other operational rules.

Attributes of stopPost / Attribute von stopPost

  • 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): This is a short string for typical, specific abbreviations, used in different systems with the same understanding.
  • name: This is a short name for the current item.
  • description: This is a more detailed description as addition to the short name. It shall allow a short overview or hints to the contents of this data set.


  • 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 is used for defining name and description.


  • pos: This is the position on a track defined as distance from its start (trackBegin) regardless the "absolute mileage" in @absPos.
    Das ist die Position des Elements auf einem Track i.S. der realen Entfernung zum trackBegin. Sie ist damit unabhängig von der mit absPos modellierten Strecken-Kilometrierung.
🗒️ For an explanation of the differences between @pos and @absPos see <mileageChange>
  • absPos: This is the position on a track as absolute mileage/chainage.
    Das ist die Position des Elements im Referenzsystem der Strecken-Kilometrierung.
🗒️ For an explanation of the differences between @pos and @absPos see <mileageChange>
  • absPosOffset (deprecated with version 2.1): The semantics of this attribute aren't very clear. It seems to be redundant to the definitions with mileageChanges in "overlapping regions".
  • dir: This defines the validity of <stopPost> along the track. Possible values are:
  • none: <stopPost> has no direction restriction.
  • up: This denotes the direction from the <trackBegin> to the <trackEnd> (increasing relative position values).
  • down: This goes opposite to up (decreasing relative position values).
  • both: <stopPost> is valid in both directions.
  • unknown: <stopPost> is restricted to a certain direction, but this direction is not known.
  • ruleCode: code for this element in the rule book, combination of letters and numbers and space allowed, e.g. Ne5, GA, SFRS/E
  • trainRelation: Reference to the part of the train from where on the stop post is valid. Normally, a stop post relates to the head of the train.
  • platformEdgeRef: This refers to the id attribute of the associated <platformEdge> element.
  • trainLength: Set this value if the stop post is only valid for trains with a certain train length. If the stop post is valid for trains with all lengths, don't use this attribute.
  • axleCount: Set this value if the stop post is only valid for trains with a certain number of axles.
  • wagonCount: Set this value if the stop post is only valid for trains with a certain number of wagons.
  • verbalConstraints: Set this value if the stop post is only valid for trains fulfilling a certain verbal constraint.
  • virtual: Marks a stop post being virtual if there is no physical representation along the track.
  • ocpRef: This refers to the id attribute of the associated <ocp> element.

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


  • pos: tLengthM (xs:decimal, 6 fraction digits, length value measured in meter); required; must be greater than or equal to zero, less than or equal to the track's length
  • absPos: tLengthM (xs:decimal, 6 fraction digits, length value measured in meter); optional
  • absPosOffset: xs:decimal, 6 fraction digits, length value measured in meter; optional
  • dir: xs:string, generic type for more constrained direction statements: enumeration up, down, unknown; derived from tLaxDirection; optional
  • ruleCode: xs:string
  • trainLength optional
  • axleCount optional
  • wagonCount optional

Best practice & Examples / Empfohlene Anwendung & Beispiele

Not yet described. / Noch nicht beschrieben.

Notes / Anmerkungen

General information on positioning

Positive pos values describe the distance from the track's begin. The track length is derived from the pos value in <trackEnd>.

The absolute mileage refered to by absPos is usually found on technical drawings of the track layout or on mileage posts next to the track.

In order to find out which <stopPost> elements belong to one specific <ocp>, you need to check the ocpRef attribute of all <stopPost> elements. A reversed way of referencing from <ocp> to <stopPost> has been discussed in the forum. Since there was no urgent need, it was decided that the current solution is sufficient and the concept of referencing will be revised with railML® version 3.1.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.