November 4, 2025 · 7 min read · MapBench editorial
Understanding GPS Coordinates: Formats, Datums and Precision
Every point on Earth can be described with two angles: latitude (north–south of the Equator) and longitude (east–west of the Prime Meridian). That sounds simple, but coordinates show up in several notations, and mixing them up is the most common source of 'my marker is in the ocean' bugs.
Decimal degrees vs. DMS
Decimal degrees (DD) write the angle as a single number: 40.7128, −74.0060. Degrees-minutes-seconds (DMS) splits each degree into 60 minutes and each minute into 60 seconds: 40°42'46"N, 74°00'22"W. Both describe exactly the same point. Software almost always wants DD; charts, legal descriptions and older GPS units often speak DMS.
- Negative latitude = south of the Equator; negative longitude = west of Greenwich.
- DMS hemisphere letters (N/S/E/W) carry the sign — never use both a minus and a letter.
- Beware of 'degrees and decimal minutes' (40°42.768'), a third format common in aviation and marine GPS.
How precise is precise?
One degree of latitude is about 111 km everywhere. That gives a useful rule of thumb for decimal places:
- 3 decimals ≈ 111 m — fine for a neighbourhood
- 4 decimals ≈ 11 m — a building
- 5 decimals ≈ 1.1 m — survey-grade for everyday purposes
- 6 decimals ≈ 0.11 m — beyond what consumer GPS can measure
Datums: WGS84 is not the only one
A datum defines the exact shape model of the Earth the coordinates refer to. GPS speaks WGS84, and so do web maps, GeoJSON, and this site. Older North American data may be NAD27 or NAD83 — the same physical point can differ by tens of metres between datums. If coordinates from an old survey disagree with your GPS by a consistent offset, a datum mismatch is the usual suspect.
Practical checklist
- Always store coordinates in decimal degrees with 6 decimals in databases.
- Validate ranges: latitude −90…90, longitude −180…180.
- Watch for swapped lat/lng — GeoJSON uses [lng, lat] order, most APIs use (lat, lng).
- When copying from Google Maps, the right-click coordinates are already decimal degrees in lat,lng order.
The toolkit behind this post, in depth
Latitude & Longitude Finder
This is the platform's universal coordinate picker: click or drag on the map and the panel instantly shows the point in decimal degrees, degrees-minutes-seconds, UTM zone/easting/northing, MGRS grid reference and Open Location (Plus) Code — each with its own copy button. Zoom controls the precision you can read, and five decimals already lands within about a metre. It is the page to keep bookmarked whenever another system asks 'what are the coordinates of this spot?'
Everything converts locally in your browser using standard WGS84 geodetic formulas, including the official Norway/Svalbard UTM zone exceptions, so the numbers you copy are interoperable with GPS devices, GIS software and mapping APIs. The current point lives in the URL, making any lookup shareable and reproducible — useful for property notes, field reports and support tickets. Pair it with the reverse geocoder when you also need the address, or feed the copied pair into distance, radius and elevation tools for deeper analysis.
Coordinate Converter
Paste a coordinate in any supported notation — decimal degrees, DMS, UTM easting/northing with zone, MGRS grid reference or Plus Code — and this converter recognises the format and shows all the others simultaneously, updating on every keystroke. It is the Swiss-army page for anyone translating between worlds: GPS hobbyists (DMS), survey-adjacent work (UTM), military and search-and-rescue literature (MGRS), and shareable short codes (Plus Codes). The recognised source format is always labelled, so you know what the parser understood.
All math is local and standards-based: WGS84 throughout, official UTM zone exceptions included, MGRS precision following your digit count (10 digits ≈ 1 m). Clicking the map feeds coordinates back into the input, closing the loop between visual and textual workflows. Only the map preview needs a network connection; the conversions themselves work offline. For single-direction jobs the dedicated DMS and UTM pages are leaner, and for naming the point the reverse geocoder adds the address layer.
GPS Coordinate Lookup
Handheld GPS units, cameras, drones and legacy datasets all emit coordinates in slightly different notations — decimal degrees, degrees with decimal minutes, full DMS with hemisphere letters, odd separators. Paste nearly any of them here and the tool parses it, validates it against WGS84 ranges, pins the exact spot on the map and presents every standard format for copying onward. A clear error message explains unparseable input instead of silently misplacing your point.
The map preview is the trust layer: before you drive to a geocache, file a boundary note or trust an EXIF location, you see where the numbers actually land. Conversions — including UTM, MGRS and Plus Codes — run locally with full geodetic series, so results match professional software at the precision you entered. Nothing is uploaded; the lookup history never leaves your browser. When the point also needs a name, the coordinates-to-address tool reverse-geocodes it, and the coordinate converter handles bulkier mixed-format jobs.
DMS to Decimal Converter
Degrees-minutes-seconds is the notation of paper charts, old surveys and many handheld GPS screens; decimal degrees is what every web map, API and spreadsheet wants. Paste values like 40°26'46"N 79°58'36"W — hemisphere letters, minus signs or mixed separators all accepted — and get clean signed decimal pairs ready to copy. The parser validates ranges (latitude ≤ 90, longitude ≤ 180) and explains failures instead of guessing.
The arithmetic is the classic sexagesimal expansion — degrees plus minutes over 60 plus seconds over 3600 — with south and west becoming negative, and the page shows the mapping explicitly so students learn rather than just copy. Precision is preserved to the sub-metre level your input carries. When the source is already decimal and the destination must be chart notation, the decimal-to-DMS tool runs the conversion in reverse; for UTM, MGRS or Plus Code targets, the all-in-one converter covers the rest of the family.
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.
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.
- 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.
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.
Step-by-step masterclass
- 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.
- 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.
- 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.
- Match precision to source — Consumer GPS earns ~5 decimals; quoting more implies a survey you didn't run. Rounding deliberately is honesty.
- 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.
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.
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.
Two more questions, answered
Is MGRS usable at the poles?
Polar work switches to UPS; this tool covers the UTM domain where virtually all field grids live.
Why do some APIs want [lng, lat]?
GeoJSON follows the axis order of the OGC standard; remembering which world you're in prevents the ocean bug.