Skip to content

feat: report duplicate group counts in the dq summary - #507

Open
Javiershenbc wants to merge 5 commits into
mainfrom
feat/TECH-11128-dqr-new-checks
Open

feat: report duplicate group counts in the dq summary#507
Javiershenbc wants to merge 5 commits into
mainfrom
feat/TECH-11128-dqr-new-checks

Conversation

@Javiershenbc

Copy link
Copy Markdown
Collaborator

The group id/size columns are metadata, not 0/1 checks, so METADATA_CHECK_KEYS filtered them out of the aggregation. Aggregate them separately and expose count_duplicate_location_groups and count_proximity_50m_groups, counted only over approved rows, with their thresholds so the PDF label cannot drift from the number. Omitted when the columns are absent, so other pipelines are unchanged.

The group id/size columns are metadata, not 0/1 checks, so METADATA_CHECK_KEYS filtered them out of the aggregation. Aggregate them separately and expose count_duplicate_location_groups and count_proximity_50m_groups, counted only over approved rows, with their thresholds so the PDF label cannot drift from the number. Omitted when the columns are absent, so other pipelines are unchanged.
Javiershenbc and others added 4 commits September 4, 2026 00:04
Set
DUPLICATE_LOCATION_GROUP_MIN_SIZE
PROXIMITY_50M_GROUP_MIN_SIZE

variables, they also can be set from env vars
"DQ Check Category" is free text and becomes a top-level key of dq-summary.json, so "location checks" and "location_checks" shipped as two sections and split the location tier in half. Normalise to snake_case, and move the two "critical checks" comparisons to a shared constant so they cannot drift from it again.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant