TT:ocpTT

From wiki.railML.org
Revision as of 16:57, 10 February 2016 by Christian Rößiger (talk | contribs) (any element added)
Jump to: navigation, search

ocpTT
 


Scheme description / Schemenbeschreibung / Description du schéma

Position of ocpTT in the XML-Tree / Position von ocpTT im XML-Baum / position de ocpTT dans l’aborescence XML

Multiplicity / Anzahl / Multiplicité

[1..1]

Semantics / Bedeutung / Sémantique

The element ocpTT describes a single point along the train path. Normally, an ocpTT belongs to a station with an arrivial and departure time. But an ocpTT could also be a blocking signal with or without passing time, or some control point on the train path. It is always referencing a certain ocp defined in the infrastructure part, providing some timetable related information for it. As a rule, no ocpRef is allowed to occur more than one time in the same <trainPart>. In the British railway timetabling system the ocpTT is called TIPLOC by Network Rail, which is a contraction of TIming Point LOCation.

Das Element ocpTT beschreibt den einzelnen Punkt im Zuglauf. Der ocpTT entspricht einem Fahrzeitmesspunkt. Ein Fahrzeitmesspunkt kann, muss aber keine Betriebsstelle sein. Meist ist ein ocpTT gleichzusetzen mit einen Bahnhof und der dortigen Ankunfts- und Abfahrtszeit. Es kann aber genauso gut ein Blocksignal mit oder ohne Durchfahrtszeit oder auch ein beliebiger Messpunkt auf der Strecke sein. Der jeweilige ocpTT verweist immer auf einen in der Infrastruktur definierten ocp und beschreibt dessen Verwendung im Fahrplan. Als Regel darf jeder ocpTT nur einmal innerhalb eines trainParts auftauchen.

Attributes of ocpTT / Attribute von ocpTT / Attributs de 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.
  • 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.
  • trainReverse: This is true if the train changes its direction of travel at this station which is often shown by a '<->' sign in printouts. For indicating that the formation starts in reversed order, you will have to build a new trainPart with trainReverse set at the first ocpTT and the attribute orientationReversed set in the formationTT.
  • alignment: This describes the alignment of the arriving train in relation to the point on a track referenced by ocpRef. Possible values are:
  • head
  • center
  • rear
  • offset: This describes the offset of the stopping point in relation to the point on a track referenced by ocpRef.
  • shuntingTime: This is the driving time used inside a station.
  • xs:anyAttribute: This provides an extension point for non-railML attributes in a foreign namespace. How to use it?

Syntactic Constraints / Syntaktische Beschränkungen / Contraintes syntactiques

  • ocpType optional
  • alignment optional
  • offset optional

The sequence of the ocpTT elements inside a trainPart has to be according to the train path.
Die Reihenfolge der ocpTT innerhalb eines Teilzuges trainPart muss mit der Abfolge der Punkte im Zuglauf übereinstimmen.

Best practice & Examples / Empfohlene Anwendung & Beispiele / Bonnes pratiques & exemples

The train is stopping in Zurich (referenced ocp) on track 12 (no reference here). It is stopping with its head 10 meters before actually reaching the crossSection of this ocp, which is assumed to be located at the buffer stop in the main hall of this station. Then the train is changing direction and leaving.

 ...
 <ocpTT sequence="35" ocpRef="_85ZUE" ocpType="stop" trackInfo="12" alignment="head" offset="-10">
   <times scope="scheduled" arrival="10:56:00.0"/>
 ...
 <ocpTT sequence="1" ocpRef="_85ZUE" ocpType="stop" trackInfo="12" alignment="rear" trainReverse="true" offset="10">
   <times scope="scheduled" departure="11:04:00.0"/>

Notes / Anmerkungen / Notes

On the difference between ocpTT/@trainReverse and formationTT/@orientationReversed, see Reversing trains and formations.
See also How to reference infrastructure

Open issues / Offene Punkte/Pedenzen / Questions ouvertes

Not yet described. / Noch nicht beschrieben. / Pas encore décrit.