Home » railML newsgroups » railml.timetable » stopDescription
stopDescription [message #661] Wed, 30 August 2006 18:44 Go to next message
Joachim.Rubröder is currently offline  Joachim.Rubröder
Messages: 33
Registered: September 2004
Member
Problem: The type-attribute of the entry-element is overloaded with three
different kinds of information: "begin/end", "stop/pass",
"operational/conditional".
The RhB (Rhätische Bahn) uses railML to distribute timetable information
between their systems and need a more detailed distinction for the
different kinds of stop.

As further development of the timetable schema I therefore suggest to
delete the two enumerations "operational" and "conditional" of the
attribute "type" and use a new (optional) element "stopDescription"
instead, with the following attributes (all optional):

- commercial boolean Indicates, whether the stop is for
commercial purpose (announced to customer) or operational only.
- stopOnRequest boolean Indicates, whether the train stops always
or on request only. Typically in combination with minStopTime = 0.
- onOff on/off/both Indicates, whether passengers are
allowed to get on or off the train and goods may be loaded or unloaded.
- purpose string Describes the purpose of the stop.
(e.g. crew change, customs)
- serviceID string Train stops on spezified days
only. (Seasonal Stop)

I think this covers most of the different kinds of stops.

Joachim
Re: stopDescription [message #662 is a reply to message #661] Fri, 01 September 2006 08:24 Go to previous messageGo to next message
Daniel Huerlimann is currently offline  Daniel Huerlimann
Messages: 17
Registered: September 2004
Junior Member
In article <ed4fa7$eli$1(at)sifaivifhgde>, jrubroeder(at)sma-partnerch
wrote:

> Problem: The type-attribute of the entry-element is overloaded with three
> different kinds of information: "begin/end", "stop/pass",
> "operational/conditional".
> The RhB (Rhätische Bahn) uses railML to distribute timetable information
> between their systems and need a more detailed distinction for the
> different kinds of stop.
>
> As further development of the timetable schema I therefore suggest to
> delete the two enumerations "operational" and "conditional" of the
> attribute "type" and use a new (optional) element "stopDescription"
> instead, with the following attributes (all optional):
>
> - commercial boolean Indicates, whether the stop is for
> commercial purpose (announced to customer) or operational only.
> - stopOnRequest boolean Indicates, whether the train stops always
> or on request only. Typically in combination with minStopTime = 0.
> - onOff on/off/both Indicates, whether passengers are
> allowed to get on or off the train and goods may be loaded or unloaded.
> - purpose string Describes the purpose of the stop.
> (e.g. crew change, customs)
> - serviceID string Train stops on spezified days
> only. (Seasonal Stop)
>


Hello Joachim

Your idea is very good. It simplifies the usage of the type-attribute of
the entry-element and it offers a very flexible description for the
reason of a stop.

Best regards

Dani

--
============================================================ ==
Eidg. Technische Hochschule Zuerich
Swiss Federal Institute of Technology Zurich
Inst. for Transportation Planning and Systems
CH - 8093 Zurich, Switzerland

Dr. Daniel Huerlimann¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý ¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý
Phone: + 41 1 633 27 38
Fax: + 41 1 633 10 57¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý
E-Mail: huerlimann(at)ivtbaugethzch¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý¬Ý
WWW: http://www.ivt.baug.ethz.ch, http://www.opentrack.ch
============================================================ ==

-- =======

-- --
Re: stopDescription [message #667 is a reply to message #661] Thu, 25 January 2007 15:06 Go to previous message
Daniel Huerlimann is currently offline  Daniel Huerlimann
Messages: 17
Registered: September 2004
Junior Member
jrubroeder(at)sma-partnerch wrote:
> Problem: The type-attribute of the entry-element is overloaded with three
> different kinds of information: "begin/end", "stop/pass",
> "operational/conditional".
> The RhB (Rhätische Bahn) uses railML to distribute timetable information
> between their systems and need a more detailed distinction for the
> different kinds of stop.
>
> As further development of the timetable schema I therefore suggest to
> delete the two enumerations "operational" and "conditional" of the
> attribute "type" and use a new (optional) element "stopDescription"
> instead, with the following attributes (all optional):
>
> - commercial boolean Indicates, whether the stop is for
> commercial purpose (announced to customer) or operational only.
> - stopOnRequest boolean Indicates, whether the train stops always
> or on request only. Typically in combination with minStopTime = 0.
> - onOff on/off/both Indicates, whether passengers are
> allowed to get on or off the train and goods may be loaded or unloaded.
> - purpose string Describes the purpose of the stop.
> (e.g. crew change, customs)
> - serviceID string Train stops on spezified days
> only. (Seasonal Stop)
>
> I think this covers most of the different kinds of stops.
>
> Joachim
>

As an addition I recommend to add an information (boolean) whether the
defined times (arrival and departure) are used as restrictions (e.g. to
define an earliest departure time) or if they are used for information only.

- isTimingStation boolean


Best regards

Dani
Previous Topic: Proposal for new timetable schema version 2.0(?)
Next Topic: Timetable scheme V1.03 released
Goto Forum:
  


Current Time: Thu Mar 28 21:52:05 CET 2024