TT:ocpTT ocpsTT patternTrainPart

ocpTT
 

💡 (introduced with version 2.5) This element was introduced with version 2.5. Dieses Element wurde mit Version 2.5 eingeführt.

Scheme description / Schemenbeschreibung

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

• Parent: <ocpsTT>
• Children: <times>, <sectionTT>, <alternativeSectionsTT>, <stopDescription>, <xs:any>

Multiplicity / Anzahl

[1..∞]

Semantics / Bedeutung

(introduced with version 2.5)
 
Please, be aware of the semantic constraint(s)!

Attributes of ocpTT / Attribute von ocpTT

• ocpRef: This refers to the id attribute of the associated ocp element.

• trackRef: This refers to the id attribute of the associated track element.
• sequence: (introduced with version 2.2) This number defines the order of the ocpTT elements inside a trainPart which is supposed to be chronological.

• trackInfo: Textual description of station track for information purposes. The real track and platform information can and should be identified via the trackRef attribute.

• ocpType: This is a mixture of two informations describing the action of the train at this ocpTT. Possible values are:

• stop The train is stopping at this ocpTT.
• pass The train is not stopping at this ocpTT and will pass.
• begin (deprecated with version 2.2) If the trainPart begins at this ocpTT and is not part of a longer train path, this value is used. The start of a train path should be detected by parsing the trains.
• end (deprecated with version 2.2) If the trainPart ends at this ocpTT and is not part of a longer train path, this value is used. The end of a train path should be detected by parsing the trains.

• remarks: This is a free attribute for further descriptions.

💡 Please take into account our references to human-intepretable data fields. Bitte berücksichtigen Sie unsere Hinweise zu menschen-intepretierbaren Datenfeldern.

• trainReverse: This is true if the train changes its direction of travel at this station which is sometimes shown by a sign "↔" in printouts for passengers. For indicating that the formation starts in reversed order, you will have to set the attribute orientationReversed in the formationTT. If the train reverses at an intermediate station and restarts in reversed order, you will have to build a new trainPart with
  • trainReverse set at the last ocpTT of the previous trainPart and
  • trainReverse set at the first ocpTT and the attribute orientationReversed set in the formationTT of the new trainPart.

For more information, see Reversing trains and formations.

• alignment: This describes the alignment of the arriving train in relation to the place on a track referenced by ocpRef. Possible values are:

• head - The head of the train (front of first vehicle) is located at the <ocp> referenced by ocpRef, possibly shifted by offset metres.
• center - The centre of the train (mid point concerning the train length) is located at the <ocp> referenced by ocpRef, possibly shifted by offset metres.
• rear - The end of the train (back of last vehicle) is located at the <ocp> referenced by ocpRef, possibly shifted by offset metres.

The default value for alignment is center if the attribute is not specified.

• xs:anyAttribute: This provides an extension point for non-railML^® attributes in a foreign namespace. How to use it?

Syntactic Constraints / Syntaktische Beschränkungen

• sequence: xs:positiveInteger, mandatory
• ocpRef: xs:IDREF, mandatory
• trackRef: xs:IDREF, optional
• trackInfo: xs:string, optional
• ocpType: restriction of xs:sting; stop, pass, begin (deprecated with version 2.2), end (deprecated with version 2.2)
  Optional
• remarks: xs:string, optional
• trainReverse: xs:boolean, optional
• alignment: restriction of xs:string; generic type for the alignment of a train relative to some objective in the used context (head, center, rear), optional

Semantic Constraints / Semantische Beschränkungen

Semantic Constraint "TT:002":   The attribute sequence is shall be increasing according to the train path. Das Attribut sequence muss ansteigend entsprechend dem Zuglauf sein.   Proposed on October 25th 2018 Approved on June 20th 2019 FIXME: add Link to discussion! Please, recognize our guidelines on semantic constraints

Best practice & Examples / Empfohlene Anwendung & Beispiele

Not yet described. / Noch nicht beschrieben.

Notes / Anmerkungen

Not yet described. / Noch nicht beschrieben.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.