Distance comparisons become unreliable when one itinerary uses miles and another uses kilometers without a clear label. The distance tool displays both for the same great-circle result, using the international mile relationship of 1 mile = 1.609344 kilometers. This guide explains the conversion, rounding and comparison workflow. Changing the unit never changes the endpoint model: a kilometer output and its mile equivalent are both geographic distance estimates, not route measurements.
Reference table
| Item or scenario | Value or choice | What to remember |
|---|---|---|
| 100 miles | 160.9344 km | Multiply by 1.609344 |
| 100 km | About 62.14 miles | Divide by 1.609344 |
| Unit label | km or miles | Mandatory when sharing |
| Model label | Route or great-circle | Must match across comparisons |
Use one common unit for comparison
Choose kilometers or miles as your working unit and convert every distance into that unit before ranking routes or destinations. To convert miles to kilometers, multiply by 1.609344. To convert kilometers to miles, divide by that same number. Avoid using a loose factor for one entry and a precise factor for another if the comparison is close. A small conversion inconsistency can change the apparent ordering of similar numbers. The tool shows both outputs so you can check the relationship without doing a second separate calculation.
Keep model and unit as separate labels
A statement such as 300 km road distance is different from 300 km great-circle distance. Converting both to miles does not make them comparable models. When collecting figures, record whether each comes from a route planner, rail timetable, coordinate calculation or another source. For a geographic separation comparison, use the same coordinate method across entries. For a practical transport comparison, use appropriate route information and state that the route options may differ. The label should identify both the unit and what was measured.
For the next input check, use Straight-Line Distance Calculator. Its result should retain the assumptions described here.
Round only after calculation
Use the full calculation internally and round the displayed result at the end. Repeatedly rounding intermediate conversions can accumulate small differences, particularly if values are later added. Two decimal places in the interface are a readable display choice, not a claim that the endpoint coordinates or spherical model are accurate to that precision. For an ordinary planning note, a rounded whole kilometer may communicate the scale more honestly than a long decimal string. Keep enough precision only for the decision you are actually making.
Never compare distance alone when time matters
A shorter distance is not necessarily a shorter journey. Transfers, service frequency, terrain and terminal access can overwhelm the geographic difference. Put route time and departure convenience beside distance when planning a trip. The distance tool should inform the scale of the map; the itinerary pace tool should use actual travel-time estimates. This separation prevents a distance conversion from becoming an unexamined scheduling rule. If two options differ mainly in time reliability, a unit conversion does not resolve that uncertainty and should not be presented as if it does.
A related planning question is covered in Checking the geographic spread of a multi-stop itinerary.
Adding several legs without mixing labels
For a three-leg table, convert each leg to the working unit before summing, and preserve the unrounded values until the total is calculated. If one leg is 50 miles and two are 80 km each, the converted first leg is 80.4672 km and the sum is 240.4672 km. A final whole-kilometer display could reasonably read about 240 km if that precision suits the purpose. However, the sum is meaningful only if the legs share an appropriate measurement model. Combining one road segment with two great-circle arcs produces a mixed quantity that should not be called the route total. Label it as a mixed planning note or replace the figures with consistent measurements. This is a useful check for multi-stop travel spreadsheets, where copied numbers often arrive with units hidden in headings or surrounding text. Each row should retain its own unit until normalization, and the final total should state the model that makes the addition meaningful. Unit consistency solves one problem; source consistency solves the other.
Worked example
Worked example: One note gives 100 miles and another gives 150 km. Convert the first to 160.9344 km, so it is geographically longer than 150 km under the same measurement model. Now suppose the first value is road distance and the second is straight-line distance. The ranking no longer answers which journey has the shorter route; the inputs describe different things. To repair the comparison, obtain road distances for both or compute great-circle distances for both verified endpoint pairs. Only then round for the final table, with a unit and model in every row.
Before you finish
- Choose one working unit for the comparison table.
- Use the same conversion relationship for every entry.
- Keep route and great-circle figures separate.
- Round after the calculation rather than at each step.
- Use route time when deciding the daily schedule.
Your next step
The useful habit is to label the quantity before interpreting it. A distance with a unit, endpoint pair and model can be reviewed. A bare number cannot. The coordinate-input guide explains how to make the endpoint part equally explicit before using the distance calculator for a new comparison.
Continue with What straight-line travel distance can and cannot tell you. When your plan needs the next calculation, open Itinerary Pace Calculator and carry over only the inputs appropriate to that tool.