| [railML3] Deprecating mileageChange [message #4075] |
Fri, 03 July 2026 12:05  |
christian.rahmig
Messages: 580
Registered: January 2016
|
Senior Member |
|
|
Dear all,
when developing railML 3.2 we introduced the functional infrastructure element <mileageChange> in 2022 (cf. [1] [2]). We went this way although we knew that the <linearPositioningSystem> with its <anchor> child elements is able to model all these mileage change scenarios, too.
With the positioning approach (cf. [3] [4]) we tried to limit model redundancies for locations making positioning unambiguous in usage. This included choosing the more powerful approach with //linearPositioningSystem/anchor/ to be chosen as preferred solution for modelling mileage changes with railML 3.3.
Now, with railML 3.4, we want to do the next step and deprecate the <mileageChange> element. From now on, users shall make use of the approach with //linearPositioningSystem/anchor/ only. Best practice examples showing how to use this approach, are documented on the wiki page [5].
[1] https://www.railml.org/forum/index.php?t=msg&th=829& goto=2915&#msg_2915
[2] https://development.railml.org/railml/version3/-/work_items/ 478
[3] https://development.railml.org/railml/version3/-/work_items/ 541
[4] https://cloud.railml.org/f/324110
[5] https://wiki3.railml.org/wiki/RTM:anchor
Best regards
Christian
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
|
|
| Re: [railML3] Deprecating mileageChange [message #4096 is a reply to message #4079] |
Fri, 14 August 2026 08:59  |
Thomas Nygreen
Messages: 129
Registered: March 2008
|
Senior Member |
|
|
Hi Mathias, do you think that could be a kind of isMilepost (with two shown values) or has to be its own type of board?
Best regards,
Thomas
Thomas Nygreen – Common Schema Coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
|
|
| Re: [railML3] Deprecating mileageChange [message #4123 is a reply to message #4097] |
Wed, 26 August 2026 18:35 |
christian.rahmig
Messages: 580
Registered: January 2016
|
Senior Member |
|
|
Dear all,
as explained in the initial post, the functionality of infrastructure element //mileageChange is being modelled with the //linearPositioningSystem anchors. As a compromise, the //mileageChange has not been marked deprecated, but extended with a reference attribute to link the relevant //anchor. The attribute //mileageChange/@type has been removed, because it is a source of potential inconsistencies as the information can be derived from the mileage values.
The railML 3.4 approach towards mileage changes is described in detail in Gitlab issue #771 [6].
Best regards
Christian
[6] https://development.railml.org/railml/version3/-/work_items/ 771
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
| Re: [railML3] Deprecating mileageChange [message #4124 is a reply to message #4097] |
Wed, 26 August 2026 18:38 |
christian.rahmig
Messages: 580
Registered: January 2016
|
Senior Member |
|
|
Mathias Vanden Auweele wrote on Fri, 14 August 2026 09:03It is its own type of board for me.
Dear Mathias,
can you provide a link to a photo of such a board?
Thanks and regards
Christian
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
|
|
Members
Search
Help
Login
Home
