MGRS to lat/lon

The Military Grid Reference System labels every place on Earth with a short alphanumeric string built on UTM zones, latitude bands, one-hundred-kilometre square letters, and a truncated easting-northing pair. Map readers, field apps, and after-action reports still exchange those strings daily, yet most web tools either refuse incomplete precision or silently return a cell centre that was never what the reference defined. This capability parses a compact or spaced MGRS string, validates the grid zone designator and the two one-hundred-kilometre letters, scales any numerical digits to metres, and returns the WGS84 latitude and longitude of the square's south-west corner together with the underlying UTM easting, northing, zone, band, and precision.

How an MGRS string becomes a south-west lat/lon corner

An MGRS reference begins with the grid zone designator: an integer UTM zone from one to sixty plus a single latitude band letter from C through X, skipping I and O because those glyphs look like digits.

Next come two letters that name a one-hundred-kilometre square inside that zone—the column letter from the twenty-four letter A–Z set without I and O, and the row letter from the twenty letter A–V set without I and O—using the AA lettering scheme that rotates column origins every three zones and shifts row origins on even zones.

An optional even-length digit string follows: half the digits are easting and half are northing, truncated toward the south-west so zero digits mean a full one-hundred-kilometre square, two digits mean ten kilometres, and ten digits mean one metre.

The decoder expands those letters into UTM easting and northing offsets, adds the scaled digit metres without a half-cell centre shift, applies the southern false northing when the band is C through M, and converts the resulting UTM point to geographic latitude and longitude on the WGS84 ellipsoid with the classical Redfearn series.

What you send and what you get back

Send one required string under the field mgrs. Spaces and mixed case are accepted and stripped: both eighteen S U J two three four eight three zero six four seven nine and the compact form resolve to the same canonical reference.

Classic checks include a one-metre reference near Washington decoding to about thirty-eight point eight nine north and seventy-seven point zero three west, a coarse Vienna cell thirty-three U X P zero four landing near forty-eight point two north and sixteen point three east, and a Hawaiian four Q F J sample in the twenty-one north one hundred fifty-seven west area. Use the free browser form when you are reading a paper map or a radio log and need degrees immediately.

Where MGRS to lat/lon conversion shows up in real work

Defence, emergency management, and search-and-rescue teams still coordinate on MGRS because a short string is easier to voice and write than full decimal degrees, yet every modern GIS layer, weather model, and phone map expects WGS84 latitude and longitude. Logistics planners importing legacy range cards and gridded patrol traces need a trusted offline decoder that refuses illegal squares instead of snapping to a wrong cell.

Software vendors shipping dual military and civilian map modes must unit-test that a fixed MGRS landmark always expands to the same south-west corner across releases without bundling a full NGA toolkit in continuous integration. Educators teaching UTM lettering schemes want students to see zone, band, and one-hundred-kilometre letters produce real coordinates with an honest error when the square cannot exist in that band.

Privacy and analytics pipelines that store only coarse MGRS cells can convert batches into bounding south-west points for heat maps while keeping the conversion pure and free of network side effects. If you later need the inverse encode of latitude and longitude into MGRS, UTM zone helpers alone, or great-circle destination points, treat those as separate search intents and landings rather than overloading this MGRS south-west corner decoder page.