Skip to content

Audit 118th → 119th boundary catch-up (GA, NC, NY, AL, LA) #1146

@DTrim99

Description

@DTrim99

Problem

Five states had mid-decade congressional redistricting between the
118th and 119th Congresses (i.e., before the 2024 election): GA, NC,
NY, AL, LA. If our districts/*.h5 files for those states were built
against the 118th-Congress boundaries, any TY 2025+ dashboard
attributing impacts to "GA-7" or "NC-1" etc. is labelling households
under the wrong polygon.

GA is the confirmed case — the dashboard at
georgia-2026-tax-changes was pulling 118th polygons from ArcGIS,
which has McBath at GA-6 / McCormick at GA-7 (the pre-2023 layout).
The 119th Congress seated McCormick at GA-6 and McBath at GA-7.

NC, NY, AL, LA need the same audit — confirm whether the current
h5 files reflect 119th boundaries or are still on 118th, and refresh
where needed.

Asks

  • Audit hf://policyengine/policyengine-us-data/districts/GA-NN.h5
    through GA-14 for boundary vintage. Refresh against 119th polygons
    if currently on 118th.
  • Same audit for NC (14 districts), NY (26 districts), AL (7
    districts), LA (6 districts).
  • Cross-reference with Document the boundary vintage of districts/*.h5 files #1143 (boundary-vintage metadata) so each
    audit's outcome lands as a congress: 119 attribute on the h5.

Why now

Closes the loop on the 119th-Congress map state. Without this,
dashboards built today that route through the existing h5 files may
silently attribute impacts to the wrong representatives in five of
the largest delegations.

Related

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions