Home » railML newsgroups » railml.timetable » Haltezwecke / Stop descriptions
Haltezwecke / Stop descriptions [message #1437] Wed, 02 November 2016 13:26 Go to next message
Mićo Mićić is currently offline  Mićo Mićić
Messages: 9
Registered: November 2016
Junior Member
Hallo zusammen

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.

Vielen Dank
Mico

----
----

Dear all,

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.

Thanks!
Mico


SBB: Haltezwecke / Stop descriptions:
Abwarten Gleisfreigabe Bhf
Abwarten Streckenfreigabe
Abwarten Zugfolgezeit
Auf-/Absteigen Personal
Aufstellen
Beistellen D/V-Lok
Beistellen P-Lok
Beistellen Tfz
Diensthalt
Durchfahrt
Durchfahrt (mit Haltberechnung)
Durchfahrt (ohne Haltberechnung)
Ein-/Auslad
Ein-/Auslad bei Bedarf
Ein-/Aussteigen
Ein-/Aussteigen bei Bedarf
Geschwindigkeitswechsel
Intervention
Kreuzung
Lok-Personalwechsel
Nur Abfuhr
Nur Abfuhr bei Bedarf
Nur Aussteigen
Nur Aussteigen bei Bedarf
Nur Einsteigen
Nur Einsteigen bei Bedarf
Nur Zufuhr
Nur Zufuhr bei Bedarf
Pause Lokpersonal
Schwächen/Trennen
Stärken/Vereinigen
Systemwechsel
Tfz-Wechsel
Trassenwechsel
Umfahren
Umstellen
Wagendurchlauf
Wegstellen
Wegstellen D/V-Lok
Wegstellen P-Lok
Wegstellen Tfz
Wenden mit Tfz-Wechsel
Wenden ohne Tfz-Wechsel
Zu-/Abfuhr
Zu-/Abfuhr bei Bedarf
Zugfolgeänderung
Re: Haltezwecke / Stop descriptions [message #1443 is a reply to message #1437] Tue, 08 November 2016 17:08 Go to previous messageGo to next message
Philip Wobst is currently offline  Philip Wobst
Messages: 27
Registered: November 2013
Location: Hanover, Germany
Junior Member
Hello Mico,

what you have described has been the solution for the TPS railML export - we have mapped our internal stop types to the railML attributes (e.g. commercial, stopOnRequest, onOff, etc.Wink and then we provide our internal description as the purpose and not as a separate enumeration.

Best regards,

Philip
Re: Haltezwecke / Stop descriptions [message #1449 is a reply to message #1443] Tue, 22 November 2016 08:33 Go to previous messageGo to next message
Mićo Mićić is currently offline  Mićo Mićić
Messages: 9
Registered: November 2016
Junior Member
Hello Philip,

thank you for the reply. I think this might be also the solution for us.

As discussed at the last telephone conference, the proposal by Vasco to refer to a list of stop descriptions provided by each IM would be also interesting. Do you already have ideas how this could be implemented in RailML?

Best regards,
Mico
Re: Haltezwecke / Stop descriptions [message #1535 is a reply to message #1449] Mon, 27 March 2017 09:49 Go to previous message
Philip Wobst is currently offline  Philip Wobst
Messages: 27
Registered: November 2013
Location: Hanover, Germany
Junior Member
Hello all,

following the discussion at the last TT developer meeting I would like to add that the TAF/TAP TSI already includes a so called train activity type. Adding the TAF/TAP train activity types might be used to support the actual list of standard and country specific activities. However, these shall be mapped to the corresponding railML attributes (mapping outstanding).

12.14.7 Use of the Train Activity Type and Associated Trains

The list of Activity Type Codes is split into two types: Common European Codes that are available to be used by all countries and National/Company codes that are only relevant to a specific network and to be used in the RU / IM communication only for that network. In both cases the element size will be 4 alpha-numeric.

Common European Codes will have the structure as follows:
•	4 Digit Code (numeric) that represents the Code List values for the common activities

National Codes will have the structure as follows:
•	The first two characters will represent the country of the network in ISO format e.g. UK
•	The remaining two characters (represented as a numeric) will represent a single unique activity within the network e.g. 01 = Stops shorter than 30 secs
Previous Topic: railML 3.x TT: Times vs. Durations in itineraries
Goto Forum:
  


Current Time: Thu Mar 30 04:43:30 CEST 2017