Why Are Sensor Coordinates Sometimes Rounded?
From the earlier reference collection. Read the current software blog.
Rounded coordinates can be useful for display or privacy, but their precision must not imply more site accuracy than metadata supports.
Precision in text is not accuracy
A coordinate with many decimal places looks exact, but the number of digits shown does not establish how accurately the sensor’s location is known. A point may have been surveyed precisely, estimated from a map, supplied at a broad site level, or deliberately generalized. Displaying extra digits can create a false impression of certainty.
Rounding can make coordinates easier to read and can reduce needless precision in a public interface. It may also be used to avoid exposing a sensitive exact location. These are different motivations, so a tool should not imply one when it only knows the other.
Explain what the coordinate represents
Metadata should say whether coordinates indicate the instrument, a station, a facility, or an approximate site. A station may cover a larger area than the point drawn on a map. If the actual sensor position is not documented, label the coordinates as representative rather than presenting them as the precise placement of the instrument.
For example, a map marker rounded to two decimal places could represent a broad vicinity. It should not be used to claim that a reading came from a particular side of a shoreline or a specific parcel. The description should explain the intended geographic scale when known.
Keep precision consistent through the data path
Rounding only the map label while retaining higher precision in a public download can undermine the display’s intent. Conversely, permanently discarding detail needed for legitimate analysis may be unnecessary if the source has a well-defined access policy. Decide at which stage generalization occurs, and document how exports and APIs handle it.
If coordinates are transformed or rounded, retain the original source value where appropriate and authorized, with a clear distinction between source and display coordinates. Do not invent a precision estimate from the number of decimal places alone.
Let users interpret the map honestly
A useful interface can include a note such as “marker location is approximate” and provide the source’s stated location precision if available. When that information is unknown, say so. Avoid drawing tiny accuracy circles unless a documented uncertainty supports their size.
Coordinates are part of the measurement context. Display them at a precision that serves the task, while being candid about what the location metadata can establish.