September 19, 2026 · 7 min read · MapBench editorial
Straight-Line Distance vs Road Distance: Why Your Trip Is Longer Than the Map Says
Two cities 800 km apart ‘as the crow flies’ can easily be 1,000 km by highway. The crow is not stuck with interchanges, border crossings, or a lake in the way. Straight-line (great-circle) distance is still useful: it is the physical lower bound, a fair way to compare separation, and the number many scientific and aviation contexts care about. It is a bad promise for arrival time in a car.
Great-circle, in plain language
On a sphere, the shortest surface path between two points is an arc of a great circle. Flat maps stretch that arc into a curve that looks wrong until you remember the projection is lying for your convenience. Tools that report crow-flies distance are computing that arc (or a very close spherical approximation), not counting lane-miles.
Road distance and driving time
Road distance follows the network: the sum of segments a router chooses. Driving time folds in speed limits and, in better engines, typical traffic. Multi-stop days add sequencing: the order you visit points can change total kilometres more than any single ‘optimisation tip’ on a blog. If you only compare straight-line legs, you will under-budget fuel and hours.
- Planning a flight-style mental model → crow-flies / great-circle
- Planning a road trip or delivery day → driving distance and time
- Meeting someone in the middle → halfway tools still use geography; roads may not meet there
Fuel and cost are not proportional to crow-flies
Fuel cost calculators that only see straight-line distance will smile optimistically. Use road distance when money is involved. Elevation and congestion still sit outside many free models — treat the result as a plan, not an invoice.
The toolkit behind this post, in depth
As the Crow Flies Distance
'As the crow flies' is the everyday name for great-circle distance: the shortest possible path between two points along the Earth's curved surface, ignoring roads, fences and terrain. Enter two places or coordinates and this tool computes that path with the haversine formula, reporting it in miles, kilometres, meters, feet or nautical miles plus the initial compass direction. The map's dashed line shows the true shortest path — and on long east-west routes it visibly reminds you why flat maps lie: the straight line on a globe projects as a curve.
Straight-line distance is the right metric whenever nothing on the ground constrains movement: radio and cellular coverage, drone and aircraft range, bird and seed dispersal, light and sound propagation, insurance radius clauses, and quick geographic comparisons. When roads do matter, the driving distance tool provides the on-road counterpart so you can see the detour penalty side by side. Both endpoints accept names, addresses or raw coordinates, results convert live between units, and the shareable URL reproduces your exact pair — free, private and instant in the browser.
Distance Between Two Places
Search any two places on Earth — cities, addresses, airports or raw coordinates — and this tool returns the straight-line distance between them in miles, kilometres, meters, feet or nautical miles, together with the initial bearing and its compass point. The calculation is a great-circle measurement on the WGS84 sphere using the haversine formula: the same geometry behind flight planning, and accurate to within about 0.3% of a full ellipsoidal geodesic. A dashed line on the map shows exactly what is being measured, and swapping A and B takes one click.
Use it for quick reality checks — how far is the airport, how big is this country, how far apart are two offices — and as the entry point to deeper tools: the bearing calculator for direction, the halfway tool for meet-ups, the driving calculator for road distance and time. Because straight-line distance is the physical lower bound, it is the right number for radio range, wildlife movement, flight baselines and service-radius thinking. Coordinates are accepted in decimal or DMS, results convert across all units live, and the URL stores both points so any calculation is shareable and reproducible.
Driving Distance Calculator
Straight-line tools tell you the planet's answer; this one tells you the road's answer. Enter a start and destination and the tool routes along the actual OpenStreetMap road network using the open Valhalla routing engine, returning true driving distance and an estimated travel time derived from road classes and speed limits — with a fallback to the OSRM engine if the primary server is busy. The route draws on the map so you can see exactly which corridors were chosen before you trust the number.
One transparency note is part of the result: durations are free-flow estimates, not live traffic, so rush-hour city legs need a buffer — the label says so every time. Islands, closed borders or points off the network produce a clear, explained error instead of a fabricated route. This is the tool for logistics quotes, commute comparisons, trip planning and reimbursement documentation; when you need more stops, the multi-stop planner extends the same engine to full itineraries, and the straight-line calculator shows the theoretical minimum for comparison.
Drive Time Map
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.
Halfway Between Two Places
Meeting a friend halfway, choosing an overnight stop, or splitting a relocation? This tool computes the geographic midpoint of two places on the sphere — the point exactly half the great-circle distance from each. That is not the same as averaging latitudes and longitudes, which skews badly over long distances and breaks entirely across the date line; the spherical midpoint follows the actual surface path, so the answer is geometrically honest even for Sydney–Santiago pairs.
After computing the midpoint the tool reverse-geocodes it, telling you the nearest named place — which is often the real decision you need ('so we meet near…'). If the midpoint falls in open ocean or wilderness, the page says so plainly and still gives you coordinates to pivot from. The result is pinnable on the map, copyable in decimal or DMS, and shareable via URL. Combine it with the driving calculator to compare each party's road time, or the cities-within-radius tool to find the nearest sizeable town when the exact midpoint is impractical.
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.
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.
The geometry of distance: why the crow flies in arcs
Distance on a planet is not distance on paper. The shortest path between two points on Earth is an arc of a great circle — a circle whose centre is the planet's centre — and every serious distance tool computes that arc, not a straight line on a flat map. The standard formula, haversine, turns two latitudes and a longitude difference into a central angle and multiplies by Earth's mean radius. On the WGS84 sphere it agrees with survey-grade ellipsoidal geodesics to about three parts in a thousand, which is far tighter than the uncertainty in most real questions, like where exactly 'the city centre' is.
Bearings complete the picture. The initial bearing is the compass angle you would steer at departure; on a great circle it drifts continuously as the route crosses meridians, so the final bearing at arrival is generally different. That drift is why intercontinental flights arc toward the poles on flat charts — they are not detouring, they are taking the shortest path, and the map is what bends. Tools that report a single 'direction' for a long route are hiding this geometry; the honest display shows initial bearing, final bearing and the compass point for humans.
Finally, keep the family of distances distinct in your head: straight-line (the physical lower bound, right for radio and wildlife), road distance (what you drive, always equal or longer), and travel time (road distance reshaped by speed limits and network structure). Comparing the first two tells you how much geography taxes your route — a number that is itself interesting, whether you are planning a commute or pricing a delivery zone.
Distance literacy: choosing the right yardstick
Most distance errors are category errors: quoting straight-line where a road is meant, or a road where a schedule is meant. A useful discipline is to name the yardstick aloud in every sentence that uses a number — 'as the crow flies', 'by road', 'at free-flow speeds'. The three form a ladder of realism, each rung adding assumptions: the sphere's geometry, the network's topology, then human speed limits. Crow-flies is reproducible forever from coordinates alone; road distance depends on the mapping vintage; travel time depends on the traffic model. Knowing which rung your decision stands on tells you how much it can move.
The ladder also teaches when disagreement is a bug and when it is truth. If your road distance is shorter than your straight-line distance, something is wrong — topology cannot beat geometry. If two straight-line tools disagree by more than half a percent, one is using flat math or a wrong radius. And if bearings from A→B and B→A don't differ by roughly 180° (convergence aside from exact antipodal oddness), a tool is faking the back-bearing. These consistency checks cost seconds and catch most published nonsense.
- State the yardstick in every sentence that carries a number; ambiguity is the enemy, not imprecision.
- Use nautical miles and bearings together for anything marine; statute miles and compass points for prose.
- For multi-point studies, export the matrix as CSV and let the spreadsheet hold the single source of truth.
- Check tool sanity with known pairs (Equator quarter ≈ 10,018 km; London–Paris ≈ 344 km) before trusting exotic ones.
Honest limits & when to escalate
The honest limits here are about category, not quality: great-circle math is near-exact, but it answers 'how far over the surface', not 'how far as driven, flown or walked'. Airline distances follow airways and winds; odometers follow detours; hikers follow switchbacks. Quoting a straight-line number into a fuel budget is the classic misuse, which is why the tools keep the ladder visible — crow-flies, road, time — and label each rung. A second limit is definitional: 'city to city' means mapped centre to mapped centre, and a suburb-to-airport question is a different measurement wearing the same sentence.
Within those bounds the numbers are durable: reproducible from coordinates alone, stable across tools that use the same radius convention, and accurate to a fraction of a percent of geodetic truth. The escalation path is short and rarely needed — ellipsoidal libraries (Karney's algorithms) for survey-grade millimetres, the routing engine for network truth, and the airline's schedule for invoice truth. Knowing which authority owns which number is the entire craft of distance literacy.
- Survey-grade millimetres → ellipsoidal geodesic libraries, not sphere math.
- Fuel and schedule planning → road routing plus your congestion buffer.
- Airline invoicing → carrier distance tables (airways ≠ great circles).
- Legal boundary lengths → licensed survey, never a clicked polygon.