| Re: Haltetafel / stop post [message #477 is a reply to message #381] |
Sun, 02 December 2012 12:15   |
Christian Rahmig
Messages: 151
Registered: January 2011
|
Senior Member |
|
|
Dear railML users,
> The new element <stopPost> is introduced (cp. [1]):
>
> - The element stopPost is defined in a container stopPosts within the
> ocsElements object.
> - The required parameters id, pos and dir are inherited from the type
> tOrientedElement.
> - Using the optional parameter platformEdgeRef the stop post can be
> referenced with a platform for which it is valid.
> - Using the optional parameter validForMovements the train types for
> which the stop post is relevant can be defined. The enumeration values
> freightTrains, passengerTrains, allTrains and shunting are currently
> possible.
> - If the stop post is only valid for trains with a certain train length,
> the optional parameter trainLength needs to be set.
> - If the stop post is only valid for trains with a certain number of
> axles, the optional parameter axleCount needs to be set.
> - If the stop post is only valid for trains with a certain number of
> wagons, the optional parameter wagonCount needs to be set.
> - If the stop post is only valid for trains fulfilling a certain verbal
> constraint, the optional parameter verbalConstraint needs to be set.
> - If the stop post is only a virtual element, which is not physically
> represented along the track but only in the operational rules, the
> optional parameter virtual needs to be set to true.
just for completeness I want to mention that a stop post can refer to
several signals by using the sequence of "signalRef" objects (cp. [2]).
> [1] https://trac.assembla.com/railML/ticket/167
[2] https://trac.assembla.com/railML/ticket/167#comment:16
Regards
--
Christian Rahmig
railML.infrastructure coordinator
|
|
|
|
Members
Search
Help
Login
Home
