|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 #1546 is a reply to message #1536]
||Fri, 07 April 2017 14:16
Registered: November 2013
Location: Hanover, Germany
I have had a look at the data you have provided and have provided an updated file in the cloud (more details and some filters). I would like to suggest to switch to 'activities' instead of 'descriptions' because the activities at a stop are described and and not the stop itself.
I see the following topics that need further review:
1. the current attributes do not allow a 1:1 mapping of the SBB stop activities
2. there are some ambiguities with regard to the attributes
- an activity might be 'ordered' by the RU for a commercial stop
- onOff is not clearly defined to be relevant to customers/goods only
- no possibility to identify activities for the IM
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?