Coordinate Precision Explained
When exporting location data from spreadsheets, mobile devices, or GPS sensors, coordinates often arrive with ten to fourteen decimal places.
A longitude entry might look like 121.5654182930412.
To the untrained eye, more decimal places look like greater accuracy. In reality, ten decimal places measure down to the width of an atom. For web maps, city guides, and business listings, excess decimals create data bloat, slow down network transfers, and give a false sense of precision.
Here is a practical guide to what each decimal place actually means on the ground, and how many numbers you need for clean digital maps.
Decimal Places vs. Real World Distance
Latitude and longitude represent angles on a sphere. Because of that geometry, one degree at the equator equals roughly 111 kilometers.
As you add decimal places, the resolution narrows rapidly:
| Decimal Places | Ground Resolution at Equator | Typical Real World Scale |
|---|---|---|
| 0 | 111 kilometers | Country or large province |
| 1 | 11.1 kilometers | Large metropolitan area |
| 2 | 1.1 kilometers | Town, district, or neighborhood |
| 3 | 110 meters | Large agricultural parcel or industrial park |
| 4 | 11 meters | Individual building footprint or residential parcel |
| 5 | 1.1 meters | Specific doorway, parking stall, or entrance |
| 6 | 0.11 meters | Pavement edge, curbstone, or footsteps |
| 7 | 11 millimeters | Surveying monument or construction stake |
| 8 | 1.1 millimeters | Microscopic structural movement |
For almost every web mapping project, four or five decimal places are all you will ever need.
Five decimal places pinpoint a location within roughly one meter. That is more precise than consumer phone GPS chips, which typically have a margin of error between three and five meters under open skies.
Why Spreadsheets Export Fourteen Decimals
Spreadsheet software like Google Sheets and Microsoft Excel stores numbers as double precision floating point values.
When you convert an address to coordinates, or when you split a coordinate string using formulas, the application performs mathematical calculations that leave behind long numerical tails. The computer is not reporting genuine physical accuracy. It is simply showing the limits of its digital math.
Exporting these long tails into CSV or GeoJSON files inflates file sizes. If your project contains several thousand coordinates, stripping the numbers down to five decimal places can reduce total data weight by thirty percent. Smaller files load faster on mobile networks and render more smoothly in the browser.
Recommended Precision by Project Type
Different mapping goals demand different levels of detail:
- Regional overview maps: Three decimal places provide accuracy within one hundred meters. This level is ideal for wine regions, national parks, and highway driving overviews.
- Store locators and city guides: Four decimal places provide accuracy within eleven meters. This level lands a pin squarely on top of a store, restaurant, or boutique hotel.
- Pedestrian navigation and campus tours: Five decimal places provide accuracy within one meter. This level helps visitors find the exact entrance door, bicycle rack, or courtyard fountain.
- Anything beyond six decimal places: Unnecessary for digital web mapping. Trim them before importing to save memory and avoid clutter.
How to Clean Coordinate Columns Before Import
Before uploading a location spreadsheet to a map builder, apply these quick cleanup rules:
- Round numeric coordinate columns to five decimal places.
- Ensure latitude values stay between negative 90 and positive 90.
- Ensure longitude values stay between negative 180 and positive 180.
- Remove trailing spaces or quotation marks that turn numbers into text strings.
Clean coordinates mean fast geocoding, predictable rendering, and maps that load without hesitation.