TT:stopDescription ocpTT ocpsTT trainPart: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(TT:stopActivities vorbereitet — bitte erst bei Veröffentlichung von Version 2.4 sichtbar machen!)
(Undocumented enumeration items)
Line 17: Line 17:


* {{Attr|onOff}}: This describes, if passengers/goods are not supposed to enter or leave the train. <br> {{Deu|z.B. "Halt nur zum Einsteigen"}} <br> Possible values are:
* {{Attr|onOff}}: This describes, if passengers/goods are not supposed to enter or leave the train. <br> {{Deu|z.B. "Halt nur zum Einsteigen"}} <br> Possible values are:
{{missing information|user=[[User:Ferri Leberl|Ferri Leberl]] ([[User talk:Ferri Leberl|talk]]) 16:19, 25 April 2018 (CEST)|topic=the semantics of the enumeration items}}
:* {{Enum|both}}
:* {{Enum|both}}
:* {{Enum|on}}
:* {{Enum|on}}

Revision as of 15:19, 25 April 2018


stopDescription
 


Scheme description / Schemenbeschreibung

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

Multiplicity / Anzahl

[1..1]

Semantics / Bedeutung

The element stopDescription describes data concerning the stop a the certain ocpTT.

Das Element stopDescription beschreibt Daten, die den Halt im aktuellen ocpTT charakterisieren.

Attributes of stopDescription / Attribute von stopDescription

  • commercial: This characterizes the stop as either commercial or operational stop.
    Verkehrshalt / Betriebshalt
  • stopOnRequest: This indicates a commercial stop, depending on a certain demand. A stop on request is a special kind of a commercial stop. This attribute is not to be defined if commercial is set to false.
    Bedarfshalt: Ein Bedarfshalt ist eine besondere Form des Verkehrshalts. Das Attribut stopOnRequest ist nur anzugeben, wenn commercial="true" ist.
  • onOff: This describes, if passengers/goods are not supposed to enter or leave the train.
    z.B. "Halt nur zum Einsteigen"
    Possible values are:

Missinginformation.png In this article there is information missing with respect to the semantics of the enumeration items. Please help improving the railML® wiki by filling the gaps. Possibly, you will find further details on the discussion pageFerri Leberl (talk) 16:19, 25 April 2018 (CEST)
  • both
  • on
  • off
  • purpose: This describes the reason for the stop in a detailed but not predefined way.
  • guaranteedPass: (introduced with version 2.2) This indicates a forbidden stop for heavy goods trains, otherwise they would not be able to get off.
    garantierte Durchfahrt
  • operationalStopOrdered: (introduced with version 2.2) This indicates that the stop is requested by the operator (Train Operating Company), i. e. it is not a commercial stop concerning traffic (not for passengers, not for payload) but anyway the stop is ordered for operational reasons of the operator. This attribute is not to be defined if commercial is set to true.
    bestellter Betriebshalt: Das Attribut ist nur anzugeben, wenn commercial="false" ist.
  • operatingPeriodRef: This refers to the id attribute of the associated <operatingPeriod> element.
    Used to reduce the operating days of the stop compared to the operating days of the train part. If not defined, the stop applies to all operating days of the parent train part.
  • stopPostRef: This refers to the id attribute of the associated <stopPost> element.
    (introduced with version 2.2)
  • xs:anyAttribute: This provides an extension point for non-railML® attributes in a foreign namespace. How to use it?

Syntactic Constraints / Syntaktische Beschränkungen

  • stopOnRequest: xs:boolean, optional, commercial="true" should be set
  • onOff: restriction of xs:string (both, on, off), optional
  • operationalStopOrdered: xs:boolean, optional, commercial="false" should be set

Best practice & Examples / Empfohlene Anwendung & Beispiele

General traffic stop | Verkehrshalt

<ocpTT ocpRef='…' ocpType='stop'>
  <times scope='scheduled' arrival='12:30:32' departure='12:31:02'/>
  <stopDescription commercial='true' stopOnRequest='false'/>
</ocpTT>

Stop on request / on demand | Bedarfshalt

<ocpTT ocpRef='…' ocpType='stop'>
  <times scope='scheduled' arrival='13:33:26' departure='13:33:56'/>
  <stopDescription commercial='true' stopOnRequest='true'/>
</ocpTT>

Operational stop infrastructure, by IM | Betriebshalt EIU

<ocpTT ocpRef='…' ocpType='stop'>
  <times scope='scheduled' arrival='12:51:25' departure='12:51:55'/>
  <stopDescription commercial='false' operationalStopOrdered='false'/>
</ocpTT>

Operational stop by TOC | Betriebshalt EVU

<ocpTT ocpRef='…' ocpType='stop'>
  <times scope='scheduled' arrival='12:45:52' departure='12:59:18'/>
  <stopDescription commercial='false' operationalStopOrdered='true'/>
</ocpTT>

Stop to alight only | Halt nur zum Aussteigen

<ocpTT ocpRef='…' ocpType='stop'>
  <times scope='scheduled' arrival='12:58:23' departure='13:00:23'/>
  <stopDescription commercial='true' stopOnRequest='false' on-Off='off'/>
</ocpTT>

Notes / Anmerkungen

It is not intended to write different stop types at the same station. Concerning the usualities of railway operation:

  • If there are reasons for both a traffic stop and an operational stop, a traffic stop shall be declared.
  • If an operational stop becomes necessary by IM as well as by TOC, it will be declared as an operational stop by TOC (ordered operational stop).

A stop on request is a special case of a traffic stop.

If a stop does not apply to all operating days of the train - i. e. the train runs through at several days - the attribute operatingPeriodRef can be used to reduce the operating days of the stop against the operating days of the train. However, be aware that other given attributes as run times, supplements etc. become incorrect by this practice. Also, it can only be used to change between a certain stop and run through but not to switch between two different stop types depending on the days of operation. Therefore, many applications would probably split the train into two instead of using operatingPeriodRef.

Es ist nicht vorgesehen, mehrere Haltearten gleichzeitig anzugeben. Entsprechend den Gepflogenheiten im Eisenbahnbetrieb gelten:

  • Wenn Gründe für einen Verkehrs- und einen Betriebshalt gleichzeitig vorliegen, wird ein Verkehrshalt angegeben.
  • Wenn ein Betriebshalt sowohl durch den Infrastrukturbetreiber als auch durch den Fahrzeugbetreiber erforderlich wird, wird er als Betriebshalt durch Fahrzeugbetreiber ausge-wiesen (bestellter Betriebshalt).

Ein Bedarfshalt ist eine besondere Form des Verkehrshaltes.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.