Distance Between Places
Calculate high-precision geodesic distance, straight-line Great-Circle distance, compass bearing, and geographic midpoint between any two points or addresses.
The Distance Between Places calculator computes the exact straight-line distance, compass bearings (azimuths), and geographic midpoint between any two addresses, cities, or coordinates using Charles Karney WGS84 ellipsoidal geodesic algorithms. It displays distance in miles, kilometers, and nautical miles alongside driving distance comparisons and GeoJSON/KML line exports.
Select Measurement Endpoints
New York (JFK)
40.6413°, -73.7781°London (LHR)
51.4700°, -0.4543°Calculated Geodesic Distance
- Initial Compass Bearing
- 51.4° (True North)
- Final Compass Bearing
- 108.0°
- Geodesic Midpoint
- 52.2167°, -41.3027°
- Rhumb-Line Distance
- 3578.26 miles
Distance Calculator Technical Specifications & Standards
WGS84 (EPSG:4326)
Standard global ellipsoidal coordinate reference system
Karney Geodesics
Sub-millimeter numerical accuracy
GeoJSON · KML · CSV · SVG
Compatible with QGIS, ArcGIS, Google Earth & CAD
100% Client-Side
Calculations run in-browser. Zero coordinate logging.
How to Use the Distance Between Places
Follow this step-by-step procedure to execute precise spatial measurements and export results.
- 1Set origin point (Point A): Type an address, city name, airport code (e.g. JFK), or decimal coordinates into the Point A input box, or click directly on the map.
- 2Set destination point (Point B): Enter your destination address, city name, or coordinates in Point B, or click a second location on the map canvas.
- 3Select distance units: Switch between Miles (mi), Kilometers (km), Nautical Miles (NM), Feet (ft), or Meters (m).
- 4Analyze bearings & midpoint: Review the initial compass bearing (forward azimuth), final bearing, and exact geographic midpoint coordinates.
- 5Export route path: Click "Export Data" to download the geodesic flight path as GeoJSON, KML (for Google Earth), or CSV coordinates.
Geodesic Precision vs. Competitor Mapping Approaches
Most legacy mapping utilities (such as CalcMaps and FreeMapTools) rely on planar Web Mercator projections or spherical approximations, causing significant mathematical distortion at higher latitudes. GeoMap Suite computes exact ellipsoidal geodesics on the WGS84 reference ellipsoid.
| Calculation Model | Mathematical Basis | Distortion on WGS84 | Standard Tools | Practical Application |
|---|---|---|---|---|
| Planar (Web Mercator) | Cartesian dx² + dy² | 10% to 200%+ error | CalcMaps / Simple map tools | Distorts drastically away from equator. Inaccurate for true distance. |
| Spherical Great-Circle | Haversine (R = 6,371 km) | Up to 0.5% (~5 km/1,000 km) | Basic Google Maps wrappers | Ignores Earth's polar flattening. Reasonable for rough estimates. |
| GeoMap Suite Ellipsoidal | Karney Direct/Inverse WGS84 | < 15 nanometers (<0.0001%) | GeoMap Suite | Geodetic surveying, maritime, flight paths & legal boundary analysis. |
Worked Example 1: Transcontinental Distance (New York JFK to London Heathrow LHR)
An aviation route planner calculates the Great-Circle / Geodesic flight path between New York JFK (40.6413° N, 73.7781° W) and London Heathrow LHR (51.4700° N, 0.4543° W).
Input Parameters
- Origin (JFK)
- 40.6413° N, 73.7781° W (New York JFK)
- Destination (LHR)
- 51.4700° N, 0.4543° W (London LHR)
- Earth Model
- WGS84 Reference Ellipsoid
Computed Outputs
- Geodesic Distance
- 3,451.61 Miles (5,554.82 km)
- Nautical Distance
- 2,999.36 Nautical Miles (NM)
- Initial Compass Bearing
- 51.58° (NE)
- Final Compass Bearing
- 117.84° (ESE)
- Geographic Midpoint
- 52.3361° N, 37.8924° W
Step-by-Step Mathematical Process
- Compute ellipsoidal geodesic distance using Karney inverse problem: s12 = 5,554,821.5 meters (5,554.82 km / 3,451.61 miles / 2,999.36 Nautical Miles).
- Calculate initial forward azimuth: α1 = 51.58° (North-East, departing JFK).
- Calculate final arrival azimuth: α2 = 117.84° (South-East, arriving LHR).
- Evaluate geodesic midpoint: 52.3361° N, 37.8924° W (mid-North Atlantic Ocean).
Worked Example 2: Intercity Distance (Los Angeles to San Francisco)
A commuter compares the straight-line geodesic distance vs. road driving distance between Los Angeles City Hall (34.0537° N, 118.2427° W) and San Francisco City Hall (37.7793° N, 122.4192° W).
Input Parameters
- Origin (LA)
- 34.0537° N, 118.2427° W
- Destination (SF)
- 37.7793° N, 122.4192° W
- Method
- WGS84 Inverse Geodesic vs Interstate-5 Road Network
Computed Outputs
- Straight-Line Distance
- 347.42 Miles (559.12 km)
- Road Driving Distance
- 383.0 Miles (616.4 km)
- Initial Bearing
- 319.46° (NW)
- Detour Factor
- 1.10x
Step-by-Step Mathematical Process
- Calculate straight-line geodesic distance: s12 = 559.12 km (347.42 miles).
- Compute road network driving distance via I-5 N: ~616.4 km (383.0 miles).
- Calculate detour factor: 383.0 mi / 347.42 mi = 1.102x (10.2% detour over straight line).
Understanding Your Results & Practical Interpretation
Geodesic vs. Rhumb Line vs. Driving Distance
A geodesic (Great Circle) is the absolute shortest path between two points on the curved surface of the Earth. A rhumb line is a path of constant compass bearing (longer, but simpler for manual marine navigation). Driving distance follows actual paved highways and city streets, navigating around topography, lakes, and urban grid networks.
Why Initial and Final Bearings Differ
Because lines of longitude converge at the poles, following the shortest geodesic path across long distances requires constantly changing your compass heading. The initial bearing is your heading at departure; the final bearing is your heading upon arrival.
Practical Applications & Real-World Use Cases
Aviation & Marine Route Planning
Calculate flight path nautical miles, true compass bearings, and waypoints for flight simulators and navigation.
Telecommunications & Line-of-Sight Engineering
Compute exact distances and azimuths between microwave towers, radio repeaters, and satellite ground stations.
Logistics Mileage Verification
Audit freight billing, air cargo mileage tiers, and straight-line service agreements.
Mathematical Methodology & Geodetic Accuracy
Karney Inverse Geodesic Algorithm (WGS84)
Evaluates the exact ellipsoidal distance s12 and initial/final azimuths (α1, α2) between two latitude/longitude points on the WGS84 ellipsoid using Newton method convergence of elliptic integrals.
(s12, α1, α2) = Geodesic.WGS84.Inverse(lat1, lon1, lat2, lon2)Limitations & Boundary Conditions
- •Measures straight-line geodesic distance along the reference ellipsoid, not driving road distance.
- •Does not account for terrain topography (elevation ascents and descents).
- •For near-antipodal points (180° apart on opposite sides of Earth), multiple shortest paths exist.
Troubleshooting & Geographic Edge Cases
Why does the straight-line path appear curved on the map?
The map uses the Web Mercator projection (a flat rectangular representation of Earth). The shortest path on a 3D sphere/ellipsoid (a geodesic) appears as a curve on flat 2D maps, especially on east-west routes at high latitudes.
How do I measure distance in nautical miles?
Select "Nautical Miles (NM)" from the unit toggle. One international nautical mile is defined as exactly 1,852 meters (approx. 1.1508 statute miles).
Frequently Asked Questions
"As the crow flies" refers to the direct, straight-line geodesic distance between two points on the Earth surface without following roads, turns, or terrain obstacles.