MGRS Converter

Military Grid Reference System, both directions

MGRS encodes a UTM position as a short, unambiguous string — zone, band letters, grid square and numeric easting/northing — where the digit count sets precision: 4 digits ≈ 1 km, 6 ≈ 100 m, 10 ≈ 1 m. Paste a reference like 33UUP 05300 21500 and the tool decodes it to decimal latitude/longitude and pins it on the map; paste coordinates and it encodes MGRS at your chosen precision. Spaces are optional, case insensitive, validation strict.

The encoding implements the official column/row lettering schemes and latitude bands, so results interoperate with military, SAR and orienteering materials. The map preview is the safety net: a single mistyped letter moves you 100 km, and seeing the pin land wrong is how operators catch it. Because MGRS is notation on top of the UTM grid, the UTM converter sits one click away for the numeric view, and the coordinate converter bundles everything when you are unsure which system a source string uses.

Worked examples

• 40.7128, −74.006 (Lower Manhattan) — is 40° 42' 46.08" N, 74° 0' 21.60" W in chart notation and 18N 583959 4507351 on the UTM grid — three dialects, one physical corner of City Hall Park.
• MGRS at 10 digits — reads 18?WK8395907350 for the same point: precision follows your digit count, 10 digits ≈ 1 m.
• One decimal place — is ≈ 11 km of latitude; five decimals ≈ 1.1 m. Consumer GPS earns five; quoting seven implies a survey you didn't run.

The many languages of a single point

One physical spot on Earth can be written a dozen ways: decimal degrees for software, degrees-minutes-seconds for charts and handhelds, UTM eastings and northings for field work, MGRS lettered squares for military prose, Plus Codes for places without addresses. None is more 'true' — they are notations over the same WGS84 datum, the reference frame GPS itself speaks. Conversion between them is exact math, which is why it can run entirely in your browser with no service and no error creeping in.

The traps are human, not mathematical. Swapping latitude and longitude is the classic — GeoJSON stores [lng, lat] while most APIs expect (lat, lng), and an offshore point is usually that typo. Hemisphere letters and minus signs must never coexist. And precision has a physical meaning: each added decimal degree is roughly a tenfold shrink, so five decimals is about a metre, six is beyond what consumer GPS can claim. Choosing rounding deliberately is choosing honesty.

Datums are the deep end: coordinates are angles against a model of Earth's shape, and older local datums (NAD27 and friends) shift the same physical point by tens of metres relative to WGS84. A consistent, unexplained offset between an old survey and your GPS is usually that story. For everyday web mapping the datum is WGS84 end to end, and keeping everything in it — as these tools do — makes round trips exact.

Tips & common mistakes

Adopt one storage format — decimal degrees, WGS84, five or six decimals — for every dataset you own, and convert at the edges for display. Mixed notations in one column are the root of nearly every coordinate bug.

Sanity-check every pasted pair by eye on a map before using it: latitude/longitude swaps land you in the ocean so reliably that 'the Null Island bug' has a name. A two-second visual check costs nothing and catches most transcription errors.

Match precision to source: consumer GPS earns about five decimals; quoting six or seven implies a survey you didn't do. Rounding deliberately is honesty, not loss.

Coordinate hygiene for people who reuse data

Coordinates are the one geographic asset that can be perfectly lossless — if you keep discipline. One datum (WGS84), one notation in storage (decimal degrees), one precision policy (five or six decimals), and conversions only at the display edge. Every deviation from that recipe taxes you later: mixed DMS strings in a column, NAD27 relics in an old shapefile, seven-decimal theatre in a CSV. The converters exist to absorb that variety at the border so your interior stays clean.

The second discipline is visual verification. A coordinate pair is two numbers; a pin on a map is a fact. Swapped axes, wrong hemispheres, degree/minute confusion — every classic error is instantly visible as a pin in the wrong ocean or the wrong hemisphere, and instantly invisible in a table. Professionals therefore make the map check a ritual: paste, look, then trust. At five decimals you are resolving metres; at that scale the eye, not the arithmetic, is the quality gate.

How professionals use this

• Store decimal degrees, WGS84, signed; convert to DMS/UTM/MGRS only for the reader who needs them.
• Validate ranges on ingest (|lat| ≤ 90, |lng| ≤ 180) and reject, don't clip, out-of-range rows.
• Make the map-pin sanity check mandatory for any coordinate you didn't generate yourself.
• When receiving UTM or MGRS strings, record the original alongside the conversion — provenance prevents arguments.

