January 12, 2026 · 7 min read · MapBench editorial
Planning a Road Trip With Nothing but Free Map Tools
Every good road trip starts as a argument about stops, and every argument about stops ends when somebody puts them all on one map. My first move is always the multi-stop route planner: drop the start, then every 'we have to stop here' the group produces, cap it at twelve, and let the engine draw the honest version of the day. The per-leg table does the diplomatic work for you — nobody can claim a detour is 'on the way' once the kilometres are on screen.
Then I press the optimize button, because humans are confidently bad at stop ordering. On a recent eight-stop coastal run, the reordered route cut a fifth off the total distance without dropping a single stop — the savings were all backtracking we couldn't see from the kitchen table. Keep your first stop fixed as the origin (home, the rental desk, wherever) and let the middle reorder itself.
Budgeting the boring parts
Fuel comes next. I feed the same two endpoints into the fuel cost calculator with the car's observed consumption — not the brochure number, the number from the last three fill-ups — and the trip stops being abstract. Round trip, one tank or two, cost per person: the arithmetic that kills bad ideas early is exactly the arithmetic people skip.
The drive-time map earns its place at lunch stops. Drop the pin on a candidate town, look at the 30-minute ring, and pick a viewpoint or beach inside it instead of gambling on 'something along the road'. Isochrones follow roads, not circles, so the ring already knows about the bridge you'd otherwise discover the hard way.
The file that saves the day
Last step: export the route as GPX and load it into whatever navigation app the car tolerates. When signal dies in the third tunnel of the day, the downloaded track is the trip. And afterwards, that same GPX opens in the GPX viewer to produce the elevation profile everyone asks about — the climb nobody noticed, now with a chart.
None of this costs anything, none of it needs an account, and every number came with its method printed next to it. A road trip planned like that isn't less spontaneous — it's spontaneous in the right places, because the boring decisions were made at the kitchen table where they belong.
The toolkit behind this post, in depth
Multi-Stop Route Planner
Real journeys have waypoints. Add up to twelve stops — by search or by clicking the map — and this planner returns one continuous route with per-leg distance and time plus grand totals, on your choice of driving, walking or cycling networks via the Valhalla engine. Stops can be reordered manually, reversed with one click, or optimised automatically: the optimizer asks the routing engine to solve the visiting order that minimises total distance while keeping your first stop fixed as the origin — the travelling-salesman solution couriers and sales drivers need.
The finished route exports as GPX, ready to load into OsmAnd, Organic Maps, Garmin and other navigation apps, which turns the page into a genuine dispatch-lite workflow: build, optimise, export, drive. Times remain free-flow estimates and the interface labels them as such; unreachable combinations (island hops, closed borders) produce explained errors rather than imaginary routes. Whether it is a weekend road trip, a service call list or a school-run reorganisation, the planner keeps every number inspectable leg by leg, and every link shareable.
Route Optimizer (Best Stop Order)
Humans are surprisingly bad at the travelling-salesman problem, and surprisingly confident about it. Type your stops in any 'logical' order and this tool shows what the routing engine knows: reordering the intermediate stops on the real road network typically shaves 15–30% off the total distance, because intuition underweights cross-town backtracking that the engine prices exactly. Your first stop stays fixed as the origin — the depot, the office, home — and the rest fall into the sequence that minimises driving.
The reordered route draws on the map with the new total, so the saving is visible rather than asserted, and a quick visual scan catches the classic failure mode of bad optimisation (a criss-crossing path) before it costs you a morning. For a dozen stops the engine's heuristic is effectively optimal; the page says plainly that fleet-scale problems belong to dedicated logistics software. It is the analytical heart of the delivery planner and the multi-stop route planner, offered bare: bring your stops, leave with the order. Export happens in the sibling tools, and the shareable URL keeps the solution reproducible for whoever drives tomorrow.
Fuel Cost Calculator
Distance is geography; the fuel bill is arithmetic on top of it. This tool closes the loop: set two points, fetch the real road distance from the routing engine (or switch to straight-line for a quick bound), then enter what your car and your pump actually report — consumption in L/100 km or MPG, price per litre or gallon — and read fuel burned, one-way cost and round trip. The unit toggle respects which dialect your dashboard speaks, and the conversions underneath are exact.
The honesty notes are part of the result: distance follows the network, consumption follows your foot, and hills, traffic and air conditioning live in the gap between the official figure and your real one — so the page invites you to use your observed consumption, not the brochure's. That single habit turns the output from a guess into a budget. It is the companion piece to the driving distance calculator and the walking-time tool, and together they make the classic comparison — drive, share, or walk — quantifiable in money, minutes and calories. Free, private, and shareable via the URL like everything else here.
Drive Time Map (Isochrone)
A radius circle pretends you move equally in all directions; reality has motorways, rivers and one-way grids. This tool draws isochrones — genuine reachable-area polygons computed by the Valhalla routing engine on the road network — for the travel mode and time contours you choose, from 5 to 60 minutes. The polygons stretch along fast corridors and stop at barriers, telling the truth about accessibility that circles cannot. Choose drive, walk or cycle and up to four contours per run.
That makes the page a decision instrument: house hunters see the real 30-minute commute envelope, restaurants visualise delivery reach, clinics map patient access, and planners compare before/after scenarios for a new bridge or line. Polygons export as GeoJSON for reports and GIS work, and the shareable URL preserves centre, mode and contours. The shapes' jaggedness and holes are data honesty, not bugs — networks are irregular. When you need geometric rather than temporal reach, the map radius tool provides the complementary circle.
GPX Viewer
Open a GPX file from a bike computer, hiking app, drone or handheld and the tool draws every track, route and waypoint on the map and computes the full stat sheet: total distance, elevation gain and loss, minimum and maximum elevation, and duration whenever timestamps exist. An elevation profile chart shows the shape of the day, with the same local, private parsing as the rest of the file tools — your activity never leaves the browser.
Methodology notes keep the numbers honest: gain sums positive differences between consecutive trackpoints, and raw GPS elevation is noisy, so gain figures can look inflated — that is the source data, not the math. Missing timestamps are reported as missing rather than faked. Conversions export the same geometry as GeoJSON or KML, and a cleaned GPX re-download normalises the file for other apps. Pair it with the elevation profile tool to compare a recorded track against terrain truth from the Copernicus DEM.
How routing engines turn streets into answers
A routing engine ingests the road and path network as a graph — intersections as nodes, street segments as edges, each with speed, access rules and geometry — then searches it for the cheapest path under a costing model. Driving, walking and cycling are genuinely different networks: pedestrians slip through footways and cut-throughs cars cannot use, cyclists avoid motorways and steep grades, cars ignore steps entirely. That is why the same two points produce three different routes and three different times, and why comparing them is often the most informative thing you can do with a trip.
Isochrones invert the question from 'how long to get there' to 'everywhere reachable in this time'. A proper isochrone is not a circle: it grows along fast corridors, pinches at bridges and rivers, and holes around barriers. When the shape looks jagged, that is the network telling the truth. These polygons make honest service-area and catchment maps — the circle version always over-promises across the river and under-promises along the motorway.
One caveat belongs on every routing result: free public engines report free-flow times derived from speed limits and road classes, not live congestion. Treat a 25-minute result as the physics of the network; your city's rush hour adds the sociology. Multi-stop optimisation adds a second layer of honesty: reordering stops to minimise distance is the travelling-salesman problem, and engine heuristics solve it beautifully at driver scale — the difference between a sensible morning and a wasteful one is frequently twenty percent of the kilometres.
Reading routes like a dispatcher
A route result is a claim about a network, and networks have personalities. Motorway cities produce long fast fingers in their isochrones; river cities show comb shapes; border towns pinch. Learning to read those shapes turns a pretty polygon into diagnostic information: a missing finger is a missing interchange, a hole is a barrier, a lopsided blob is a one-way system. The same literacy applies to stop ordering — an optimized route that criss-crosses itself is either a data error or a constraint you forgot to state, because distance-minimising engines don't voluntarily draw bows on their own paths.
Time estimates deserve the same reading discipline. Free-flow times are the network's physics; your city adds sociology on top. Dispatchers handle this with explicit buffers by area and hour, and you can too: keep the engine's number as the reproducible baseline, store your buffer as policy, and present the sum. When someone asks 'how long will it take', the honest answer has two numbers and a reason — which is precisely what a good tool's labels should invite you to give.
- Snap endpoints to visible roads before calculating; stable inputs, stable results, explainable diffs.
- Keep the engine's free-flow figure and your congestion buffer as separate fields; policies change, physics doesn't.
- Export isochrones with their mode and contours in properties; a polygon without its parameters is unverifiable.
- After auto-optimising stops, scan the drawn path for self-intersection — the cheapest QA in logistics.
Honest limits & when to escalate
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.
- Accessibility-critical walks → ground truth; curb data is still emerging everywhere.
Step-by-step masterclass
- Pin endpoints on roads — Drag each pin to a visible street before calculating; snapping surprises are the top cause of 'weird' routes, and road-pinned inputs make results stable and explainable.
- Pick the mode that matches reality — Driving, walking and cycling follow different legal networks; comparing all three is often more informative than any single answer.
- Read the shape, not just the total — Isochrone fingers follow fast corridors and holes mark barriers; a route that criss-crosses itself after optimisation is a cue to re-check your stop list.
- Separate physics from policy — Keep the engine's free-flow figure and your congestion buffer as distinct numbers; present the sum with its parts and your estimate becomes defensible.
- Export for the next step — GPX for navigation apps, GeoJSON for reports; embed mode and contours in properties so the file is auditable without archaeology.
Routing quality follows OpenStreetMap's coverage: excellent across Europe, North America and most of East Asia, good in South America's cities, patchier in remote regions — and access rules (one-ways, pedestrian zones) reflect local mapper knowledge, which is why the engine sometimes knows a shortcut your satnav doesn't.
Tips & common mistakes
Add a congestion buffer to any free-flow travel time: 20–40% in peak urban areas is a sane rule of thumb, and the interface labels its times as free-flow for exactly this reason. For appointments, plan with the buffer; for physics, trust the raw number.
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.