At the moment we still have mileageChanges as functionalInfrastructureElements. However, as of version 3.4 of railML the linearPositioningSystem will basically require users to provide mileageChanges at the level of the positioningSystem, because otherwise the calculated mileages would not be correct anylonger (as they are calculated based on the offsetToStart value). Considering this, the element mileageChange as functionalInfrastructureElement needs to be reevaluated. In principle it is not necessary anymore and could be removed. There is some people in the community though that very much like the element to remain in the standard. I see 3 options: a) complete removal of the now redundant element<br> b) extension of the element by a mandatory reference to the anchor it represents. This way users would be pointed towards usage of anchors to describe the specifics of the linear positioning system / mileage. This could also be useful when dealing with overlapping mileage systems.<br> c) Leave mileage change as is, pointing out in documentation that it should be aligned with the positioning systems.<br> Personally, I would be leaning towards option b as a compromise to those that want to hold on to the mileageChange element. ## Links * Forum discussion: * Christian Rahmig, 03.07.2026: https://www.railml.org/forum/index.php?t=msg&th=1169&goto=4075&#msg_4075