| Re: Difference between 'load' and 'timetableLoad' [message #793 is a reply to message #787] |
Wed, 30 May 2012 13:25  |
Dirk Bräuer
Messages: 311
Registered: August 2008
|
Senior Member |
|
|
Dear Joachim,
> the attribute "timetableLoad" was requested by yourself 2 years ago and
> means "Fahrplanmasse = Masse Wagenzug ohne Tfz(e)".
thank you for reminding me. I thought so.
> I would assume, that "load" means rather the real/actual load of a
> formation while running, in contrast to the assumed "timetableLoad"
> during the timetable planning process. If the real load is unknown, you
> could
> assume a higher "timetableLoad" to get a maximum for the running time.
> The attribute "load" is rather old and is propably used in different ways
> without awareness of the detailed differences between real/actual and
> assumed values. So every program using "load" should announce how it is
> meant to be interpeted.
Well, I don't like these "do what you want" policies so I would rather see
the load being equipped with a certain meaning and function. So, my
suggestion is to declare the 'load' for actual load of a certain day
_after_ the train did operate in contrast to 'timetableLoad' which is
always a value assumed in advance.
It may be a contradiction that there are some 'actual' values in
'timetable' scheme but anyway, we also have already the possibility to
define actual arrival/departure times. For the moment, let's leave away
the "problem" that these values only make sense if the train has not more
than one operating day in the past.
For the more far future, it should be discussed and decided to move away
all the 'actual' values from 'timetable' scheme leaving the 'timetable' as
something which is always a planning in advance. Additionally, we could
provide a kind of "actualData" scheme for all the operating data of _one_
day of the past.
Best regards,
Dirk.
|
|
|
|
Members
Search
Help
Login
Home
