Running Route Planner

Plan distance first, then apply your own running pace

For runners, mapped distance is usually more useful than a generic travel-time estimate. This route planner uses the pedestrian network as a baseline so roads and mapped paths are followed instead of drawing a straight line through buildings or rivers.

The routing engine does not know your fitness, target pace, temporary closures or every informal trail. Review the line on the map, use the distance for your training plan and export GPX when you want to carry the route into a watch or navigation app.

When this tool is useful

Use Running Route Planner when the question matches the method the page actually uses. Typical workflows include:

• Use the output as a planning or teaching reference, then move to an official or specialist source if the result affects legal, safety, engineering or financial decisions.
• Run the same workflow for locations in different countries while keeping units and assumptions consistent.
• Answer a one-off question about running route planner and keep the result tied to a visible map or explicit input.

Worked examples

These examples are meant to show how to interpret this kind of output, not to replace the values produced from your own inputs.

• Urban drive — A short route can take much longer than its distance suggests because of road classes, turns, bridges and local restrictions. Treat public routing times as planning estimates unless live traffic is explicitly provided.
• Cycling reach — A cycling-time area often stretches along continuous cycleways and contracts around rivers, limited crossings and steep terrain.
• Multiple stops — Changing stop order can reduce backtracking substantially. Route optimisation is most useful when several destinations are scattered across a city or region.

How to interpret the result

The most common errors come from using a correct result to answer the wrong geographic question. Keep these points in mind for Running Route Planner:

• Place route endpoints on roads, not rooftops. Routing engines snap points to the nearest drivable way, and a point in a river or a courtyard can snap somewhere surprising — nudging the pin to the nearest street makes results stable and explainable.
• When optimising many stops, keep the true origin first and let the engine order the rest; then sanity-check the result visually. Optimizers minimise distance, not your time windows — hard appointments still belong in manual order.

Limits & appropriate use

Routing's limits live in three places: data vintage, access reality and time modelling. The network is OpenStreetMap's current picture — new interchanges lag, private gates may be missing, seasonal ferries keep their own calendars. Access rules reflect mapped law, not today's roadworks. And durations are free-flow physics: speed limits and road classes without your city's sociology, so peak hours, weather and parking belong in your buffer, not in the engine's promise. The tools label all three limits on every result, because an unlabelled estimate is a trap.

What the stack does brilliantly is the reproducible core: the same stops, mode and engine give the same route to everyone, everywhere, which makes it a superb baseline for comparison, screening and planning. Escalation is domain-specific and well understood — professional dispatch adds live traffic and driver hours; logistics tenders add contracted networks; navigation products add certified maps. A free browser tool that hands you a clean, exportable baseline with its assumptions printed is not competing with those; it is feeding them.

• Live congestion and ETAs → traffic-aware commercial routing.
• Driver-hours and windows → transport-management systems.
• Certified navigation → licensed map products with update guarantees.

Data & methodology

Routes follow the available pedestrian network through the site's open routing providers; displayed duration is not a personalized running pace prediction. Routes and isochrones come from the FOSSGIS Valhalla engine on OpenStreetMap data (OSRM fallback for driving). Durations are free-flow estimates and are labelled as such on every result.

For source details, licences and model limitations, see Data Sources and Methodology.

Key terms worth knowing

Free-flow time

Travel time from speed limits and road classes, without congestion.

Travelling-salesman ordering

Reordering stops to minimise total route distance.

Go deeper: guides & original studies

Use these resources when you need the reasoning behind the calculation, a comparison with another geographic method, or an example of the same approach applied across a dataset.

Related tools

If this page answers only part of your question, these tools use a nearby but different method or dataset.