Home » railML newsgroups » railML.infrastructure » [railML3] measure and distance in linear positioning systems (distanceToNext seems to be the better choice than measureToNext)
[railML3] measure and distance in linear positioning systems [message #3289] Fri, 30 August 2024 10:35
christian.rahmig is currently offline  christian.rahmig
Messages: 458
Registered: January 2016
Senior Member
Dear all,

have you ever wondered what the attribute @measureToNext in //linearPositioningSystem/anchor/ is used for?
If not, you may be aware of the best practice documentation on the wiki page of the <anchor> element [1]

However, the attribute name @measureToNext is little bit confusing. because the other anchor attribute, which describes the linear position value, is named @measure, too. What @measureToNext actually describes is a distance. It is the distance from this anchor until the next anchor or until the end of the linear positioning system. Therefore, I suggest to rename @measureToNext into @distanceToNext. The topic is already documented in a new ticket [2].

What are your ideas on this proposal?
What about the datatype for the @distanceToNext? Shall it be fixed with tLengthM in metres, or shall we leave the unit open to be decided by the user (@units is an already existing attribute in linearPositioningSystem)?

As usual, any feedback is highly appreciated.

Best regards
Christian


[1] https://wiki3.railml.org/wiki/RTM:anchor
[2] https://development.railml.org/railml/version3/-/issues/566


Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
 
Read Message
Previous Topic: [railML3] Usage of <ownsPlatform> vs <ownsInfrastructureElement>
Next Topic: [railML2] Single and double derailer
Goto Forum:
  


Current Time: Sun Sep 01 07:09:41 CEST 2024