Interactive publication
Back to the catalogueData qualityCase 01 of 14
Accuracy-radius attrition
Geolocation vendors ship a per-record error bar (accuracy radius, and in some products per-field confidence factors), but downstream ad-serving and reporting schemas carry only the point or cell, so the uncertainty is discarded at the first hop and delivered geography arrives dressed as exact.
Class
Case to account for
Affects
2 conversions
01
Detection
Delivery or reporting records carry a location with no accompanying radius/confidence field although the upstream source publishes one per record.
02
Mitigation
01
Propagate the source's accuracy radius and confidence through every hop that carries the location
02
Pin the statistical meaning of the radius (containment probability) in the schema — vendor documentation may not state one
03
Reject 'exact' locations whose source is a probabilistic lookup
03
Affected conversions
IP lookupH3 (probabilistic crosswalk)
OPENPointH3
OPENChapter
IP Lookup To H3More in Data quality
Axis-order reversal (lat/lng swap)Coastal / mixed pixelsConfidence-convention mismatchDuplicated region IDsGeocoding uncertaintyIncomplete geometryMissing CRS declarationMissing polygonsRaster no-data valuesRaster/cell resolution mismatchRounded / truncated coordinatesWrong CRS assumedZero-island coordinates