Home » railML newsgroups » railML.infrastructure » mileagesChanges and Anchors
mileagesChanges and Anchors [message #4243] Fri, 16 October 2026 16:19 Go to next message
Stefan Hubrig is currently offline  Stefan Hubrig
Messages: 12
Registered: October 2018
Junior Member
Hello all,

I understood that an anchor can be used to describe a mileage change at the positioning system level.

In some cases, however, the mileage change is not applicable to all parallel tracks that use the same positioning system.

This could happen, for example, when a siding track within a station is longer than the main track. As far as I know, a mileage change is the only mechanism that could be used to represent this additional length.

Or is there another way to model this?

Best regards,
Stefan
Re: mileagesChanges and Anchors [message #4244 is a reply to message #4243] Sat, 17 October 2026 12:19 Go to previous messageGo to next message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 180
Registered: February 2025
Location: Brussels
Senior Member
Hello Stefan,

Best is to make the linear positioning system a truely linear element. Thus it's like a linear location, never branches out. That means that if you need multiple tracks in a station to have a linear referencing system, you also need multiple linear positioning systems in that station. Of course, they can use the same anchors. In that way, linear positioning is unambiguous


Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium
Re: mileagesChanges and Anchors [message #4248 is a reply to message #4244] Mon, 19 October 2026 10:10 Go to previous messageGo to next message
Stefan Hubrig is currently offline  Stefan Hubrig
Messages: 12
Registered: October 2018
Junior Member
Hello Mathias,

for many use cases, it does not matter whether a non-main track is somewhat longer than the main track.

However, in cases where this information is relevant, I believe it would introduce considerable overhead if a separate positioning system had to be created for each station track, for example.

Best regards,
Stefan
Re: mileagesChanges and Anchors [message #4250 is a reply to message #4248] Tue, 20 October 2026 19:39 Go to previous messageGo to next message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 180
Registered: February 2025
Location: Brussels
Senior Member
Hello Stefan,

You'll have to do a trade-off for yourself if you need unambiguous positioning or simplification. All I can say is that problems start when reality is simplified and the scope is increased later :)

And your first post in this topic actually already covers one of these cases. It's best solved by defining additional LPS


Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium
Re: mileagesChanges and Anchors [message #4266 is a reply to message #4250] Tue, 03 November 2026 13:43 Go to previous message
Stefan Hubrig is currently offline  Stefan Hubrig
Messages: 12
Registered: October 2018
Junior Member
Hello all,

So far, four options have been discussed:

1) Use a new positioning system for all netElements whose length differs from the main track
Problem: This introduces additional overhead for positioning data and may lead to confusing information, as the lengths in one representation differ from those in another.

2) Use a "fake" anchor with a mileage change of 0, which can then be referenced on the siding track
Problem: It seems illogical to make such an anchor mandatory if it is immediately compensated by a "fake" anchor. In addition, the anchor data would differ from the corresponding mileage change data again.

3) Use the length of the track
Problem: The exact location of the mileage change would still remain unknown.

4) Use a railML extension
Problem: This could potentially lead to certification issues. On the other hand, one could argue that railML 3.4 no longer supports mileage changes on netElements.

Are there any additional ideas or alternative approaches?

Best regards,
Stefan

[Updated on: Tue, 03 November 2026 16:46]

Report message to a moderator

Previous Topic: Infrastructure element datamodel quality and input-data source
Goto Forum:
  


Current Time: Sun Nov 08 18:29:10 GMT+1 2026