Coordinates invite a false sense of exactness. A phone happily displays eight decimal places, a number that claims to locate you within a millimeter, from a signal that cannot locate you within a car length. The digits are free; the accuracy is not. This article gives you the conversion table everyone looks for, then the more valuable thing: the rule for deciding how many of those digits deserve to survive when you write a coordinate down, share it, or store it. For how coordinates are written and formatted in general, see our guide to latitude and longitude formats; this article owns the precision question alone.
Home / Coordinates and Location Formats
GPS Coordinates: How Many Decimal Places Do You Actually Need?

Photo: Joice Rivas / Pexels
Coordinate Converter: Watch the Places Change
Convert a pair, then trim its decimal places one at a time and watch the meaning shrink from a region to a doorway. Five places is the honest limit of a phone fix; six belongs to survey gear.
From decimal degrees
Your latitude breaks down as 40 degrees, 41 minutes, 21.00 seconds. One degree is 60 minutes, one minute is 60 seconds, so a second of latitude is about 31 meters on the ground.
From degrees minutes seconds
Conversions use the WGS 84 coordinate system, the same one GPS satellites and phone maps use. Plus codes are computed with the open location code algorithm, the same method Google Maps uses.
The Table: What Each Decimal Place Is Worth on the Ground
A degree of latitude spans about 111 kilometers everywhere on Earth, and each additional decimal place divides that by ten. The result is the table at the heart of every precision discussion:
| Decimal places | Latitude distance | What it identifies |
|---|---|---|
| 0 | about 111 km | a region or small country |
| 1 | about 11.1 km | a city and its suburbs |
| 2 | about 1.11 km | a neighborhood or village |
| 3 | about 111 m | a large field, a campus, a few streets |
| 4 | about 11.1 m | a building, a house plot |
| 5 | about 1.11 m | a doorway, a parking space, a tree |
| 6 | about 11 cm | a survey marker, a specific corner |
| 7 | about 1.1 cm | a point on a machine part |
| 8 | about 1.1 mm | nothing a GPS should be claiming |
Read the table as resolution, not accuracy: five places can name a square about a meter across. Whether your point actually sits in that square depends on the measurement, which is where the next section earns its keep.
Longitude Shrinks: The cos(Latitude) Twist
The table above is exact only for latitude. Longitude degrees converge toward the poles, so a degree of longitude spans about 111 km at the equator, about 85 km at 40 degrees latitude, about 56 km at 60 degrees, and nothing at the pole itself. The shrink factor is the cosine of the latitude. Practically: at temperate latitudes, the sixth decimal place of longitude is worth noticeably less ground distance than the sixth place of latitude (at 40 degrees, roughly 8.5 cm rather than 11 cm), and at high latitudes the longitude digits inflate in number while shrinking in meaning. Anyone storing coordinates for a northern dataset and quoting centimeter precision from digit counts alone is fooling themselves in the longitude column first.
The Accuracy Reality: What GPS.gov Says About Your Phone
Against the table, set the measurement reality. GPS.gov, the United States government's own GPS site, states that GPS enabled smartphones are typically accurate to within about 4.9 meters (16 feet) at 95 percent confidence under open sky, and worse around buildings, bridges, and trees. Compare that with the table: 4.9 meters sits between the fourth decimal place (11.1 m) and the fifth (1.11 m). So a phone fix, at its documented best, honestly supports about five decimal places, and the fifth is already generous on a bad day. Digits six, seven, and eight from a phone are arithmetic exhaust: the receiver computed them, but they encode noise, not knowledge. Survey grade receivers with corrections are a different world and genuinely earn six or seven places; that is exactly why the rule below is about the source, not the number.