Step-by-step masterclass

1. 1. Standardise storage first — Decimal degrees, WGS84, five or six decimals in every column you own; convert at the display edge and the interior stays clean forever.
2. 2. Validate on ingest — Reject out-of-range values (|lat| > 90) instead of clipping; a rejected row is a fixable row, a clipped one is silent corruption.
3. 3. Make the pin check a ritual — Paste, look at the map, then trust — swapped axes and wrong hemispheres are instantly visible on a globe and invisible in a table.
4. 4. Match precision to source — Consumer GPS earns ~5 decimals; quoting more implies a survey you didn't run. Rounding deliberately is honesty.
5. 5. Preserve provenance — When converting UTM/MGRS strings, keep the original beside the decimal pair; provenance prevents every later argument about what was meant.

Notation culture splits by profession more than by country — mariners and aviators favour DMS and nautical frames, soldiers MGRS, developers decimals, hikers UTM — which is why a converter that shows all dialects simultaneously is more useful than any single 'correct' format.

Related questions people ask

Quick glossary

Datum

The reference shape model (WGS84 for GPS) that coordinates are angles against.

DMS

Degrees-minutes-seconds notation; 1° = 60′ = 3600″.

UTM

Metre-based zone/easting/northing grid on the WGS84 ellipsoid.

Plus Code

Open Location Code: keyless short codes for any spot, by open math.

Null Island

0,0 — where swapped/zeroed coordinates wash up; the classic bug's nickname.

Hemisphere letter

The N/S/E/W suffix carrying sign in DMS and MGRS notations.

Coordinates in the wild: where notation meets consequence

It is worth closing with two stories that explain why all this notation discipline matters. In the first, a search-and-rescue volunteer copies a grid reference from a radio call into a decimal-only field, drops a digit pair, and the rescue tasking points a valley away — the error invisible in the table, instantly obvious on a map. In the second, a research team merges three decades of ecological plots and discovers one legacy file was NAD27: every point shifted by the same quiet thirty metres, enough to move a forest edge. Both failures were preventable with the same two habits this toolset makes default — convert at the edge, verify with the pin — and neither required expertise, only ritual. Coordinates reward exactly that attitude: they are the one geographic asset that can be perfectly lossless, provided the humans touching them keep their agreements about datum, notation and precision.

• Radio/voice workflows: read MGRS or DMS back in grouped digits; transcription errors cluster at the group boundary.
• Merged historical datasets: assume a datum split until proven otherwise; plot both frames and look for a rigid offset.
• Public forms: accept every notation, store one; the converter's 'recognised as' label is your audit trail.

Honest limits & when to escalate

Coordinates are lossless in principle and lossy in practice, and every loss is human: swapped axes, wrong hemispheres, datum relics, precision theatre. The converters eliminate the notation problem completely — DMS, UTM, MGRS and Plus Codes are exact translations on WGS84 — but they cannot eliminate the provenance problem: a number without its datum and its source is a rumour. Old NAD27-era documents, hand-typed sheets and seven-decimal CSVs each carry their own failure signature, and the honest tool answers with validation errors and visible pins rather than silent corrections.

The practical boundary is therefore organisational, not mathematical: teams that standardise storage (decimal, WGS84, sane precision) and ritualise the map check enjoy a lossless system; teams that don't accumulate expensive folklore. For work beyond consumer frames — control points, machine guidance, legal description — the escalation is geodetic: licensed surveyors, published transformations and national datums. Everything between a pasted waypoint and that door is exactly where this toolset lives.

• Datum-critical legacy data → published grid transformations (NTv2/HTDP).
• Control points and machine guidance → licensed geodetic survey.
• Aviation/marine charts → the chart's own datum and notation, verbatim.
• Massive pipelines → scripted validation with rejection, not clipping.

Data & methodology note

All conversions (DMS, UTM with Norway/Svalbard exceptions, MGRS, Plus Codes) run locally on WGS84 with standard geodetic series; round-trips are exact at display precision.

Category context: Coordinates — Find, convert and validate GPS coordinates in every common format. This page is one of the coordinates tools on MapForge; the related-tools links below and the header's Tools menu connect every sibling instrument.