MGRS vs UTM: How the Military Grid Reference System Builds on UTM
MGRS and UTM share the same math but read differently. Learn how MGRS compresses UTM coordinates into grid references like 4QFJ 12345 67890, and when each system is the right choice.
If you have used a military map, a search-and-rescue protocol, or certain hiking GPS units, you have seen references like 4QFJ 12345 67890 — clearly not latitude/longitude, and not quite UTM either. That is MGRS, the Military Grid Reference System. The key insight: MGRS is not a different coordinate system — it is a more compact way of writing UTM (plus UPS near the poles). The USGS describes MGRS as the military's own implementation of the UTM system, and notes that neither is more accurate than latitude/longitude — they are just different ways of writing a position.
The Same Foundation
Both systems start identically: project the Earth onto 60 UTM zones, each 6° of longitude wide, and measure positions in meters on the WGS84 ellipsoid. An MGRS reference and a UTM coordinate for the same spot contain the same underlying numbers. What differs is the encoding.
A full UTM coordinate looks like:
Zone 4, hemisphere N, E 612345, N 2367890
The same location in MGRS:
4QFJ 12345 67890
Shorter, unambiguous, and readable over a radio. Here is how the compression works.
Anatomy of an MGRS Reference
4Q — Grid Zone Designator (GZD). The UTM zone number (4) plus the latitude band letter (Q). Bands are 8° tall, lettered C through X (skipping I and O), starting at 80°S. Band X is stretched to 12° so it reaches 84°N. Letters C–M are south of the equator, N–X are north.
FJ — 100,000-meter Square ID. Each grid zone is subdivided into 100 km × 100 km squares, each identified by two letters. The first letter encodes the easting column, the second the northing row. This pair replaces the leading digits of the UTM easting and northing — that is where the compression comes from.
12345 67890 — Numerical Location. Digits within the 100 km square, split evenly: first half easting, second half northing. The number of digits sets the precision:
| Digits | Precision | Example |
|---|---|---|
| 2 + 2 | 1 km | 4QFJ 12 67 |
| 3 + 3 | 100 m | 4QFJ 123 678 |
| 4 + 4 | 10 m | 4QFJ 1234 6789 |
| 5 + 5 | 1 m | 4QFJ 12345 67890 |
One detail matters: MGRS digits are truncated, not rounded. A shorter reference names the south-west corner of a square that contains the point, not the nearest grid line. GeographicLib's documentation spells this out: 38SMB4488 means 444 km ≤ easting < 445 km and 3688 km ≤ northing < 3689 km.
Worked Example: The Same Point in Both Systems
Below are two real places converted with two independent libraries: pyproj (PROJ) plus the Python mgrs package, cross-checked against PyGeodesy. All UTM values and all MGRS strings matched exactly between the two.
Seoul City Hall (37.5665°N, 126.9780°E)
- UTM: zone 52N, E 321,424.29 m, N 4,159,640.64 m (EPSG:32652)
| Precision | MGRS |
|---|---|
| 1 m | 52S CG 21424 59640 |
| 10 m | 52S CG 2142 5964 |
| 100 m | 52S CG 214 596 |
| 1 km | 52S CG 21 59 |
Read it piece by piece: 52 is the UTM zone, S the band from 32°N to 40°N, CG the 100 km square, and 21424 59640 are the last five digits of the UTM easting (321424) and northing (4159640). The digits the square ID "swallowed" are 3 for the easting and 41 for the northing.
Sydney Opera House (33.8568°S, 151.2153°E)
- UTM: zone 56S, E 334,900.57 m, N 6,252,288.75 m (EPSG:32756)
| Precision | MGRS |
|---|---|
| 1 m | 56H LH 34900 52288 |
| 10 m | 56H LH 3490 5228 |
| 100 m | 56H LH 349 522 |
| 1 km | 56H LH 34 52 |
Note that the southern-hemisphere UTM northing includes the 10,000,000 m false northing, so it is a positive number. In MGRS the band letter H already says "south", so no hemisphere flag is needed.
Truncation shows up here too. Sydney's northing digits are 52288.75, so the 1 m form is 52288 (rounding would give 52289), and the 100 m form is 522 (rounding would give 523). Every shorter form is simply the longer one with digits cut off the end.
Polar Regions and Zone Exceptions
UPS near the poles. UTM covers 80°S to 84°N. Beyond that, MGRS switches to the Universal Polar Stereographic (UPS) system, and the GZD becomes a single letter: A/B for the south polar area, Y/Z for the north. The South Pole itself encodes as B AN 00000 00000 in both libraries.
Norway. In band V (56°N–64°N), zone 32 is widened west to 3°E, so zone 31V is narrower. Bergen (60.3913°N, 5.3221°E) would fall in zone 31 by the plain 6° rule, but its correct reference is 32V KN 97353 00648.
Svalbard. In band X (72°N–84°N), zones 32X, 34X and 36X do not exist. Instead 31X spans 0°–9°E, 33X 9°–21°E, 35X 21°–33°E and 37X 33°–42°E. Ny-Ålesund (78.9236°N, 11.9300°E) would be zone 32 by the plain rule, yet it is 33X VH 34186 63177. A converter that ignores these exceptions produces a valid-looking but wrong reference.
Common Mistakes
- Reading the band letter as a hemisphere. NGA explicitly warns about this: UTM is written two ways, one with MGRS band letters and one with N/S for hemisphere. Band
S(32°N–40°N, Seoul) is in the northern hemisphere. - Rounding instead of truncating when shortening a reference, which can move you into the neighbouring square.
- Dropping the GZD or square ID.
21424 59640alone repeats every 100 km; it is only meaningful with52S CGin front, or when everyone already knows which square you are working in. - Mixing easting and northing. In MGRS, easting always comes first ("read right, then up").
- Unequal digit counts.
52SCG214596splits as 214/596; an odd number of digits is invalid. - Wrong datum. NGA notes that MGRS uses an alternate "old" lettering scheme for squares referenced to older datums, so a map's datum note matters.
Who Uses Which
- Military: MGRS is the U.S. military's grid reference, and NGA (the National Geospatial-Intelligence Agency) publishes the reference documentation for MGRS, UTM and UPS.
- Emergency management and SAR in the U.S.: FEMA Directive 092-5 makes the U.S. National Grid (USNG) FEMA's standard geographic reference for land-based operations, including search and rescue. FEMA and NGA both describe USNG as functionally equivalent to MGRS.
- Surveying, GIS, and engineering: numeric UTM, or a national projected system. Most geospatial files and databases store UTM or latitude/longitude, not MGRS strings.
- Marine navigation: USGS notes that ocean-going sailors almost always use latitude/longitude because nautical charts are built around it.
I work with UTM, not MGRS, in drone ground-control software. When I analyzed drone crash locations recorded by different tools, part of the job was converting Korean EPSG:5186 (KGD2002 / Central Belt 2010) coordinates into UTM so everything shared one metric grid. For Seoul City Hall, the EPSG:5186 position (easting ≈ 198,056 m, northing ≈ 551,885 m) converts back to exactly the UTM 52N values above. You can try the same conversion with the EPSG converter.
When UTM Is the Better Fit
MGRS optimizes for humans reading references aloud. Plain UTM optimizes for computation:
- GIS and surveying software works natively with numeric easting/northing — the 100 km letter pairs just add a parsing step.
- Continuous math across squares: MGRS references reset at each 100 km square boundary; UTM numbers flow continuously across the zone.
- Data interchange: EPSG codes such as 32652 (UTM 52N) describe UTM directly, while MGRS is a reference notation layered on top of UTM/UPS rather than a CRS you store data in.
Rule of thumb: speak MGRS, compute UTM, store latitude/longitude.
Converting Between Them
MGRS → UTM is mostly a table lookup (expanding the square letters back into meters); UTM → latitude/longitude requires the projection math. In practice you let software do both. Our UTM converter handles the latitude/longitude ↔ UTM leg on WGS84, including the band letters and the Norway/Svalbard zone exceptions that MGRS builds on. The EPSG converter moves coordinates between national grids and UTM codes, and the coordinate converter covers the degree-based formats.
FAQ
Is MGRS more accurate than UTM? No. Both encode the same projected coordinates. A 10-digit MGRS reference resolves a 1 m square; the accuracy of the position itself depends on how it was measured.
Is a 6-digit MGRS reference enough? Six digits (3 + 3) name a 100 m square. That is often enough to point a team at an area, but not to mark a specific doorway; use 8 digits (10 m) or 10 digits (1 m) when the location must be exact.
What is the difference between MGRS and USNG? For WGS84/NAD83 data they are functionally the same format. NGA notes the main difference is how the datum is specified: MGRS uses an alternate letter scheme for older datums.
Sources
- NGA Office of Geomatics, "Coordinate Systems" (MGRS, UPS, USNG): https://earth-info.nga.mil/index.php?dir=coordsys&action=coordsys
- USGS FAQ, "What does the term UTM mean? Is UTM better or more accurate than latitude/longitude?": https://www.usgs.gov/faqs/what-does-term-utm-mean-utm-better-or-more-accurate-latitudelongitude
- FEMA Directive 092-5, "Use of the United States National Grid (USNG)" (hosted by the U.S. Coast Guard NSARC): https://www.dco.uscg.mil/Portals/9/CG-5R/nsarc/USNGDirective(2015_10_15_1802)_(3).pdf
- GeographicLib, GeoConvert manual (truncation, Norway/Svalbard exceptions): https://geographiclib.sourceforge.io/C++/doc/GeoConvert.1.html
- GeographicLib, MGRS and UTMUPS class reference: https://geographiclib.sourceforge.io/C++/doc/classGeographicLib_1_1MGRS.html
Related Posts
What Is the UTM Coordinate System? Zones, Easting, and Northing Explained
Understand the UTM (Universal Transverse Mercator) coordinate system: how its 60 zones work, what easting and northing mean, and when to use UTM instead of latitude/longitude.
Geocoding vs Reverse Geocoding: How Addresses Become Coordinates (and Back)
What geocoding and reverse geocoding actually do, how match quality levels work (rooftop vs interpolated), why results differ between providers, and what accuracy you can expect.
How to Calculate the Distance Between Two Coordinates (Haversine vs Vincenty, With Worked Examples)
Calculate the distance between two GPS coordinates with the haversine formula, see how far it drifts from the exact WGS84 ellipsoid answer, and avoid the most common mistakes. Includes a Seoul–Busan worked example.