The Rule: Match the Places to the Source
One sentence decides every case: never report more precision than the source supports. Applied:
- Phone or watch fix, shared with a person: five places. It names the doorway without pretending to survey it, and it keeps the coordinate short enough to read aloud and type without error.
- Phone fix stored in a dataset: keep five, or keep the raw reading plus a note of its source. Trimming is honest; padding with copied digits is fabrication.
- Dedicated handheld GPS: five to six, depending on conditions; six under open sky with a settled fix.
- Survey or RTK corrected data: six to seven, with the correction method recorded, because the digits are only meaningful with their provenance.
- A point read off a map by eye or by clicking: four to five. Your click has a pixel size, and the map's own imagery alignment adds its error to yours.
Two corollaries matter as much as the rule. First, rounding is not losing data when the discarded digits were noise; it is removing a false claim. Second, truncation direction: round normally rather than chopping digits, since chopping biases every point in one direction, a small systematic shove applied to an entire dataset.
Why Extra Digits Actively Hurt
False precision is not harmless decoration. Long coordinates are harder to type, dictate, and proofread, and every extra digit is another chance to transpose two and land in the wrong field while looking more authoritative than the four place version. In datasets, mixed precision hides quality: a column where survey points and phone points both carry seven places pretends they are equals, and the person analyzing them later cannot tell which points to trust. And in shared locations, an eight place coordinate quietly promises a rescue service or a delivery driver an exactness nobody has, which can send them hunting the wrong square meter of a large site. Five honest places beat eight theatrical ones in every one of these cases.
One Coordinate at Every Precision
Watch a single real point shrink as the places fall away. Take a trailhead at 45.923706, 6.869433 (latitude, longitude, somewhere in the French Alps):
- 2 places: 45.92, 6.87. A square about a kilometer across. You have named the village, not the trailhead. Good enough for a weather forecast or a regional map.
- 3 places: 45.924, 6.869. About 111 meters in latitude. The right neighborhood of the mountain: a parking area, a hamlet, a large site.
- 4 places: 45.9237, 6.8694. About 11 meters. The trailhead itself, its sign, its car park. This is the precision of a point picked carefully off a map.
- 5 places: 45.92371, 6.86943. About 1.1 meters. The gate at the trailhead's edge. The most a phone fix should claim, and the right stopping point for anything a consumer device measured.
- 6 places: 45.923706, 6.869433. About 11 centimeters. The corner of the signpost. A claim only survey equipment with corrections can cash.
- 7 places and beyond. Centimeters to millimeters: machine parts and tectonic plates, measured by instruments that cost more than cars.
Notice what the exercise reveals: each added place is a promise. The coordinate does not get better as it gets longer; it gets more specific about what it promises, and honesty consists of promising only what the measurement behind it can deliver.
What Different Jobs Actually Use
Precision conventions differ by trade, and matching your audience's convention is part of matching the source. Emergency and rescue work trades in five places or in dedicated grid systems, because the number must be short enough to read over a radio without error and exact enough to find a person. Geocaching publishes coordinates to five places (often written as degrees and decimal minutes to three places, which resolves similarly), because the game is finding a container, not a molecule. Property and construction live at six places and beyond, backed by instruments and correction services that earn them, and their documents say so. Web maps and APIs traffic in six places as a storage default, which is a statement about databases, not about the accuracy of the points stored, and mistaking the storage format for a measurement claim is the most common professional version of the false precision error. When you hand coordinates to another trade, hand them at that trade's convention and say what measured them; both halves of that sentence are the professionalism.
Accuracy and Precision Are Not the Same Word
One distinction powers this whole subject, and it is worth stating nakedly before the FAQ. Precision is how finely a number is divided: the decimal places, a property of the digits. Accuracy is how close the number sits to the truth: a property of the measurement. A coordinate can be exquisitely precise and badly inaccurate, the eight place readout of a fix that multipath moved twenty meters, and it can be imprecise and perfectly accurate, the three place reference to a summit that is exactly where claimed, somewhere in its hundred meter square. Decimal places are free; accuracy is earned by instruments, sky view, and time. The craft taught in this article is matching the free thing to the earned thing, neither inflating the digits to flatter a weak fix nor rounding a strong survey down to a guess. When someone hands you a coordinate, the places tell you what they are claiming. Whether they can cash the claim is a question about their receiver, not their formatting, and now you know to ask it.
A Rule You Can Keep
Compress the whole subject into one pocket rule: publish five places for anything a phone measured, six for anything a survey produced, and never let the places outrun the instrument. Five places says "within about a meter," which is the truth about consumer GPS at its best and a fair rounding of its usual few meters. Six says "within about ten centimeters," which is a claim for corrected, professional measurement to make. Anything beyond six belongs to specialists who will not need this article, and anything below four belongs to maps, not coordinates. Match the digits to the device, and every coordinate you hand out will be exactly as trustworthy as it looks, no more and, importantly, no less.
Related Guides
Readers working through this topic usually need its closest companions too. These coordinates guides cover the neighboring ground:
- GPS Coordinates Accuracy: What the Numbers Actually Promise: GPS accuracy is two different quantities wearing one name.
- How to Find the Length Between Coordinates: The Distance Formula, in 2D, 3D, and on the Earth: The length between two coordinates is the distance formula, which is Pythagoras wearing coordinates: square the gap in x, square the gap in y,...
- Plus Code vs what3words: Open vs Proprietary, and Which One to Actually Use: Plus codes and what3words both turn a location into a short code, and they could not be more different underneath.
Frequently Asked Questions
How many decimal places do I need for GPS coordinates?
For a phone or watch fix, five decimal places is the honest standard: it resolves to about 1.11 meters, which matches the roughly 4.9 meter accuracy GPS.gov documents for smartphones under open sky. Four places (about 11 meters) suits points picked from a map. Six or more places are justified only for survey grade or corrected measurements.
What does the sixth decimal place represent?
About 11 centimeters in latitude, and less in longitude away from the equator, because longitude degrees shrink by the cosine of the latitude. Six places is the realm of survey markers and measured corners. A consumer phone reporting six places is displaying computed digits, not measured accuracy.
Are more decimal places always better?
No. Digits beyond your source's accuracy encode noise and create false confidence. They also make coordinates longer to type and easier to corrupt, and they hide quality differences inside datasets. Match the places to the measurement: five for phones, six to seven only for survey grade data with its method recorded.
Why is longitude precision different from latitude precision?
Latitude degrees are evenly spaced at about 111 km everywhere. Longitude degrees converge toward the poles, spanning about 111 km at the equator, about 85 km at 40 degrees, and about 56 km at 60 degrees. So each longitude decimal place is worth less ground distance the farther you are from the equator, by a factor of cos(latitude).
Should I round coordinates or truncate them?
Round them. Truncating (simply cutting off digits) shifts every point systematically in one direction, by up to a full unit of the last kept place. Rounding distributes the error evenly and keeps the reported point as close as possible to the measured one.
Photo credits: Joice Rivas (Pexels); Stanislav Kondratiev (Pexels). Photos are served from this site; follow the credit to the library page for the original.