Home » railML newsgroups » railML.infrastructure » More detailed 'speed change' definitions
Re: Mandatory stops e.g. before a level crossing [message #1949 is a reply to message #1823] Mon, 03 September 2018 19:28 Go to previous message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 311
Registered: August 2008
Senior Member
I must complement Christians answer a bit: It is not such a special exception as Christian writes.

Theoretically, a "speed change" which is a mandatory stop could be encoded as:
- one speed <speedChange> with @speed=0,
- one more <speedChange> with @speed>0 and @trainRelation='headOfTrain' at the same position.

This would be logical (at least as long as the order is out of question) and no exception. This is how we write it into driver's timetables.

But for railML, we did want to avoid having two <speedChange>s (of the same speed profile) at the same position.

So, we introduces <speedChange>@mandatoryStop="true". Such a <speedChange>@mandatoryStop="true" implies the two above mentioned <speedChange>s and avoids speed=0.

Best regards,
Dirk.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re-factoring of <infraAttributes>
Next Topic: Hierarchy of overlaying speed profiles and National vs. Generic speed profiles.
Goto Forum:
  


Current Time: Sat Apr 27 21:28:48 CEST 2024