What happens at route intersections?

Lines that meet

A crossing on the screen may represent several different structures.

A route can cross itself, touch an earlier point, share a section or pass over another line at a different level. These shapes can look similar when zoomed out. Only some create a physical choice.

A bridge over a lower path creates a visual crossing but no turn. A figure-of-eight may use a real central junction twice. A narrow loop can touch the same coordinate while approaching from different directions. A route overlay can also appear to meet a base-map path because of drawing tolerance even when their underlying coordinates differ.

The screen intersection is therefore the start of a question, not an instruction. First establish whether the route geometry actually connects and whether the ground offers a usable movement between the branches.

Read through the junction

The intended exit follows from the line before and after the decision.

An ordered route does not merely identify the intersection point. It arrives along one section and leaves along another. Zoom in far enough to see both. The angle between them, the direction of travel and the next distinctive feature are stronger clues than whichever branch is closest to the position marker.

Turn-by-turn route data can include a manoeuvre location, bearings before and after the movement and information about the available network exits. A plain GPX track may carry none of that. It supplies geometry, leaving the app or user to interpret the bend in the point sequence.

• ApproachIdentify the path on which the route enters the decision area.
• DepartureTrace enough later geometry to distinguish parallel or closely spaced exits.
• LevelCheck whether a bridge, tunnel or embankment prevents the apparent connection.
• SequenceIf the junction occurs twice, confirm which occurrence follows the route already travelled.

Limited evidence

A turn cue is only as specific as the route and map data behind it.

Sparse geometry can place the bend before or after the physical junction. Position drift can attach the marker to a neighbouring branch. Map matching can favour a path in the network that differs from the saved line. On an overlap, progress may be associated with the wrong pass.

A missing alert does not prove that the route continues straight. A plain track can cross a junction without any stored manoeuvre. Equally, an alert may prepare you before the actual movement rather than mark the precise place to turn.

Use a cue to focus attention. Use the route shape and the physical junction to make the movement.

At the crossing

Slow the navigation problem down until the branches are distinct.

Read the intersection as a small decision tree. Begin with the line on which you arrived, establish whether the apparent branches connect on the ground, then trace the one exit that continues the stored sequence.

Does the crossing connect on the ground?

Recenter if needed and use a scale that shows recent travel as well as the next section. Check level, signs and access. A highlighted line cannot establish a bridge, open gate, lawful movement or safe surface.

If it connects, which exit continues the sequence?

Use north, recent direction and visible features instead of repeatedly rotating the map while deciding. Trace the chosen branch far enough beyond the junction to distinguish close or parallel exits.

Does the route settle after leaving?

Watch whether the distance between your movement and the intended line settles or grows. Stop and reassess when the evidence does not converge.