Interactive publication
Back to the catalogueTemporalCase 09 of 10
Version mismatch between execution and reporting
The H3/boundary/crosswalk version active at campaign execution time can differ from the version active when the reporting/measurement query runs later, causing the same nominal geography to resolve to different actual cells between planning and results.
Class
Case to account for
Affects
3 conversions
01
Detection
Compare the crosswalk/boundary version identifier stamped at execution time against the version currently active when reporting queries run; flag any difference.
02
Mitigation
01
Pin and log the exact crosswalk/boundary version used at execution time in the campaign record
02
Always run reporting/measurement joins against the pinned execution-time version, never the current-latest version
03
Affected conversions
Cell systemcell system
OPENAdmin polygonsH3 (weighted crosswalk)
OPENH3platform-native IDs
OPEN