The distance calculator measures the shortest surface arc between two coordinates on a spherical Earth model. This is often called great-circle distance. It is useful for comparing broad geographic separation, but it does not follow streets, railways, borders or actual flight paths. Understanding that boundary prevents a precise-looking number from becoming an unrealistic journey estimate. This guide explains the calculation and the questions it can answer honestly.
Reference table
| Item or scenario | Value or choice | What to remember |
|---|---|---|
| Model | Sphere, radius 6,371 km | Approximate surface geometry |
| Input | Two latitude/longitude pairs | No address lookup |
| Output | Kilometers and miles | Same distance, different units |
| Excluded | Roads, schedules and accessibility | Requires route-specific sources |
Think of a surface arc, not a tunnel through Earth
On a globe, the shortest surface path between two points is an arc of a great circle. The calculator uses the Haversine formula with a mean Earth radius of 6,371 km. A flat map may make that arc appear curved, particularly across large distances, because map projections distort the sphere. The reported number is not the straight chord through the planet. It is still an approximation because Earth is not a perfect sphere. For broad travel planning that distinction is usually less important than whether the points represent the places you actually intend to compare.
Choose coordinates that match the question
A city-center coordinate answers a city-center comparison. An airport coordinate answers a different comparison. Large metropolitan areas can have several airports far apart, so substituting the center may introduce a meaningful endpoint difference. The built-in example coordinates on the tool page are illustrative and rounded. For a specific plan, obtain verified coordinates for the actual endpoints from an appropriate mapping source. The tool does not geocode addresses or decide which station, terminal or neighborhood you meant. It accepts the points exactly as you enter them.
For the next input check, use Straight-Line Distance Calculator. Its result should retain the assumptions described here.
Do not infer route accessibility
Two points can be geographically close while their practical journey is long because of water, terrain, restricted roads, borders or missing connections. Conversely, a convenient rail or flight connection can make a larger geographic separation easy to manage. The distance output contains none of those route features. Do not use it for navigation or crossing decisions. Its best use is a scale check or a comparison of geographic spread before consulting route-specific information. If the itinerary depends on a particular connection, check schedules and actual route options separately.
Avoid turning distance directly into travel time
Dividing a great-circle distance by an assumed speed produces a hypothetical movement time, not a door-to-door itinerary. Airports, terminals, waiting, transfers and the real route can dominate the experience. The site therefore does not label the distance result as a flight or driving duration. For a daily plan, use a route-specific time estimate as an input to the itinerary pace tool. Add preparation and waiting time according to the event. This keeps the geographic comparison useful without letting it pretend to answer a logistical question it does not contain enough data to solve.
A related planning question is covered in Latitude and longitude: entering coordinates without swapping them.
Why small output differences can be harmless
Two distance tools can report slightly different results for the same named cities. One may use different city-center coordinates, another may use an ellipsoidal Earth model and another may round earlier. Before deciding that one is broken, compare the actual numeric endpoint pairs and model descriptions. If the endpoints differ, the tools are answering different questions. If only the model differs, a modest numerical difference can be expected. For ordinary itinerary screening, the existence of a practical route usually matters far more than a small geometry discrepancy. Do not choose the larger decimal count as proof of greater accuracy. Precision in display is separate from accuracy in inputs and assumptions. If you need survey-grade or navigation-grade measurement, this spherical travel utility is outside that purpose. Keep its result as an approximate geographic scale check. The independent value is repeatable arithmetic with an explicit model, not a claim to outperform every geodesic calculation or mapping service available for specialized tasks.
Worked example
Worked example: Compare rounded central coordinates for London, 51.5074 latitude and −0.1278 longitude, with Paris, 48.8566 and 2.3522. The calculator gives roughly 344 km along the great-circle model. That result describes those central points. It does not give rail-track distance, a road route, an airport-to-airport flight path or travel duration. To plan a day using the connection, obtain the relevant departure location, arrival location and route time separately. If you replace city-center coordinates with airport coordinates, you have changed the question, so preserve the endpoint labels with the saved distance result.
Before you finish
- Name the exact endpoints before collecting coordinates.
- Check latitude and longitude order.
- Label the result as great-circle or straight-line distance.
- Obtain actual route and schedule information separately.
- Use route-specific time in the daily itinerary calculation.
Your next step
A bounded answer is more useful than an overconfident one. Great-circle distance helps you understand scale and compare endpoint separation. It becomes misleading only when the endpoint labels disappear or the output is presented as a route. Keep both the coordinate source and the model note beside any distance you share.
Continue with Kilometers and miles: comparing travel distances consistently. When your plan needs the next calculation, open Itinerary Pace Calculator and carry over only the inputs appropriate to that tool.