geoprimsField-grade geospatial math

Read any coordinate

Reads a coordinate in almost any notation (decimal, , DDM, packed aviation, labeled, MGRS, UTM, UPS, or a grid code) and reports what it assumed.

Go the other way: Format a coordinate →

40.4461111°

That is 40.4461111°, -79.9822222° (DMS).

Longitude
Notation
DMS
Provenance
Computed by
geodesy.parse.coordinates 1.3.0, core 0.1.0
Model
geoprims coordinate grammar (ISO 6709 notations, NGA MGRS)
Accuracy
Exact: every notation converts by exact arithmetic
Notes
None
Cites
International Organization for Standardization, Geographic Point Location, ISO 6709; National Geospatial-Intelligence Agency, Military Grid Reference System, NGA.STND.0037

Something look off?

Your values

Showing an example. Change anything.
Run many at once from a CSV

Loading…

How we got thisFormula, worked example, sources, and proof

Model: geoprims coordinate grammar (ISO 6709 notations, NGA MGRS)

Show your work

  1. Notation

    which way the position was written

    40°26'46"N 79°58'56"W = DMS

  2. Longitude

    read from that notation, east positive

    40°26'46"N 79°58'56"W = -79.9822222°

  3. Latitude

    read from that notation, north positive

    40°26'46"N 79°58'56"W = 40.4461111°

The same steps an agent gets from the MCP server with explain: true.

Accuracy: Exact: every notation converts by exact arithmetic

When to use this: Use this when a coordinate arrives as text and you do not want to hand-convert it: decimal degrees, degrees and minutes, degrees, minutes and seconds, packed aviation form, labeled pairs, MGRS, UTM, UPS, or a grid code (Maidenhead, GARS, GEOREF, geohash, or a full Plus Code, read as the center of its cell). It reports what it read, in your chosen output form, and says which assumptions it had to make.

Limitations: Text can be genuinely ambiguous — which number is the latitude, which hemisphere an unsigned pair means, whether a comma is a decimal mark — and this tool reports the ambiguity and its alternatives instead of guessing; a short code like fn20 is both a Maidenhead square and a geohash, and both readings are given. A short Plus Code needs a nearby place to complete it and is refused. It cannot know the datum of a bare pair: coordinates are treated as WGS 84 unless the notation itself carries one.

Worked example: Pittsburgh in degrees, minutes, and seconds. Source: add-geodesy-suite parsing scenario: 40.446111…, -79.982222…. It is golden test vector v001, and every build checks the tool still gives its answer within its tolerance.

You enter

Coordinate
40°26'46"N 79°58'56"W

You get

Latitude
40.4461111°
Longitude
-79.9822222°
Notation
DMS
DMS
40°26'46.000"N 79°58'56.000"W

Review: Not yet independently reviewed by a geodesist.

Last verified: 2026-09-18, when a maintainer last confirmed this tool's sources at the issuer. See the sources ledger.

Status: version 1.3.0, core 0.1.0. See this tool in the verification report.

Changes

Checked against: 42 golden test vectors (download the test vectors, each with its source and tolerance). See how results are checked and every source.

Sources

Terms

DMS: degrees, minutes, seconds
An angle written as whole degrees, minutes (1/60 degree), and seconds (1/3600 degree), like 40°26'46". Source: ISO 6709 Geographic point location

DMS — degrees, minutes, seconds

An angle written as whole degrees, minutes (1/60 degree), and seconds (1/3600 degree), like 40°26'46".

Source: ISO 6709 Geographic point location