Home » railML newsgroups » railml.timetable » Haltezwecke / Stop descriptions
Re: Haltezwecke / Stop descriptions [message #1589 is a reply to message #1588] Wed, 24 May 2017 19:46 Go to previous messageGo to previous message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 311
Registered: August 2008
Senior Member
Dear all,

in preparation of the meeting on 1st June I quickly set up a suggestion for the extension of railML from version 2.4 with additional stopping information. It is based on the aforementioned comparison of SBB, ÖBB and DB and what is common between at least two of the three.

I suggest a tAdditionalStopInfo (simple type enumeration, see below) with the following values:

collect, drop, split, join, crewChg, crewBreak, reverse, runAround, engineChg, staple, occupation, block, crossing, station, power, wagonCheck, axleChange, borderCheck, photo, catering, movAuth, releaseLine, shuntPerm, misc, other:...

The full suggestion with explanations and notes is here:
\timetable\railML 2.4\Haltegrund --> Vorschlag Erweiterung Halteinfo ab r2-4.pdf

Examples for usage:
1) Traffic stop for collecting and dropping wagons (freight train):

<stopDescription commercial='true' stopOnRequest='false'>
<stopTimes minimalTime='PT30S'/>
<addStopInfo info='collect'/>
<addStopInfo info='drop'/>
</stopDescription>

2) Operational stop for crew change (daily) and a crossing on Mon-Fri only:

<stopDescription commercial='false' operatingPeriodRef='op_Mon-Fri'>
<addStopInfo info='crewChg'/>
<addStopInfo info='crossing'/>
<addStopInfo info='releaseLine'/>
<addStopInfo info='movAuth'/>
</stopDescription>
<stopDescription commercial='false' operatingPeriodRef='op_Sat+Sun'>
<addStopInfo info='crewChg'/>
</stopDescription>

--> If several <stopDescription>s are given, they must have disjunctive @operatingPeriodRef.
--> All @operatingPeriodRef must be subsets of the <operatingPeriodRef> of the <trainPart>.

---
Definition of the enumeration type:

<xs:simpleType name="tAdditionalStopInfo">
<xs:union>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="collect" />
<xs:enumeration value="drop" />
<xs:enumeration value="split" />
<xs:enumeration value="join" />
...
<xs:enumeration value="misc" />
</xs:restriction>
</xs:simpleType>
<xs:simpleType>
<xs:restriction base="rail:tOtherEnumerationValue" />
</xs:simpleType>
</xs:union>
</xs:simpleType>

All names and titles may be regarded as working titles only.

Best regards,
Dirk.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Timetable data elements for railVIVID
Next Topic: addendum to <stopDescription> in railML2.4
Goto Forum:
  


Current Time: Fri Mar 29 16:43:00 CET 2024