How Many Decimal Places for GPS Coordinates? Precision Explained

When working with Latitude and Longitude in decimal degrees (e.g., 38.8895° N, -77.0353° W), the number of decimal places dictates the precision of the location. A common mistake is providing either too few decimals (placing a point miles away from the target) or far too many (implying millimeter precision from a smartphone).

The 5-Decimal Rule: For almost all commercial GPS, mapping, and GIS tracking applications, 5 decimal places (e.g., 40.12345) is the correct standard. It provides approximately 1.1 meters (3.6 feet) of precision, which matches the physical accuracy of commercial GPS receivers.

Precision Scale: What Each Digit Means

At the equator, one degree of latitude equals about 111 kilometers. Therefore, moving the decimal point one place scales the precision by a factor of 10. (Note: Longitude lines converge at the poles, so the east-west distance gets smaller as you move north/south, but latitude distances remain roughly constant).

DecimalsExampleApproximate Accuracy (at Equator)Use Case
040111 km (69 miles)Identifying a country or large state.
140.111.1 km (6.9 miles)Identifying a large city or county.
240.121.11 km (0.69 miles)Town or neighborhood level.
340.123111 meters (364 feet)Identifying a specific neighborhood block or large estate.
440.123411.1 meters (36.4 feet)Identifying a specific parcel or street. (Common car GPS output).
540.123451.11 meters (3.6 feet)The Sweet Spot. Identifying a specific tree, door, or person. Matches smartphone GPS accuracy.
640.12345611.1 centimeters (4.4 inches)Specialized mapping, differential GPS, laying out rough construction.
740.12345671.11 centimeters (0.44 inches)Survey-grade RTK GPS. Requires professional geodetic equipment.
8+40.123456781.11 millimetersTectonic plate tracking. Essentially meaningless for static mapping.

The False Precision Trap

Software developers frequently export Latitude and Longitude as raw 64-bit floating-point numbers containing 13 or 14 decimal places (e.g., 40.1234567890123). This is false precision.

Unless the coordinate was generated by a geodetic surveyor using an RTK base station, taking a phone GPS reading and displaying 14 decimal places implies the coordinate is accurate to the size of a single human cell. In reality, the phone's hardware error circle was 4 meters wide. All digits after the 5th decimal place are random numerical noise.

Database Optimization: Storing 14 decimal places for millions of tracking coordinates in a spatial database wastes massive amounts of index space and memory. Truncating incoming coordinates to 5 or 6 decimal places (using DECIMAL(9,5) or DECIMAL(9,6)) before inserting into a database can speed up geospatial queries significantly.

Convert decimal coordinates to DMS or UTM and see how the precision holds up:

→ Decimal to DMS Coordinate Converter

UTM Precision Comparison

Unlike Lat/Long, UTM coordinates are measured in actual meters. Therefore:

This linear simplicity is why civil engineers prefer UTM or State Plane over calculating decimals of a degree.

FAQ

How many decimal places does Google Maps use?

When you right-click a location in Google Maps, the web interface typically copies coordinates to 5, 6, or 7 decimal places. Google's internal APIs often accept data at any precision but calculate paths based on routing nodes.

Why do longitude distances change by location?

Lines of longitude converge at the North and South Poles. At the equator, 1 degree of longitude is ~111km. At 60 degrees North (e.g., Oslo), 1 degree of longitude is only ~55km wide. Latitude distances, however, stay relatively constant pole to pole.

See also: MGRS Precision Levels | Data Validation

US State Plane (SPCS) Converters & Local Guides

Professional engineering and surveying transformations from state-specific conformal grids to GPS WGS84.