Plus Code Finder

Plus Codes encode location into a grid reference that works even where street addresses are weak

Open Location Code converts latitude/longitude into an alphanumeric area code. It is useful for rural sites, meeting points and locations that lack a conventional street address.

A Plus Code represents an area, not a legally assigned address. Short codes also depend on locality context, so preserve the full code when sharing across regions or systems.

When this tool is useful

Use Plus Code Finder when the question matches the method the page actually uses. Typical workflows include:

• Compare two or more scenarios involving open location code without creating an account or installing desktop software.
• Use the output as a planning or teaching reference, then move to an official or specialist source if the result affects legal, safety, engineering or financial decisions.
• Run the same workflow for locations in different countries while keeping units and assumptions consistent.

Worked examples

These examples are meant to show how to interpret this kind of output, not to replace the values produced from your own inputs.

• 40.7128, −74.0060 — The same Lower Manhattan point can be written as 40° 42' 46.08" N, 74° 0' 21.60" W or 18N 583959 4507351. Different formats describe the same location.
• MGRS precision — For the same sample point, a 10-digit MGRS reference is 18?WK8395907350. More digits increase numeric precision, not the accuracy of the original measurement.
• Decimal places — Five decimal places of latitude are roughly metre-scale. That does not mean a phone GPS measurement itself is accurate to one metre.

How to interpret the result

The most common errors come from using a correct result to answer the wrong geographic question. Keep these points in mind for Plus Code Finder:

• 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.

Limits & appropriate use

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.

Data & methodology

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.

For source details, licences and model limitations, see Data Sources and Methodology.

Key terms worth knowing

Datum

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

DMS

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

Go deeper: guides & original studies

Use these resources when you need the reasoning behind the calculation, a comparison with another geographic method, or an example of the same approach applied across a dataset.

Related tools

If this page answers only part of your question, these tools use a nearby but different method or dataset.