What does coordinate distance actually tell you?

A number is only useful when you know its model

Two coordinate pairs describe two positions. The distance between them still needs a definition. This tool chooses the shortest surface arc on a sphere. That gives you a reproducible comparison, rather than a route you can follow. The result is useful when the question is “how far apart are these coordinates under the same model?” It does not answer “how far will I travel?” Start by deciding which of those questions you mean. If you need a road journey, terrain-aware route or a safety-critical navigation measurement, this calculator is the wrong instrument. [1]

Read the coordinates before reading the result

Enter signed decimal degrees, with latitude first and longitude second. The form accepts latitude from −90 to 90 and longitude from −180 to 180. These are the input limits of this implementation. A minus sign is part of the value: do not remove it to make a coordinate look more familiar. If your source uses degrees, minutes and seconds, convert it to decimal degrees before entering it; this form does not silently interpret mixed notation. Check the order of each pair. A swapped pair can still fall inside the allowed ranges, so successful validation alone cannot tell you whether you entered the intended position.

The calculation, in plain language

The implementation first converts the input angles from degrees to radians. It applies the haversine relation to the differences in latitude and longitude, then turns the resulting central angle into an arc length by multiplying by the chosen sphere radius: 6,371 kilometres. Both points use the same sphere and the same radius. There is no lookup, location search or map service behind the answer. This is why the tool can run entirely offline. It also means the model does not gain extra accuracy from the number of decimal places you type. [1]

Three checks you can reproduce

Try (0, 0) and (0, 0): the result is zero because the two input positions coincide. Next try (0, 0) and (0, 90). In this synthetic example the central angle is one quarter of a full turn, so the model gives approximately 10,007.5 kilometres. Finally try (0, 0) and (0, 180): the model gives approximately 20,015.1 kilometres. These are calculated examples, not measurements of journeys or named places. Swap the start and end points: separation should stay the same. Switch units: the underlying calculation should stay the same too. These checks help distinguish a change in presentation from a change in the model.

Precision is not the same as accuracy

The result panel rounds the displayed distance to one decimal place. That is a presentation choice, not an accuracy guarantee. The spherical model omits the Earth’s ellipsoidal shape and terrain. More displayed digits would not remove those assumptions. If two comparisons are close, avoid treating the last displayed digit as a decisive real-world difference. Keep the original inputs with your result, note the model and radius, and report the units. The local permalink preserves the coordinate inputs and selected unit, so you can reproduce the calculation. [1]

Use the result responsibly

For a quick comparison, calculate both pairs using identical settings and compare the resulting surface separations. For a worksheet, include the input pairs alongside the answer so the reasoning is inspectable. For a route-planning question, stop and obtain an appropriate routing method instead. No traffic conditions, borders, transport options or surface obstacles are considered here. This page and the calculator explain a limited mathematical method; they do not supply geographic demand evidence, commercial evidence or a safe navigation route. The reviewed evidence covers the calculation method only. Broader geography claims require separate research before they can be added. [1]

Evidence & provenance

[1] Latitude/longitude calculations, Movable Type Scripts / Chris Veness. The existing canonical source ledger records a manual method review on 7 October 2026. Evidence covers the spherical haversine method only.

Reference identifier: www.movable-type.co.uk/scripts/latlong.html

Synthetic worked examples are calculated locally. The editorial explanation is original; the stored method note is a paraphrase, not a captured source document. No source is fetched by this site.