What the location accuracy circle means

The circle around the dot

The radius expresses uncertainty around a reported coordinate.

A location provider returns a latitude and longitude as its best current estimate. It can also return an estimated horizontal accuracy in metres. Mapping software commonly draws that distance as a circle centred on the reported point.

The true position is not known to the device, so the circle cannot be a measured distance to the truth. It is an uncertainty estimate made from the provider's model and available observations. A smaller circle says the provider reports tighter uncertainty under that model. It does not certify that the centre is correct.

Nor is the edge a physical boundary. A true position can lie outside the circle because confidence is probabilistic and the model can miss a systematic error such as persistent reflection. The display should be read as a quality cue, not a fence.

The hidden convention

The same radius can represent a different stated probability.

Android's Location API defines horizontal accuracy as a radius with a 68 per cent chance of containing the true position. The W3C Geolocation specification uses a 95 per cent confidence level for its accuracy field. Apple describes CLLocation horizontal accuracy as a radius of uncertainty but does not state the same confidence convention on the general CLLocation reference page.

This prevents a clean comparison based on the number alone. A ten-metre value from one API and a ten-metre value from another need not describe the same statistical boundary. An app can also transform, round or style the provider value before drawing it.

Confidence is not a percentage chance that the map, route line or destination is correct. It concerns the position estimate under the API's definition.

Separate evidence

Horizontal uncertainty does not cover age, height or map quality.

• AgeA small circle around an old cached position may be precise for a place you have already left.
• Vertical errorHorizontal accuracy says nothing about altitude uncertainty unless a separate vertical value is provided.
• Map alignmentA mapped path can be displaced even when the location coordinate is good.
• Route geometryA GPX line can be simplified, planned on different mapping or recorded with its own error.
• Privacy precisionAn approximate permission can deliberately broaden the delivered location regardless of physical GNSS conditions.

A route comparison therefore has at least three geometries: the estimated current position, the saved route line and the background map. One circle cannot validate all three.

A better reading

Read size, freshness and behaviour together.

1. Check

   Look for a current timestamp.

   A fresh broad estimate can be more useful than a stale tight one.

2. Watch

   Observe the trend rather than one frame.

   A shrinking circle after entering open sky suggests the provider is refining the solution.

3. Compare

   Use visible terrain and route context.

   Do not choose a branch solely because the centre dot falls on it.

4. Pause

   Let a fresh solution arrive.

   Movement through a poor reception area can leave the display catching up.

When the circle remains unexpectedly broad, check precise location permission, the local sky view and power settings. The companion article on phone GPS accuracy places that report in the wider receiver chain.