Convert mi to cm

A mile is 1,760 yards — a number that comes from a Roman thousand paces, adjusted by an Elizabethan statute to fit the furlong. It is exactly 1,609.344 metres.

Centimetres are the everyday metric length — body measurements, paper, furniture — and they are the one metric unit that has no direct customary counterpart, which is why so much converting happens through them.

The mile has been defined in metric terms since the international yard and pound agreement of 1959, and in this page's units that comes out at 160934.4 cm to one. The definition is exact by stipulation — it was not measured, and it cannot be refined by measuring it better. The decimal above is the whole of it, with nothing rounded away at the end.

Before that agreement the US and the British versions differed slightly, and old survey figures still carry the older definition. For anything outside land surveying the difference is far below the precision anybody is working to.

The reason anybody converts a mile into centimetres is almost never that they wanted centimetres. It is that a schema has one length column, that column was defined in centimetres by whoever wrote the first migration, and it now has to hold a component width, a room dimension and a route length in the same field. The conversion is a consequence of a decision made once and never revisited.

That framing changes what a good answer looks like. Nobody is going to read 160,934.4 and picture a mile, so legibility does not matter; correctness and reversibility do. The exact figure is more useful than a tidy one, the original unit is worth recording alongside it, and the question of how many decimals to print is replaced by the question of how the value is stored.

Follow the chain once and the reason is obvious. An inch is exactly 25.4 mm, a mile is 63,360 inches, so a mile is 1,609,344 mm — an integer, with no fraction anywhere in it. Divide by ten for centimetres and the integer becomes 160,934.4, which is exact as a decimal and no longer a whole number.

Every customary length behaves this way: a foot is 304.8 mm, a yard 914.4 mm, an inch 25.4 mm, and each is a whole number of tenths of a millimetre. So the millimetre is the natural base unit for holding imperial lengths exactly, and the centimetre is one decimal place worse for no benefit. If the unit is still yours to choose, this is the argument for choosing the millimetre.

A binary floating-point number cannot represent 0.4 exactly, in the same way a decimal cannot represent a third. The nearest double to 160,934.4 is a fraction below it, so the stored value is not the number that was written. For a single distance that is invisible — the discrepancy is under a hundred-millionth of a centimetre — and it stops being invisible when values are summed, compared for equality, or round-tripped through two different code paths.

The integer form has none of these problems. 1,609,344 is exactly representable, sums of it are exact, and equality means equality. This is why length is usually stored as an integer count of a small unit rather than as a decimal of a convenient one, and it is the same reasoning that puts money in integer cents rather than in floating-point currency.

A schema that normalises lengths usually holds areas too, and the factor above is the wrong one for them. A square mile is 160,934.4 squared square centimetres, which is about 2.59 × 10¹⁰ — roughly twenty-six billion. Applying the linear figure instead is out by a factor of 160,934, and the result is still a positive number of a plausible order of magnitude, which is exactly why it survives review.

Volumes take the cube and become unreadable. The defence is structural rather than arithmetic: keep areas in an area type and lengths in a length type, and put the unit in the value or its schema rather than in the column name where nothing enforces it. Most damage attributed to unit conversion is not a wrong factor but a right factor applied to a quantity of the wrong dimension.

The value 160,934.4 in a column tells you nothing about where it came from. It could be a measured distance, a nominal mile converted exactly, or a mile that was itself a rounding of something else. Once the original unit and figure are gone, no amount of care downstream can recover them, and the next person to touch the column has to guess.

The canonical warning is the Mars Climate Orbiter, lost in September 1999 because one team's software produced impulse figures in pound-force seconds while the navigation software receiving them expected newton-seconds. Nothing in either number said which it was. The fix in any system is the same: carry the unit with the value, record the conversion that produced it, and never let a number and its unit be separated by a column boundary.

A distance that will be converted more than once should be converted only at the boundary. Store the value in one unit at full precision, do every calculation in that unit, and convert on the way out to whatever a report or an interface needs. Converting on the way in, storing the result, and converting again later compounds a rounding at every step for no gain.

That also settles the question of how many digits to print. Inside the system, all of them, because the storage is exact. On the way out, as many as the original measurement supported — an odometer reading good to a tenth of a mile carries 16,093 cm of uncertainty, so the trailing digits of 160,934.4 describe the definition of the mile rather than the distance that was travelled.

If a human being is going to read the number, the centimetre is the wrong choice for a distance this size. A mile is 1.609 km, 1,609 m or 1,760 yards, and each of those gives a reader something to hold. A hundred and sixty thousand centimetres gives them a string of digits and an opportunity to lose a factor of ten while counting them.

Where the unit is fixed by a system, convert exactly and move on. Where it is a choice — a report, a chart axis, a label, a specification you are writing — pick the unit whose numbers land between about one and a thousand for the quantities involved. That is a rule of thumb rather than a standard, and it is the reason kilometres and centimetres both exist rather than one of them serving for everything.