View source for TT:ocpTT ocpsTT trainPart

{{ElementDocu|
elementName = ocpTT

|semantics =
The element {{TT:Doc|ocpTT}} describes a single point along the train path. Normally, an {{TT:Doc|ocpTT}} belongs to a station with an arrivial and departure time. But an {{TT:Doc|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 {{IS:Doc|ocp}} defined in the infrastructure part, providing some timetable related information for it.
In the British railway timetabling system the {{TT:Doc|ocpTT}} is called ''TIPLOC'' by [//en.wikipedia.org/wiki/Network_Rail Network Rail], which is a contraction of '''TI'''ming '''P'''oint '''LOC'''ation. 

{{Deu|Das Element {{TT:Doc|ocpTT}} beschreibt den einzelnen Punkt im Zuglauf. Der {{TT:Doc|ocpTT}} entspricht einem ''Fahrzeitmesspunkt''. Ein Fahrzeitmesspunkt kann, muss aber keine Betriebsstelle sein. Meist ist ein {{TT:Doc|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 {{TT:Doc|ocpTT}} verweist immer auf einen in der Infrastruktur definierten {{IS:Doc|ocp}} und beschreibt dessen Verwendung im Fahrplan. Als Regel darf jeder {{TT:Doc|ocpTT}} nur einmal innerhalb eines {{TT:Doc|trainPart}}s auftauchen.}}

|parent = {{TT:Tag|ocpsTT|trainPart}}
|childs = {{TT:Tag|times|ocpTT ocpsTT trainPart}}, {{TT:Tag|connections}}, {{TT:Tag|statistics}}, {{TT:Tag|sectionTT}}, {{tag|tt|alternativeSectionsTT}} {{intro|2.5}}, {{TT:Tag|stopDescription|ocpTT ocpsTT trainPart}}, {{tag|TT|originalTrackInfo}} {{intro|2.5}}, {{any}}
|maxocc=∞
|inheritedAttributes=''None''
|ownAttributes =
{{InheritRef
|attributeName = ocpRef
|contextLink = {{IS:Doc|ocp}}
|notes_en =
}}

{{InheritRef
|attributeName = trackRef
|contextLink = {{IS:Doc|track}}
|notes_en =
}}
* {{Attr|sequence}}: {{Intro|2.2}} This number defines the order of the {{TT:Doc|ocpTT}} elements inside a {{TT:Doc|trainPart}} which is supposed to be chronological.

* {{Attr|trackInfo}}: Textual description of station track for information purposes. The real track and platform information can and should be identified via the {{Attr|trackRef}} attribute.

* {{Attr|ocpType}}: This is a mixture of two informations describing the action of the {{TT:Doc|train}} at this {{TT:Doc|ocpTT}}. Possible values are:
:* {{Enum|stop}} The {{TT:Doc|train}} is stopping at this {{TT:Doc|ocpTT}}.
:* {{Enum|pass}} The {{TT:Doc|train}} is ''not'' stopping at this {{TT:Doc|ocpTT}} and will pass.
:* {{Enum|begin}} {{Depr|2.2}} If the {{TT:Doc|trainPart}} begins at this {{TT:Doc|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 {{TT:Doc|train}}s.
:* {{Enum|end}} {{Depr|2.2}} If the {{TT:Doc|trainPart}} ends at this {{TT:Doc|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 {{TT:Doc|train}}s.

* {{Attr|remarks}}: This is a free attribute for further descriptions.{{human}}

* {{Attr|trainReverse}}: This is true if the {{TT:Doc|train}} changes its direction of travel at this station which is sometimes shown by a sign "&harr;" in printouts for passengers. For indicating that the {{RS:Doc|formation}} starts in reversed order, you will have to set the attribute {{Attr|orientationReversed}} in the {{TT:Doc|formationTT}}. If the train reverses at an intermediate station and restarts in reversed order, you will have to build a new {{TT:Doc|trainPart}} with 
** {{Attr|trainReverse}} set at the last {{TT:Doc|ocpTT}} of the previous {{TT:Doc|trainPart}} and 
** {{Attr|trainReverse}} set at the first {{TT:Doc|ocpTT}} and the attribute {{Attr|orientationReversed}} set in the {{TT:Doc|formationTT}} of the new {{TT:Doc|trainPart}}.
:For more information, see [[TT:Reversing_trains_and_formations | Reversing trains and formations]].

* {{Attr|alignment}}: This describes the alignment of the arriving train in relation to the place on a {{IS:Doc|track}} referenced by {{Attr|ocpRef}}. Possible values are:
:* {{Enum|head}} - The head of the train (front of first vehicle) is located at the <{{IS:Doc|ocp}}> referenced by {{Attr|ocpRef}}, possibly shifted by {{Attr|offset}} metres.
:* {{Enum|center}} - The centre of the train (mid point concerning the train length) is located at the <{{IS:Doc|ocp}}> referenced by {{Attr|ocpRef}}, possibly shifted by {{Attr|offset}} metres.
:* {{Enum|rear}} - The end of the train (back of last vehicle) is located at the <{{IS:Doc|ocp}}> referenced by {{Attr|ocpRef}}, possibly shifted by {{Attr|offset}} metres.
:The default value for {{Attr|alignment}} is {{Enum|center}} if the attribute is not specified.

* {{Attr|offset}}: This describes the offset of the stopping point in relation to the place on a {{IS:Doc|track}} referenced by {{Attr|ocpRef}} in metres. The default value is zero (no offset).

* {{Attr|shuntingTime}}: {{Depr|2.5}} This is the shunting time used inside a station in case the train is shunted there. 

{{InheritAnyAttribute
|anyAttribute =
|anyAttribute_de =
}}

|constraints =
* {{Attr|sequence}}: {{RailMLType|tPositiveCounter}}, mandatory
* {{Attr|ocpRef}}: {{RailMLType|tGenericRef}}, mandatory
* {{Attr|trackRef}}: {{RailMLType|tGenericRef}}, optional
* {{Attr|trackInfo}}: {{XsdType|string}}, optional
* {{Attr|ocpType}}: {{RailMLType|tOcpTTType}}<br>Optional
* {{Attr|remarks}}: {{XsdType|string}}, optional
* {{Attr|trainReverse}}: {{XsdType|boolean}}, optional
* {{Attr|alignment}}: {{RailMLType|tTrainAlignment}}, optional
* {{Attr|offset}}: {{RailMLType|tLengthM}}, optional
* {{Attr|shuntingTime}}: {{XsdType|duration}}, optional {{Depr|2.5}}
|semcon=
{{semcon|The attribute sequence is shall be increasing according to the train path.<br/> {{Deu|Das Attribut sequence muss ansteigend entsprechend dem Zuglauf sein.}}|status=approved|proposed=2018-10-25|approved=2019-06-20|id=TT:002}}

|bestpractice = 
===How to define track and platform usage in stations===

The {{Attr|trackRef}} can reference either a ''microscopic'' {{IS:Tag|track}} inside the {{IS:Tag|ocp}} (containing a {{IS:Tag|crossSection}}) or a ''macroscopic'' station track (one where {{IS:Tag|trackBegin}} and {{IS:Tag|trackEnd}} contain {{IS:Tag|macroscopicNode}}s referencing the same {{IS:Tag|ocp}}).

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. 

===Train reverses in a station===

The train is stopping in Zurich (referenced {{IS:Doc|ocp}}) on track 12 (no reference here). It is stopping with its head 10 meters before actually reaching the cross section of this {{IS:Doc|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. In this example the train path is split into two subsequent {{TT:Doc|trainPart}}s because the position of the train (attributes {{Attr|alignment}} and {{Attr|offset}}) is different for arrival and departure. 

<syntaxhighlight lang=xml>

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

</syntaxhighlight>

On the difference between {{TT:Doc|ocpTT}}/@{{Attr|trainReverse}} and {{TT:Doc|formationTT}}/@{{Attr|orientationReversed}}, see [[TT:Reversing_trains_and_formations | Reversing trains and formations]].<br>
See also:
* [[Dev:How_To_Reference_Infrastructure | How to reference infrastructure]]
* [[dev:How to define track usage of a train in stations|How to define track usage of a train in stations]]

===Depicting track changes===
{{Intro|2.5}}To see how to handle the case when the actual track differs from the originally scheduled track, see the description of [[TT:originalTrackInfo#Depicting_track_changes|depicting track changes]].

==={{@|ocpType}} at the first and last stop===
Software that reads a {{rml}} document should also be able to handle {{TT:Tag|trainPart}}'s whose first and/or last {{TT:Tag|ocpTT}} has the value {{@|ocpType}} specified as {{enum|pass}}. This situation can occur in different scenarios. If, for example, incoming or outgoing traffic is described in {{rml}}, it is often the case that the first {{IS:Tag|ocp}} does not represent a stop, but rather encodes the time at which a train enters or leaves the network. Another reason may be that data on the {{TT:Tag|trainPart}} changes and this must therefore be broken. You should therefore generally not make the assumption that a train has a stop at the beginning or end of the {{TT:Tag|trainPart}}.

According to the semantic constraint [[TT:times_ocpTT_ocpsTT_trainPart#Semantic_Constraints_/_Semantic_Bestraints|TT:014]], no arrival time is specified in such a case, neither on the last {{TT:Tag|ocpTT}} of the ending {{TT:Tag|trainPart}} nor on the first {{TT:Tag|ocpTT}} of the beginning {{TT:Tag|trainPart}}. Make sure that the times do not contradict each other, i.e. ensure that also the semantic constraints [[TT:times_ocpTT_ocpsTT_trainPart#Semantic_Constraints_/_Semantic_Bestraints|TT:015 and TT:016]] are taken into account.

{{Deu| Eine Software, die ein {{rml}} Dokument liest, sollte auch mit {{TT:Tag|trainPart}}'s umgehen können, deren erster und/oder letzter {{TT:Tag|ocpTT}} als {{@|ocpType}} den Wert {{enum|pass}} angegeben hat. Diese Situation kann in unterschiedlichen Szenarien auftreten. Wenn beispielsweise einbrechende oder ausbrechende Verkehre in {{rml}} beschrieben werden, kommt es häufig vor, dass der erste {{IS:Tag|ocp}} keinen Halt darstellt, sondern vielmehr die Zeit kodiert zu der ein Zug in das Netz eintritt, oder dieses wieder verlässt. Ein anderer Grund kann sein, dass sich Daten am {{TT:Tag|trainPart}} ändern, und dieser deswegen gebrochen werden muss. Man sollte also generell nicht die Annahme treffen, dass ein Zug am Anfang oder Ende es {{TT:Tag|trainPart}} einen Halt hat.

Entsprechend des semantic constraints [[TT:times_ocpTT_ocpsTT_trainPart#Semantic_Constraints_/_Semantische_Beschränkungen|TT:014]] wird in einem solchen Fall keine Ankunftszeit angegeben, weder am letzen {{TT:Tag|ocpTT}} des endenden {{TT:Tag|trainPart}} noch am ersten {{TT:Tag|ocpTT}} des beginnenden {{TT:Tag|trainPart}}. Es ist darauf zu achten, dass die Zeiten sich nicht widersprechen, die semantic constraints [[TT:times_ocpTT_ocpsTT_trainPart#Semantic_Constraints_/_Semantic_Bestraints|TT:015 und TT:016]] sind also ebenso zu beachten.}}

===Train(part)s with one <ocpTT> only===
Normally, each {{TT:Tag|train}} has at least one {{TT:Tag|trainPart}} with at least two {{TT:Tag|ocpTT}}s. However, it is allowed that a {{TT:Tag|trainPart}} has only one {{TT:Tag|ocpTT}}. In this special case, what is mentioned at [[TT:times‎]] concerning {{Attr|arrival}} at first and {{Attr|departure}} at last {{TT:Tag|ocpTT}} applies at the same time: The train arrives from outside and immediately departs to outside the {{rml}} file. In very rare cases, this is used, for instance, to express only an occupation of a station track by a train which is not considered further. You can imagine a whole {{rml}} file which only expresses the station timetable of one station: All trains arrive from and depart to "nowhere". You should keep that special case in mind if you handle {{rml}} files on import.

===Specifying shunting times===
As of version 2.5 the attribute {{@|shuntingTime}} of the {{TT:Tag|ocpTT}} was declared deprecated. In order to specify a shunting time at a stop please refer to the attribute {{@|shuntingTime|TT:stopTimes}} of {{TT:Tag|stopTimes}}.
}}