Home » railML newsgroups » railML.infrastructure » [railML3] speedSection maxSpeed values ("end" is no longer needed)
[railML3] speedSection maxSpeed values [message #3336] Mon, 14 October 2024 10:52
christian.rahmig is currently offline  christian.rahmig
Messages: 474
Registered: January 2016
Senior Member
Dear all,

in railML 2 it was possible to define the end of a speed restriction with a <speedChange> with @vMax="end" (see [1]).
For railML 3 this concept is no longer needed, because instead of (spot) <speedChange> elements, railML 3 provides (linear) <speedSection> elements. This means, that the end of a speed restriction is derived directly from the end of the <speedSection>'s linear location. Consequently, we suggest to remove the @maxSpeed value "end" and change the @maxSpeed data type into tSpeedKmPerHour (based on xs:decimal). This was mentioned in the forum [2] and formulated as ticket for railML 3.3 [3].

If you have any objections, please let us know asap.

[1] https://www.railml.org/forum/index.php?t=msg&th=159& goto=559&#msg_559
[2] https://www.railml.org/forum/index.php?t=msg&th=159& goto=3146&#msg_3146
[3] https://development.railml.org/railml/version3/-/issues/582

Thank you very much and best regards
Christian


Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Previous Topic: [railML3] Extension of border type enum
Next Topic: [railML 3] railway signal modeling
Goto Forum:
  


Current Time: Thu Dec 05 14:35:24 CET 2024