Running route calculator

The route you choose is not just about distance — it directly shapes the training stimulus. Surface type affects mechanical load on joints and tendons: trail running increases proprioceptive demand and engages stabilizing muscles differently than road running. Paved routes are more predictable for pace-specific work like threshold sessions and tempo runs.

Elevation changes shift the physiological demand of a run. A flat 10K at tempo pace trains the lactate threshold. The same pace on a hilly route trains a mix of threshold climbing and eccentric downhill loading — a different stimulus with different recovery demands.

Intentional route selection means matching terrain to your training goal for the day, rather than always defaulting to the same loop. Easy runs benefit from varied, comfortable terrain. Quality sessions benefit from consistent, measured surfaces. Race preparation benefits from terrain that simulates race-day conditions.

Uphill running increases energy cost roughly 10-15% per 1% grade. This means a 5:00/km pace on flat ground requires the effort of approximately 4:20/km on a 5% uphill grade — the pace slows, but the physiological demand increases substantially.

Downhill running reduces metabolic cost but increases mechanical stress. The eccentric muscle contractions during downhill running cause more muscle damage per kilometer than flat or uphill running. This is why predominantly downhill routes can leave you more sore than expected despite feeling easier during the run.

Wind exposure also varies by route: open roads and exposed ridgelines create headwind drag that increases energy cost, while sheltered urban routes or tree-lined trails reduce wind effects. Route planning should consider prevailing wind direction, especially for long runs and tempo sessions.

For race pacing, use grade-adjusted pace to set realistic expectations. Running power (from the power calculator) provides a terrain-independent intensity metric that can be more useful than pace on variable terrain.

Race-specific route planning means simulating the demands of your target race in training. If your race has significant hills in the second half, include routes with back-half elevation. If the course is exposed to wind, train on similar terrain. If the race surface transitions from road to trail, practice that transition.

For goal races, try to rehearse key segments: the steepest climb, the longest flat stretch, the finish-line approach. This builds both physical adaptation and mental familiarity with the course demands.

Use this route planner to create training routes that match your race profile. Compare surface breakdowns and elevation density scores with your target race data. Export courses to your GPS watch for turn-by-turn navigation during training runs, and use the split calculator to plan pacing adjustments for elevation changes.

Use loops for balanced terrain and logistics, out-and-back for pacing discipline, and manual routing for race-specific terrain rehearsal.

Paved routes are usually more predictable for threshold work. Trail-heavy routes can be better for aerobic durability and mechanical variety. Elevation preference should align with workout intent, not just route aesthetics.

Surface score checks match to your preferred terrain. Climb score checks if route elevation profile fits your chosen load. Suitability score is a data-informed quality hint from routing metadata.

Grade-adjusted pacing is planning context, not a hard prescription. Use it to avoid over-pacing climbs and to set realistic split expectations.

GPX export is widely supported, but watch ecosystems can simplify geometry and alter cue density. Validate imported courses on-device before race day.

Route confidence depends on mapping coverage and routing endpoint reliability. If fallback mode is active, treat terrain and surface insights as lower confidence.

Routing behavior and metadata are derived from the active ORS/OSM data source. See ORS API docs for request/response details.