Interactive publication
Back to the catalogueData qualityCase 13 of 14
Wrong CRS assumed
Coordinates delivered in a projected or regional CRS (e.g. State Plane, UTM) but consumed as if they were WGS84 lat/lng place points thousands of kilometers off with no error thrown.
Class
Case to account for
Affects
2 conversions
01
Detection
Coordinate magnitudes inconsistent with WGS84 range (e.g. values in the millions typical of a projected CRS false easting/northing).
02
Mitigation
01
Require and validate an explicit CRS tag on every geometry source
02
Reproject to WGS84 (EPSG:4326) before any H3 indexing step
03
Affected conversions
PointH3
OPENPolygonH3 (intersects)
OPENMore in Data quality
Accuracy-radius attritionAxis-order reversal (lat/lng swap)Coastal / mixed pixelsConfidence-convention mismatchDuplicated region IDsGeocoding uncertaintyIncomplete geometryMissing CRS declarationMissing polygonsRaster no-data valuesRaster/cell resolution mismatchRounded / truncated coordinatesZero-island coordinates