Home » railML newsgroups » railML.infrastructure » Haltetafel / stop post
| Re: Haltetafel / stop post [message #385 is a reply to message #381] |
Tue, 09 October 2012 11:01   |
Dirk Bräuer
Messages: 311
Registered: August 2008
|
Senior Member |
|
|
Dear Christian,
the summary of attributes/parameters for <stopPost> sounds good. Some
short notes:
1) I think we need one more attribute/parameter defining the relation of
the stop post to the train. (There were earlier discussions about that
feature.) It should be something with the enumerations "frontOfTrain" /
"mittleOfTrain" / "endOfTrain":
Most "normal" stop posts we know (from Germany) are valid for the front of
the train and are non-virtual. But this is not always the case. For
instance in Czech Republic, there are virtual stop posts valid for the end
of the train. The virtual stop post stands at the beginning of the
platform because the stairs/elevators are at the beginning of the
platform. This virtual stop post is valid for the end of the train, which
means that the train should not move further forward that that its last
door is at the rear end (=beginning) of the platform. This is to avoid an
unnecessary long walk for the passengers.
Such virtual stop posts are programmed in the Czech "black boxes" (ATO),
and they are therefor "really" existing in software (in practice).
It is also a matter of some national ETCS instances but (unfortunately, in
my opinion) not very common in Germany due to the "relying on old INDUSI
philosophy". But that should not mean that we forget or ignore it in
RailML.
2) Concerning the attributes trainLength, axleCount, wagonCount I would
prefer a clarification of the relation: maxAxleCount, maxTrainLength,
maxWagonCount. Theoretically you could then also add the other boundaries:
minAxleCount, minTrainLength, minWagonCount but they would not have
equivalence in practice as far as I know - but again: We should not rely
too much at German experience but in case of doubt rather be a little bit
more theoretical.
3) Concerning the attribute "validForMovements" is should be possible to
enumerate more than one value.
Would be nice if you could consider these notes before releasing 2.2.
Thank you,
Best regards,
Dirk.
|
|
|
|
Current Time: Wed May 08 22:07:15 CEST 2024
|
Members
Search
Help
Login
Home
