Coordinate Precision Tool
Control how many decimal places you keep when copying lat/lng for forms and APIs.
By Aryan Khan, Founder & Editor · Updated October 2026
For example, a phone fix honest to about 5 metres deserves 5 decimals (1.1 m grain) — the 8th decimal your app displays is measuring the table your phone sits on, not the world.
How to use Coordinate Precision Tool
Decimals are a claim. Make the claim your data can defend:
The Coordinate Precision Tool controls how many decimal places you keep when copying latitude and longitude for forms and APIs. Set the places and read the trimmed pair — precision chosen on purpose, matched to your source's real accuracy instead of inherited from a screen's enthusiasm.
- 1Find a point.
- 2Copy with the precision you need.
What people use Coordinate Precision Tool for
1. Form and API compliance
Some systems demand exactly 6 places, others choke on 8. Trim deliberately here rather than letting a form truncate silently — mid-digit truncations move points.
2. Honest publication
Publishing a sensitive site's coordinates at 3 places (111 m grain) is the standard fuzz — sized by the Decimal Degree Precision Calculator's table, applied by this tool.
3. Consistent datasets
Mixed-precision columns look sloppy and join badly. Normalise the column's dress to its least-accurate member's honesty.
4. Report writing
Coordinates in prose should carry the precision the method earned — typically 5 for GPS fieldwork, 4 for map-read points.
Worked examples
4 places ≈ 11 m, 5 ≈ 1.1 m, 6 ≈ 0.11 m (latitude grain, computed). Choosing 6 for a handheld GPS fix overclaims by two orders of magnitude — the ladder makes the overclaim visible.
Cutting digits (truncation) biases every point one way; rounding is neutral. This tool rounds — a small professionalism with systematic consequences at scale.
Decimal places and ground grain
Latitude grain (longitude's is finer away from the equator) — computed from WGS84 degree lengths.
| Decimals | Grain | Honest source |
|---|---|---|
| 2 | ~1.1 km | A town reference |
| 3 | ~111 m | A map-read point |
| 4 | ~11 m | A decent map click |
| 5 | ~1.1 m | A good phone fix |
| 6 | ~0.11 m | Survey-adjacent kit |
| 7+ | Centimetres and below | Geodetic instruments — or fiction |
Grain is resolution, not accuracy: a 7-decimal point can still be 50 m wrong if the fix was. Precision displays; accuracy is earned upstream.
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 Coordinate Precision Tool:
- 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
The coordinate workspace changes displayed decimal places and share URL precision. More digits do not improve the accuracy of the source position.
For source details, licences and model limitations, see Data Sources and Methodology.
Key terms worth knowing
- 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.
Editorial guidance: MapBench explains the method and limitations so the tool can be used as a transparent reference, not as a black-box answer. For legal boundaries, safety-critical routing, surveying, engineering, regulated decisions or official statistics, verify the result with the responsible authority or a qualified professional.
Category: Coordinates. Results are intended for everyday analysis and planning unless a page explicitly states otherwise.
Method, assumptions & limits
- This tool’s method
- The coordinate workspace changes displayed decimal places and share URL precision. More digits do not improve the accuracy of the source position.
- Before relying on the answer
- Record the coordinate order, signs, format and datum where specified. In GeoJSON, positions are longitude first; many input forms ask for latitude first.
- What the result cannot establish
- A format conversion preserves the source measurement's uncertainty. Extra digits do not improve the original GPS fix.
Coverage: Worldwide. Search, basemap and external data requests may use third-party services; browser-based does not mean every operation is offline. Read the source and licence notes, calculation methodology and privacy policy. If a result looks inconsistent, report a correction with the inputs and mode used.
Frequently asked questions
Clear answers about the calculation, accuracy and appropriate use.
How many decimals?
~5 decimals ≈ 1 m order; more is rarely meaningful for consumer GPS.
Which datum do these coordinate tools use?
MapBench location tools generally use WGS84 latitude and longitude, the same global reference system commonly used by GPS and web maps.
Do more decimal places always mean better accuracy?
No. More digits increase numeric precision, but they cannot improve the accuracy of the original GPS, survey or source data.
Can I copy the result into GIS software?
Usually yes. Check the format, axis order and datum expected by the destination software before importing.
How many decimals should I keep?
One more than your accuracy earns: phone fixes 5, map clicks 4, survey kit 6. The table on this page prices each place in metres — choose with it open.
Rounding or truncation?
Rounding — truncation systematically drags points southwest (northeast in southern/eastern sign terms), a bias invisible per-point and obvious per-dataset.
The form wants exactly N places.
Set N here and copy the dressed value — trailing zeros included, which is what 'exactly N' usually means.
Privacy fuzzing?
Dropping to 3 or 2 places is the standard deliberate fuzz for sensitive locations — size it with the grain table so the fuzz matches the intent.
Longitude grain differs?
Yes — finer by the cosine of latitude. The table quotes latitude (the conservative axis); your longitude grain at 60° is half the table's.
Negative zero and edge dress?
Rounded outputs normalise cosmetic oddities (−0.0000 becomes 0.0000) — parsers downstream appreciate it.
Batch trimming?
One pair at a time here; the rounding tool is its sibling for quick jobs, and scripts wear the bulk work.
Should I store full precision anyway?
Store the fullest honest value; dress copies for use. Storage precision is cheap — false display precision is the sin, not the digits themselves.
Related tools and resources
Grain maths: the Decimal Degree Precision Calculator; rounding sibling: the Coordinate Rounding Tool; seconds: the Arcseconds to Ground Distance Calculator.
More free tools
Sources, methodology & editorial trust
- ✓ Browser-first processing where supported
- ✓ External sources are documented
- ✓ No account required for public tools
- ✓ Review data sources
Calculations are documented with their assumptions, limitations and source context rather than presented as unexplained answers.
Reviewed and maintained by Aryan Khan, Founder & Editor of MapBench.
Part of our coordinates hub
Coordinate Precision Tool sits in the coordinates cluster, alongside 63 other tools that answer neighbouring questions with different methods or datasets.
You may also need
When this answer is only part of the job, these clusters cover the next step.
Read the guide behind this tool
Understanding GPS Coordinates: Formats, Datums and Precision — A practical guide to latitude/longitude: what decimal degrees and DMS really mean, why datums matter, and how many decimal places you actually need.