Latitude longitude distance

Latitude and longitude are the coordinates almost every GPS chip, GIS export, and mobile check-in already stores, but converting two of those pins into a distance in kilometres is where many products silently go wrong. Treating decimal degrees as a flat plane stretches a degree of longitude as if it were constant from the equator to the pole, so the same change in longitude is a very different ground length in Quito than in Oslo. This latitude-longitude distance calculator applies the haversine formula on a sphere of mean radius 6371 kilometres and returns the great-circle arc length in kilometres only. Send four decimal-degree numbers, read one kilometre figure you can pin in tests, and skip map tiles, geocoders, and ellipsoidal solvers when a spherical crow-flies kilometre is the contract you need.

What latitude-longitude distance on a sphere actually measures

The shortest path between two points on Earth is not the straight line you draw on a printed map. Printed and web maps flatten a curved surface, so a ruler length in map millimetres is a projection artefact rather than a ground length. Latitude and longitude distance on a sphere instead measures the central angle between two geographic positions and multiplies that angle by the sphere radius to obtain arc length—the great-circle kilometre people mean when they ask how far apart two GPS pins sit as the crow flies.

Given latitudes φ1 and φ2 and longitudes λ1 and λ2 converted to radians, the haversine of the central angle satisfies hav(c) equals hav(φ2 minus φ1) plus the product of cos φ1, cos φ2, and hav(λ2 minus λ1), where hav of an angle is the square of the sine of half that angle.

The numerically stable evaluation used here is a equals sin squared of half the latitude difference plus cos φ1 times cos φ2 times sin squared of half the longitude difference, then c equals two times atan2 of the square root of a over the square root of one minus a, then kilometres equals R times c with R fixed at 6371 kilometres, the conventional mean Earth radius in GPS tutorials and spherical GIS snippets.

That sphere is not the WGS-84 ellipsoid, so polar flattening is ignored and results can differ by a small fraction of a percent from Vincenty or Karney geodesics; for store radii, analytics buckets, and crow-flies filters that gap is usually acceptable. Identical coordinates produce zero. Antipodal pairs produce a result near πR.

The arithmetic is pure and deterministic: no clock, no random seed, no network, and the same four numbers always yield the same rounded kilometre figure.

Where a distance in kilometres helps

Store locators, delivery-radius gates, and marketplace apps already hold shopper and venue coordinates and only need a crow-flies kilometre before they spend money on road routing. Logistics and warehouse prefilters drop hubs that sit outside a great-circle threshold so expensive drive-time engines run only on the shortlist.

Sports and hiking summaries, fraud signals that compare a billing city to a device GPS pin, and bulk CSV enrichment jobs that add a km column next to every origin-destination pair all fit the same pattern: you already have latitudes and longitudes, and you need a deterministic kilometre you can explain in a support ticket. Call the free in-browser latitude longitude distance calculator for classroom demos and quick checks without installing a GIS stack.

For turn-by-turn paths keep a routing engine; for legal property boundaries use an ellipsoidal solver and a local CRS.