Repeated ground
The same coordinate can belong to several moments in one route.
A loop may use one track from the start, branch into a circuit, then return along the same track to finish. A figure-of-eight can pass through its centre twice. A route may also touch the same junction on outward and homeward legs.
On the map, the repeated sections can collapse into one visible line. In the file, they remain separate occurrences because the ordered points reach that place at different stages. One belongs near the beginning and another near the end.
This matters for progress. Remaining distance, the next turn and the highlighted section all depend on which occurrence the navigation system believes you have reached. Geometry alone does not label an outbound line and a return line when they sit directly on top of each other.
The nearest-point trap
One position can be equally close to two valid places in the sequence.
A simple progress method could find the nearest point on the route. That works when every part of the line is well separated. On an overlap, the same measured position may match an early point and a late point with almost identical distance.
Location error makes the ambiguity wider. A marker that wanders across the overlapping line cannot reveal which pass is intended. Direction helps, especially where outward and return legs oppose each other, but direction can be weak while stationary or when movement is slow.
- Recent progressThe section already completed is evidence for the next occurrence in sequence.
- Travel directionOpposing passes can be separated once movement is clear.
- Branch historyEntering or leaving the unique circuit shows which side of the overlap you occupy.
- Manual confirmationAn app may need the user to choose or continue before progress settles.
Before and after
Identify the unique section on each side of the shared line.
Zoom out until the entire overlap, its branches and the unique circuit are visible. Then read the journey in order rather than trying to interpret the doubled stroke in isolation.
- Departure
Follow the route away from the common track.
Identify the junction where the outward sequence leaves the shared section and enters unique ground.
- Circuit
Trace the section that occurs only once.
The ordered line around the circuit establishes which occurrence of the overlap comes before it and which comes after.
- Return
Find where the route rejoins the shared section.
The physical path may now be identical, but the expected next branch belongs to the homeward sequence.
If a route is supplied as several disconnected lines or has been simplified heavily, the intended sequence may be harder to see. Inspect the source route before relying on automatic remaining-distance or manoeuvre cues.
Mark the transitions
Turn an invisible duplication into two clear decisions.
If the departure place can change, settle where the circular route should start before interpreting its overlaps. Moving the start changes the sequence around the loop even when the visible shape stays closed.
Inspect the full route in the Library and give each pass a plain description, such as outbound until the reservoir junction and returning after the summit circuit. Those descriptions retain meaning when both passes occupy one stroke on the map.
If remaining distance suddenly resembles the end of the route, compare the last unique section travelled before trusting the new state. At the branch itself, use signs, terrain and the route on both sides of the decision rather than choosing whichever visible stroke appears brighter.
Sources & scope
What this answer is based on.
- Topografix: GPX tracks and connected point order
- RFC Editor: GeoJSON LineString coordinate order
- PostGIS: locating the closest fractional position on a line
The sources define ordered line geometry and closest-point location. The article applies those concepts to repeated route sections; individual apps resolve progress differently.