| Re: Haltetafel / stop post [message #392 is a reply to message #385] |
Fri, 19 October 2012 12:52   |
Christian Rahmig
Messages: 151
Registered: January 2011
|
Senior Member |
|
|
Dear Dirk and other railML users,
> 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":
In the latest commit regarding trac ticket [1] I added the exisiting
attribute "trainRelation" to the element <stopPost>.
> 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.
Let's think of the tram scenario where there are two stop posts situated
at a station, one telling "30m" and the next one "45m". If a short train
stops at the stop post entitled "45m", the passengers would have to walk
more meters. Regarding your explanation of the "maxTrainLength" the
short train would be principally allowed to stop at the "45m-stop-post",
because its length is shorter.
However, I would skip these detailed view and leave it open to the user
if he/she refers to a minimum or maximum value.
> 3) Concerning the attribute "validForMovements" is should be possible to
> enumerate more than one value.
In the latest commit regarding trac ticket [1] I put the attribute
"validForMovement" into a sequence. Now it is possible to define
multiple movement validities for the same stop post.
[1] https://trac.assembla.com/railML/ticket/167
Regards
--
Christian Rahmig
railML.infrastructure coordinator
|
|
|
|
Members
Search
Help
Login
Home
