Home » railML newsgroups » railml.timetable » Haltezwecke / Stop descriptions
|Haltezwecke / Stop descriptions [message #1437]
||Wed, 02 November 2016 13:26
Registered: November 2016
Eine Frage bezüglich der Halte-Beschreibungen: Im RailML 2.3 kann mit dem Element <stopDescription> ein Halt beschrieben werden. Der effektive Haltezweck lässt sich nur grob mit dem Attribut „onOff" definieren. Bei der SBB kennen wir aber aktuell über 80 Haltezwecke. Wo könnten diese abgebildet werden? Im Attribut „purpose" oder sollte man ein neues Listen-Attribut definieren welches erweiterbar ist? Gibt es hier bereits andere Lösungen?
Eine Liste der SBB Haltezwecke ist angehängt.
A question regarding the stop descriptions. In RailML 2.3, the element <stopDescription> is used to describe a stop. The effective purpose of the stop can only defined roughly using the attribute "onOff". At the SBB, we have currently more than 80 different stop purposes. How can they be represented? With the attribute "purpose" or should there be defined a new list attribute which can be extended? Are there any other solutions?
A list of all SBB stop descriptions is attached.
SBB: Haltezwecke / Stop descriptions:
Abwarten Gleisfreigabe Bhf
Durchfahrt (mit Haltberechnung)
Durchfahrt (ohne Haltberechnung)
Ein-/Auslad bei Bedarf
Ein-/Aussteigen bei Bedarf
Nur Abfuhr bei Bedarf
Nur Aussteigen bei Bedarf
Nur Einsteigen bei Bedarf
Nur Zufuhr bei Bedarf
Wenden mit Tfz-Wechsel
Wenden ohne Tfz-Wechsel
Zu-/Abfuhr bei Bedarf
|Re: Haltezwecke / Stop descriptions [message #1537 is a reply to message #1536]
||Fri, 31 March 2017 17:31
Registered: March 2017
I want to contribute to this topic from the point of view of the TAF TSI. In the TAF TSI exists one element dealing with the activities of a train, the element TrainActivityType. The definition is as follows:
<xs:documentation>Indicates certain treatments or operations required for a train. If national codes are used, the first 2 position will be the ISO country code, followed by 00-99.</xs:documentation>
The element defines the structure, but not the European codes to be exchanged for the train activity. For the time being there is no legally binding - through the TAF TSI - European code list available.
On the other hand the railway sector (railway undertakings, infrastructure managers) have a responsibility for those elements not defined in the TAF TSI. For the TrainActivity there is a sector supported documentation available at " github.com/smagla/sector-xsd/blob/master/taf_cat_complete_se ctor.xsd ". In this file are the codes for the train activity defined as follows:
0001 Commercial stop RU Board/disembark passenger train, load/unload freight train
0002 Operational stop IM Stops needed by the IM (e.g. overpassing by another train)
0003 Service stop RU/IM Stops which are used for non-commercial activities (e.g. boarding of staff)
0004 System stop RU/IM allowing the RU to change a system (e.g. signalling system, safety system)
0005 Reversing stop RU/IM stop to enable train unit to run in the opposite direction (without change of engine)
0006 Stops for reversing move or driver change ends RU stop to enable train unit to run in the opposite direction (with using another engine at the other end of the train and change of driver)
0007 Stops for locomotive to run round train RU stop to enable train unit to run in the opposite direction (with using the same engine at the other end of the train)
0008 Technical check/inspection coaches/wagons RU/IM e.g. at origin or intermediate station:
brake test, checking load
0009 Change gauge RU/IM continuation on a network with a different gauge with change of bogies or adaptation of the axles (F->E, SVE->FI)
0010 attach engine/unit RU Unit not previously in service
0011 detach engine/unit RU Unit no longer in service
0012 change engine RU
0013 attach coach/wagon RU
0014 detach coach/wagon RU
0015 attach and detach coach/wagon RU
0016 attach train Operational Train (in service)
0017 split train Operational Train (in service)
0018 Parking of vehicle RU e.g. need to park the train/composition midway for several hours
0019 Mail/parcel services RU
0020 shunting RU actual activity of shunting
0021 shunting service RU Request for shunting service (if offered by the IM or a third party)
0022 Terminal service (terminal in the meaning of final destination) RU Request for services at the end of a train run (if offered by the IM or a third party)
0023 Loco driver change RU
0024 Loco driver break RU legal issue, e.g. to respect working law
0025 Crew change RU different to loco driver change as for the change of the crew a platform will be needed
0026 Custom and passport facilities RU
0027 Other stop reason (miscellaneous) RU/IM
0028 Boarding only RU
0029 Disembarking only RU
0030 Stop on request RU
0031 Departure equals to arrival time RU If in some stations only arrival times are published, this activity code may used to indicate that the train cannot continue before the published arrival time in case of an early arrival.
0032 Departure after disembarking RU mainly used at the end of train run, train may continue as soon as all passengers have disembarked
0033 No waiting for connection RU
0034 Watering RU Indicates the IM that a track with water access will be needed.
0035 Heating Indicates the IM that a track with heating equipment will be needed.
0036 Cleaning / disinfecting RU
0037 Treatment on plants and live animals RU Watering, Foddering, Milking, Spraying, Closing ventilation flaps, Opening ventilation flaps
0038 Treatment of perishable goods RU Checking the temperature, Re-icing, Heating, Checking the proper functioning of the mechanical refrigeration equipment, Refuelling machinery, Switching machinery on or off
0039 Administrative operations RU Weighing, Re-forwarding, Submission to phytosanitary inspections
0040 Run Through (Passing Time) IM
0041 Photo run-by / Photo-stop
0042 Train Waiting Waiting according to local rules
0043 Train running with another train RU Where trains have been attached at a previous location on the schedule
0044 Next working service RU Association where there is a need to define a relationship between a train and its next service. The same vehicle is used for the next train service. Also called "train-set turnover"
0045 Previous working service RU Association where there is a need to define a relationship between a train and its previous service. The same vehicle is reused from the previous train service.
The list above is maintained by the sector and can be changed without consulting ERA.
|Re: Haltezwecke / Stop descriptions [message #1574 is a reply to message #1546]
||Thu, 18 May 2017 12:28
Registered: August 2008
Dear Philip, Mico and all "lurkers",|
I can possibly clarify some issues raised by Philip. This concerns the
current situation in railML, their current usage and the background
behind former development; I do want to value the current situation as
being sufficient or not.
> 2. there are some ambiguities with regard to the attributes
> - an activity might be 'ordered' by the RU for a commercial stop
To explain the intention behind the current situation: The term
"ordered" in the attribute /operationalStopOrdered/ refers to the
contractual relationship between IM and TOC.
The term "commercial" of the attribute of the same title in railML
traditionally refers to the contractual relationship between TOC and
end-customer, not to the contractual relationship between IM and TOC.
> - onOff is not clearly defined to be relevant to customers/goods only
May be "not clearly defined", but the intention behind is of course:
Only for commercial stops. Does not make sense for traditional
operational stops (which are not ordered). Theoretical, having an
operational stop for crew change, one could differ between on/off/both
but so far, there was never a practical demand for that and it is very
far-fetched just to raise or reduce the number of crew-members and fix
this in a timetable.
The intention behind onOff was clearly: Passenger information.
I want to add concerning stopOnRequest: Intended for passenger usage
only; makes no sense for "goods only" activities. The real background is
to tell the passenger whether he has to signal his wish for a stop
immediately before. For freight, a customer cannot signal a wish to stop
"immediately before" (by hand or button). At least, he would have to
phone or communicate in a more specialised way a special time period before.
From an operational view (concerning relationship between TOC and IM
and inside TOC and IM), "goods only" activities are always "on request",
so by default they can be omitted if there is no demand. The former
"Bedarfszug" has been made obsolete therefore.
> 3. in general I suspect that more than one 'activity' can be
> supplied for a stop - how shall 'conflicting' attributes be
> treated in such a case?
Concerning this, it is documented:
"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
I agree that if we will define an enumeration of additional stop
informations (activities), this should be repeatable (several activities
at one stop).
|Re: Haltezwecke / Stop descriptions [message #1588 is a reply to message #1536]
||Thu, 18 May 2017 19:51
Registered: August 2008
Dear Mićo and other timetable developers,|
I have complemented the mapping between railML and SBB stop descriptions
from Mićo with that of ÖBB and DB. The result is in the cloud at
\timetable\railML 2.4\Haltegrund --> Gegenüberstellung Haltearten
Anybody who wants to contribute to the development having no access yet
can surely apply for one.
Thank you, Mićo and Philip for the excellent work in advance.
Now, from my opinion, we could make the following next steps:
- Since a specification of stoppings in railML is needed, we should
start with the stopping information common between the three (or two of
the three) railways. These would be about 30 values (rows 28-64 of the
Excel table). It could become a repeatable list of enumeration
additional and optional to the basic stop types (railML: ocpType= und
If wanted, I can quickly create a suggestion for such an enumeration. It
would cover 98% of the SBB's stop types. (All except two: Trassenwechsel
and Intervention. These two would have to be implemented as "other:...".)
- We should use the term "stop description" rather then "reason" or
such ("Haltezweck") since it is rather an additional information. It
leads to all activities one can do during a stop without being
necessarily reasons for the stop. (E. g. a "brake check" or "finishing
train for departure" can hardly be reasons for a stop; also
"intermediate parking" is rarely a reason for but rather a consequence
of a stop.) Part of the very special "stop descriptions" should
therefore, in my opinion, be deferred and be implemented later on demand
at another place in railML.
- I personally wonder that we come as far as "stop for catering"
(wherein at least 2/3 of the railways are united) but the
security-relevant stops for (virtual) token exchange / train messages
are not included so far. So, from a professional expertise, I suggest to
count these stop descriptions here too. At least these operational stop
descriptions should be distinguishable by operating days.
Hopefully this is a support for further development. Looking forward
with best regards,
> Question regarding the attribute "onOff":
> The railML attribute onOff is an enum with the allowed
> values "BOTH", "ON" or "OFF". What value should be set for
> stops where e.g. the train crew changes (Haltezweck:
> "Auf-/Absteigen Personal")? This is a stop for BOTH but not
> for the passengers.
"onOff" is intended for traffic stops (commercial, "public" stops) only.
"Auf-/Absteigen Personal" is not a public stop therefore it shall be
implemented as @commercial=false, @operationalStopOrdered=true or false.
This is to be regarded as implicit by definition.
> There are also stop descriptons where none of the enum values are suitable (e.g. for "Kreuzung").
Again same answer: "Kreuzung" (only) is not public. A stop which is both
for passenger exchange and crossing, is (per definition) a public stop
and therefore you can use @onOff=both/on/off. If you want to use "none",
it is per definition a non-public stop with implicitly no on/off.
|Re: Haltezwecke / Stop descriptions [message #1589 is a reply to message #1588]
||Wed, 24 May 2017 19:46
Registered: August 2008
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'>
2) Operational stop for crew change (daily) and a crossing on Mon-Fri only:
<stopDescription commercial='false' operatingPeriodRef='op_Mon-Fri'>
<stopDescription commercial='false' operatingPeriodRef='op_Sat+Sun'>
--> 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:enumeration value="collect" />
<xs:enumeration value="drop" />
<xs:enumeration value="split" />
<xs:enumeration value="join" />
<xs:enumeration value="misc" />
<xs:restriction base="rail:tOtherEnumerationValue" />
All names and titles may be regarded as working titles only.
Current Time: Mon May 29 17:16:12 CEST 2017