Cartographic Projection
every map is wrong, and by exactly how much
Figure

Molodensky against the exact route, NAD27

Drawn here at the parameters it defaults to, with every essay that calls it.
Molodensky against the exact route, NAD27. The distance on the ground between where each shortcut puts the transformed point and where the exact Cartesian route puts it, at 0 metres of ellipsoidal height, on a logarithmic scale. The full formulae stay within 0.8 centimetres across every latitude drawn; the abridged form, which replaces two ellipsoid-difference coefficients with one combined term, is worst at 40 centimetres — a factor of 48. The abridged curve dips near 45°, where the combined coefficient happens to equal the pair it replaces.

The distance on the ground between where each shortcut puts the transformed point and where the exact Cartesian route puts it, at 0 metres of ellipsoidal height, on a logarithmic scale. The full formulae stay within 0.8 centimetres across every latitude drawn; the abridged form, which replaces two ellipsoid-difference coefficients with one combined term, is worst at 40 centimetres — a factor of 48. The abridged curve dips near 45°, where the combined coefficient happens to equal the pair it replaces.

It is drawn by datum-figure with show: "shortcut-error" — one member of a family of 11 figures that share a generator, so the drawing above is what that generator returns when it is asked for this one and given nothing else.

5 essays call it. Every call below passes it something, because a placement that passes nothing draws whichever member of the family the generator happens to default to rather than the one its essay argues about.

Where it is called

Changing this changes every one of these figures.

OSGB36 to WGS84, one parameter at a time. Each bar is how far the mark at 2.0° west, 54.5° north moves under one of the seven parameters with the other six set to zero. seven of the seven are not zero for OSGB36. The units hide the comparison: one arcsecond of rotation moves this point 30.8 metres and one part per million of scale moves it 6.36 metres, so OSGB36's scale term contributes 130 metres — more than one of its three translations. What the numbers refer to

The seven parameters, and what each one does

A datum transformation is published as three metres, three arcseconds and one part per million, in three different units — which hides the fact that all seven are the same size of thing. Converted to ground displacement, the scale term beats two of the translations.

 Molodensky against the exact route, NAD27. The distance on the ground between where each shortcut puts the transformed point and where the exact Cartesian route puts it, at 0 metres of ellipsoidal height, on a logarithmic scale. The full formulae stay within 0.8 centimetres across every latitude drawn; the abridged form, which replaces two ellipsoid-difference coefficients with one combined term, is worst at 40 centimetres — a factor of 48. The abridged curve dips near 45°, where the combined coefficient happens to equal the pair it replaces. What the numbers refer to

Molodensky's shortcut

The exact way to shift a datum needs an iteration nobody wanted to run on a 1950s machine, so a direct formula was derived instead. It lands within centimetres — and the abridged version everybody quotes is a different formula, worse by a factor of fifty.

 What grid spacing a tolerance buys. The worst bilinear interpolation error across OSGB36's ground, against the spacing of the table it is interpolated from, both axes logarithmic. The smooth shift falls by exactly four for every halving, which is what second-order interpolation does. Adding a 30 centimetre ripple 2 degrees across — three parts in a thousand of the 99 metre shift it rides on — moves the spacing needed for 20 millimetres from 1° to 0.125°, which is 64 times as many nodes. What the numbers refer to

When a formula is not enough

National mapping agencies distribute datum shifts as tables of numbers on a grid rather than as parameters. What decides the spacing that table needs is not the size of the shift — a hundred-metre shift tabulates coarsely, and a thirty-centimetre ripple riding on it does not.

 The same coordinate on four datums. One pair of numbers — 2.0° west, 54.5° north — read as a coordinate on OSGB36, ED50, NAD27 and on WGS84, and plotted where each reading puts the mark on the ground. The spread runs to 195 metres, and the height changes by 51, 44, 47 metres, which is the component nobody quotes. What the numbers refer to

The third coordinate moves too

A datum shift is quoted as a horizontal displacement because horizontal is what people look at. The transformation acts on a three-dimensional point, and its vertical component is between a quarter and a half of the horizontal one — 51 metres, for a British coordinate.

 OSGB36 then DHDN, done four ways. How far each route lands from the truth — applying the two transformations one after the other — at 54.5° north, 2.0° west. Composing them into one affine map is exact, because two affine maps compose into an affine map and nothing is dropped. Describing that composition with seven parameters again leaves 0.19 millimetres, because two linearised rotations compose into something with a symmetric part that seven numbers cannot hold. Adding the fourteen published numbers in pairs — which is what a chain is usually done with — leaves 7.4 millimetres. Logarithmic from a micrometre. What the numbers refer to

A chain of transformations does not close

Two datum transformations applied one after the other are not the sum of their fourteen published numbers. The gap is seven millimetres in Britain, doing the two in the other order moves the answer twenty, and the rotation matrix everybody prints is not a rotation.

The whole library