What an offset or shifted coordinate looks like
An offset coordinate is one that plots close to the expected location but not exactly on it. Unlike a coordinate that lands in the wrong country or the wrong continent, an offset point is tantalisingly close. It looks plausible enough that it might go unnoticed unless you check carefully.
The shift is usually consistent. If one point is 100 metres northwest of where it should be, the other points from the same source will typically be shifted by a similar distance in a similar direction. That consistency is itself a diagnostic clue, because it points toward a systematic cause rather than random error.
Cause 1: Datum mismatch (the most common cause)
The single most common reason for offset coordinates is a datum mismatch. A datum is the mathematical model of the Earth that a coordinate system is built on. Different datums define the shape of the Earth slightly differently, which means the same latitude and longitude values describe slightly different physical locations depending on the datum.
In the UK, the most important datum distinction is between WGS84 and OSGB36. WGS84 is the datum used by GPS, smartphones, Google Maps, and most web mapping tools. OSGB36 is the datum used by Ordnance Survey and British National Grid. The offset between the two can be up to about 120 metres across Great Britain, with a typical shift of around 70 to 100 metres in most of England.
If a latitude/longitude pair was originally captured or calculated in the OSGB36 datum and then plotted on a WGS84 map without transformation, the point will land in the wrong place by that offset distance.
| Scenario | Typical offset | Direction |
|---|---|---|
| OSGB36 lat/long plotted on WGS84 map | ~70 to 120 m | Generally northeast |
| WGS84 lat/long used in OSGB36 GIS project | ~70 to 120 m | Generally southwest |
| ED50 coordinates plotted on WGS84 map | ~50 to 200 m | Varies by location in Europe |
| NAD27 vs NAD83 in North America | ~10 to 100 m | Varies by location |
Cause 2: Projection-related distortion
Every projected coordinate system introduces some distortion when it flattens the Earth onto a plane. In well-designed systems like UTM and British National Grid, the distortion is kept very small within the intended area. But if coordinates are used outside the intended zone, or if the wrong projection is applied during conversion, the result can be a measurable offset.
For example, UTM coordinates from Zone 30 processed as if they were Zone 31 will produce a shifted result. Projection-related offsets tend to be larger and more variable than datum offsets.
Cause 3: GPS or device accuracy limits
Consumer GPS devices and smartphones typically deliver accuracy of 3 to 10 metres under good conditions. In built-up areas, under tree canopy, or near tall buildings, accuracy can drop to 15 metres or more. That means even a perfectly handled coordinate will have some positional uncertainty baked in from the moment it was captured.
If you are seeing offsets of 5 to 15 metres and the coordinate came from a consumer GPS or phone, the shift may simply be the expected accuracy of the source device rather than a data handling problem.
| Source | Typical accuracy | Notes |
|---|---|---|
| Smartphone GPS | 3 to 10 m | Varies with signal quality and environment |
| Handheld GPS unit | 2 to 5 m | Better with WAAS/EGNOS correction |
| Survey-grade GPS (RTK) | 1 to 3 cm | Requires base station or correction network |
| Total station | mm-level | Requires line of sight to target |
| Google Maps pin drop | 5 to 50 m | Depends on zoom level and user precision |
Cause 4: Rounding or truncation of coordinate values
If a coordinate has been rounded or truncated, the resulting loss of precision can shift the plotted point. In Decimal Degrees, each decimal place represents roughly a factor-of-ten reduction in ground distance. Rounding from six decimal places to three reduces precision from about 0.1 metres to about 111 metres.
If the offset is small and inconsistent between points rather than uniform, rounding or truncation is a likely cause.
Cause 5: Map tile or imagery alignment issues
Sometimes the coordinate is actually correct, but the map tiles or satellite imagery underneath it are slightly misaligned. This is more common than many users realise. Google Maps, Bing Maps, and OpenStreetMap all use imagery from different sources and dates.
If you see a consistent offset between your coordinates and the visible features on the satellite view, but the coordinates are correct when checked against a different map source, the issue may be with the imagery rather than the data.
How to diagnose the offset
The size and consistency of the offset are the two most useful diagnostic clues:
| Offset size | Consistency | Most likely cause |
|---|---|---|
| 50 to 150 m | All points shifted same direction | Datum mismatch (e.g. WGS84 vs OSGB36) |
| 3 to 15 m | Random direction per point | GPS/device accuracy limit |
| 100+ m, increasing with distance | Grows toward edges of dataset | Wrong projection or UTM zone |
| Variable, up to ~100 m | Some points more affected than others | Rounding or truncation of values |
| 5 to 20 m | Consistent, visible on satellite imagery | Map tile or imagery misalignment |
How to fix offset coordinates
The fix depends entirely on the cause:
- Datum mismatch: apply the correct datum transformation. For UK work, this means converting between WGS84 and OSGB36 using the appropriate transformation. CoordinateMapper handles this automatically when converting between latitude/longitude and British National Grid.
- Projection error: confirm the correct UTM zone or grid system and re-convert with the right parameters.
- GPS accuracy: accept the inherent limitation of the capture device. If higher accuracy is needed, recapture with better equipment.
- Rounding: go back to the original source and recover the full-precision coordinate before rounding occurred.
- Imagery misalignment: verify the coordinate against a second map source before concluding the data is wrong.
How to prevent offset problems
- Always record the datum alongside your coordinates. "51.5074, -0.1278 (WGS84)" is far more useful than "51.5074, -0.1278" alone.
- When combining data from multiple sources, convert everything to a single datum before merging.
- Store coordinates at full precision, even if you display them rounded.
- When working in the UK, be especially aware of the WGS84/OSGB36 distinction.
- Always plot and visually check coordinates on a map before using them in reports, planning submissions, or downstream systems.
Takeaway
Offset coordinates are almost always a datum, projection, accuracy, or precision problem rather than a formatting problem. The key diagnostic step is measuring the size and consistency of the shift. A uniform offset of 50 to 150 metres across all points strongly suggests a datum mismatch. A random scatter of a few metres per point suggests GPS accuracy limits. And a growing offset toward the edges of the dataset suggests a projection issue. Identifying the cause correctly is essential, because each one requires a different fix.