Per-leg
One decision at a time, framed the way you ran it.
Per-leg slices your track at the controls and shows one leg at a time, cropped and framed to it. It is where route choice is actually argued about, because it is the only view where two routes between the same pair of controls are the same size on screen.
How a leg is found
Leg boundaries come from where your track passes each control. Where the event has split times, those correct the match: for each control, the difference between the track's pass and the official split should be the same number, and the median across all controls is used, so a single bad control match does not move the rest.
This matters most for a runner who searched around a control, where matching on the closest pass alone places the boundary late.
Rotation and zoom
| Setting | Options | Default |
|---|---|---|
| Rotation | north keeps the map north-up; run rotates it so the control you are heading for is at the top | run |
| Zoom | tight, fit or loose framing of the leg | fit |
Run rotation matches how a map is held in the terrain: turned so you are running up the sheet.
Both are defaults you can set once in Settings and override per analysis.
The leg comparison table
Eleven columns, all individually switchable:
| Column | What it tells you |
|---|---|
| Distance | How far you actually ran on this leg |
| Straight | The straight-line distance between the two controls |
| Time | Your leg time |
| Pace | Your pace over the ground you covered |
| Straight pace | Your time divided by the straight-line distance — comparable across runners on different routes |
| Climb / Descent | Vertical metres, where the file has elevation |
| Mean deviation | How far, on average, you were from your intended line |
| Events | Detected mistakes on this leg |
| Field rank | Where your leg time places you in the class |
| Terrain mix | The share of the leg spent on path, open, runnable forest, slow forest, fight, marsh and rock |
Straight pace is the comparable column. Pace over your own distance rewards a longer route choice, since you covered more ground faster. Time over the straight-line distance is what the leg cost, and it compares two runners who chose differently.
Other runners on the leg
Every shared track in the class is drawn on the same leg, beneath your own. Hovering or tapping one shows the runner's name and leg time, according to your label settings.
Two lines leaving the same circle and rejoining at the next, with their times attached, is the most direct comparison the product offers.
Forked legs and merged splits
In a forked race — a relay, or an individual race with gaffling — a split-time sheet often aggregates several course legs into one entry, because the runners did not all visit the same controls in between.
Analyse handles that by mapping split legs onto course legs explicitly and merging the course legs a single split covers into one displayed leg. The mapping travels with the data, so the leg comparison and the AI coach both know when a leg number in the split sheet means a range of course controls.
Forking is declared, not inferred
Jumping here from elsewhere
Clicking a mistake in the mistakes list, or a finding in the AI review, opens the per-leg view at that leg with the position marked.