Coordinates, distance and bearing, with the reading it used printed BEARING
Degrees and decimal minutes read as degrees, minutes and seconds puts you four hundred metres out and looks entirely reasonable. So it says which one it took.
A position
Decimal degrees, degrees and minutes, degrees minutes and seconds, or an MGRS reference. Latitude first. Whichever reading it used is printed, because the wrong one is hundreds of metres out and looks perfectly reasonable.
Every other way of writing it
Distance and bearing
Where a bearing and a range put you
A whole column
One position per line, in any of the forms above, mixed if you like.
How it works
BEARING reads coordinates as decimal degrees, degrees and decimal minutes, degrees minutes and seconds, or MGRS, converts between them, and works out the distance and bearing between two points. It always says which format it took your input to be, because reading decimal minutes as seconds puts you hundreds of metres out while looking perfectly reasonable. The arithmetic runs in this tab.
Questions people ask about BEARING
What forms of coordinate does it read?
Decimal degrees (51.4778, -0.0015), degrees and decimal minutes (51°28.668′N 000°00.090′W), degrees minutes and seconds (51°28′40.1″N 0°00′05.3″W), and MGRS references at any precision from one to five digits. Hemisphere letters may come before or after, and a minus sign works instead. Latitude always comes first. Whichever form it settled on is printed with the answer, and anything it cannot read unambiguously it refuses rather than guesses.
Why are the starting and finishing bearings different?
Because the shortest path between two points on a globe is a great circle, and a great circle crosses each meridian at a different angle. Setting off from London to New York on the initial bearing and holding it will not get you there. Over short distances the two bearings are almost identical; over long ones they differ by tens of degrees, and both are given so that neither is mistaken for the other.
Which is the right distance, Vincenty or haversine?
Vincenty, essentially always: it models the earth as the flattened ellipsoid it is and is accurate to well under a millimetre. Haversine is shown beside it because it is what most tools give you and because seeing the gap is instructive: a few centimetres across a town, tens of metres across a continent. The one case where Vincenty is not available is two points almost exactly opposite each other on the earth, where the iteration does not converge; the page says so plainly rather than quietly falling back to the spherical figure.
Why no Ordnance Survey grid reference?
Because doing it correctly requires OSTN15, the grid of corrections the Ordnance Survey publishes, and the seven-parameter Helmert transformation that free converters actually use is roughly five metres out. Almost none of them tell you that. Five metres is irrelevant for a walk in the hills and quite relevant for a scene, a boundary or a search area, so the honest options were to ship OSTN15 or not to offer it, and this does not offer it.
Is MGRS exact here?
Yes. MGRS is a lettered way of writing a UTM coordinate, and UTM is a projection of WGS84 rather than a different datum, so there is no approximation involved, only the truncation you choose. A five-digit reference is to the metre, four to ten metres, three to a hundred, and the page tells you which. The zone exceptions and the twelve-degree X band are implemented, and a reference converted out and back returns the same square.
Does it work without a network?
Yes. It is arithmetic, and once the page has loaded it needs nothing. That matters for the people most likely to want it, who are frequently somewhere with no signal.
Doing this often? OBSCURA Pro saves the result from here, along with the result of every other tool outside the Workspace, and includes the paid applications. Everything is US$5 a month or US$48 a year.