Haversine Distance Examples for Beginners

The fastest way to understand haversine distance is to see it worked through on familiar routes. This beginner-friendly reference collects several fully solved Indian examples so you can follow the pattern, check your own answers, and build confidence. Every example uses Earth’s mean radius of 6,371 km and decimal-degree coordinates you can copy straight into our calculator.

Key takeaway: Once you have seen two or three examples, the pattern becomes automatic: convert to radians, find the differences, apply the formula, and multiply by 6,371.

The Four Steps, Recapped

Every example below follows the same recipe. First, convert all four coordinate values from degrees to radians by multiplying by π/180. Second, find Δlat and Δlon, the differences between the two points. Third, apply a = sin²(Δlat/2) + cos(lat1)·cos(lat2)·sin²(Δlon/2) and c = 2·atan2(√a, √(1−a)). Fourth, multiply c by 6,371 km to get the distance.

Example 1: Delhi to Mumbai

Delhi (28.6139, 77.2090) to Mumbai (19.0760, 72.8777). Working through the steps gives a = 0.008095 and c = 0.18019 radians, so the distance is 6,371 × 0.18019 = 1,148 km. The road distance on NH-48 is about 1,400 km.

Example 2: Mumbai to Bengaluru

Mumbai (19.0760, 72.8777) to Bengaluru (12.9716, 77.5946). Here a = 0.004395 and c = 0.13268 radians, giving 6,371 × 0.13268 = 845 km straight-line, against roughly 980 km by road.

Example 3: Delhi to Kolkata

Delhi (28.6139, 77.2090) to Kolkata (22.5726, 88.3639). This yields a = 0.010431 and c = 0.20462 radians, so the distance is 6,371 × 0.20462 = 1,304 km. The drive is closer to 1,500 km.

Example 4: Chennai to Hyderabad

Chennai (13.0827, 80.2707) to Hyderabad (17.3850, 78.4867) resolves to about 515 km great-circle distance, with a road distance near 625 km on NH-44.

Reference Table of Indian Routes

Benefits of Studying Worked Examples

Worked examples turn an abstract formula into a repeatable skill. By following the same four steps on familiar routes, beginners internalise the process far faster than by reading the formula alone. The examples also give you known-good answers to test your own calculations or code against, which is invaluable when you are debugging. And because the routes are real Indian metro pairs, the numbers stay memorable and easy to sanity-check against your own travel experience.

Challenges and Limitations

Remember that every figure here is a straight-line distance and will always be shorter than the actual journey. The circuity ratio column shows just how much longer the roads are, and that ratio varies with terrain: flat routes like Delhi–Jaipur have low ratios, while hilly or river-crossing routes are higher. The examples also assume a spherical Earth, so they carry the usual half-percent error, and they ignore altitude entirely.

Common Mistakes to Avoid

• Skipping the radian conversion. Every example depends on it; degrees give wrong answers.
• Copying coordinates inaccurately. A single transposed digit can move a city hundreds of kilometres.
• Comparing haversine to road distance as if they should match. They never will; roads are always longer.
• Using a mileage radius by accident. Stick to 6,371 km for kilometre results.
• Rounding mid-calculation. Keep precision until the final multiplication.
• Forgetting the circuity factor. Add 15–30% when you need a realistic travel distance.

Best Practices and Expert Recommendations

• Practise on your own city pairs. Pick two towns you know and verify the answer feels right.
• Keep a reference table. Save common routes so you can spot-check new calculations.
• Verify with the calculator. Cross-check every hand calculation against the tool.
• Note the circuity ratio. Track it for routes you use often to improve road estimates.
• Use authoritative coordinates. Pull from Bhuvan or Survey of India for accuracy.
• Label your results. Always mark whether a figure is straight-line or road distance.

Example 5: Delhi to Jaipur

Delhi (28.6139, 77.2090) to Jaipur (26.9124, 75.7873) is a short, flat route popular with weekend travellers. The haversine calculation gives about 240 km straight-line, while the Delhi–Jaipur Expressway drive is around 280 km. The low circuity ratio of roughly 1.17 reflects the fact that this corridor runs across open plains with a modern, near-direct expressway.

Example 6: Ahmedabad to Surat

Ahmedabad (23.0225, 72.5714) to Surat (21.1702, 72.8311) is an even shorter Gujarat route. The great-circle distance works out to about 210 km, against a road distance of roughly 265 km on NH-48. Short routes like this show that the haversine method is just as reliable over a couple of hundred kilometres as it is across the whole country.

How to Check Your Own Answer

Whenever you compute a haversine distance by hand, run three quick sanity checks. First, confirm your answer is smaller than the known road distance — if it is larger, you have made an error. Second, check that the distance feels right against your own knowledge of Indian geography; two neighbouring cities should not come out thousands of kilometres apart. Third, re-enter the same coordinates into the DigiToolkit calculator and confirm the figures match to within a kilometre or two. If all three checks pass, you can trust your result.

Understanding the Numbers Behind the Examples

Notice how the circuity ratio changes with terrain and infrastructure. Plains routes served by expressways, such as Delhi–Jaipur, have ratios close to 1.15, meaning the road adds only about 15% to the straight-line distance. Routes that cross rivers, ghats, or older road networks tend toward 1.25 or higher. Tracking this ratio for the corridors you use most often turns a raw haversine figure into a surprisingly accurate driving estimate, which is why logistics planners across India keep their own tables of typical ratios.

Example 7: Kolkata to Bhubaneswar

Kolkata (22.5726, 88.3639) to Bhubaneswar (20.2961, 85.8245) is a well-travelled eastern-India route. The haversine distance comes to about 370 km, while the NH-16 road distance is close to 440 km. This route is a useful reminder that even along the coast, where you might expect roads to run straight, the great-circle figure still sits comfortably below the driving distance.

Putting the Examples to Work

Taken together, these seven examples cover the full range of Indian journeys, from a 210 km hop between Ahmedabad and Surat to a 1,304 km haul between Delhi and Kolkata. The pattern never changes: convert, difference, apply the formula, multiply by 6,371. Once you have worked through three or four of them, you will be able to estimate any route in the country in under a minute, and you will instinctively know that the road figure will land 15 to 30 percent higher. That intuition — knowing roughly what answer to expect before you calculate — is the real payoff of studying worked examples, because it lets you catch mistakes the moment they appear.

Frequently Asked Questions

What is the haversine distance from Delhi to Mumbai?
The great-circle distance from Delhi to Mumbai is about 1,148 km using Earth’s mean radius of 6,371 km. The actual road distance on NH-48 is roughly 1,400 km because highways curve around terrain and towns.

Why are all the example distances shorter than road distances?
Haversine measures the shortest path across the Earth’s curved surface, while roads must follow available routes around rivers, hills, and settlements. This makes road distances consistently longer, typically by 15–30% in India.

Can I reuse these coordinates in the calculator?
Yes. All coordinates are given in decimal degrees, so you can copy any pair directly into the Haversine Distance Calculator and reproduce the result instantly.

What is a circuity ratio?
The circuity ratio is the road distance divided by the straight-line distance. A ratio of 1.2 means the road is 20% longer than the great-circle path, and it is a handy way to convert haversine distances into rough driving distances.