PolicyEngine / PolicyEngine/policyengine.py
Remove regional H5 path templates from US Populace release contract
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7
- Forks
- 9
- Avg merge
- 15h 51m
- Merged PRs (30d)
- 9
Description
Populace is moving to a single national US H5 with state/CD scoping columns instead of publishing one file per state or congressional district. policyengine.py still has release/provenance surfaces that assume regional artifact path templates such as states/{state_code}.h5 and districts/{district_code}.h5 in certification tests, fixtures, and bundled country metadata.\n\nMigration target:\n\n- US regions should resolve to the single certified Populace dataset plus a scoping strategy, not regional dataset paths.\n- Certification/provenance should reject or ignore states/*.h5 and districts/*.h5 for Populace releases once the single-H5 contract is active.\n- Keep historical bundle snapshots readable if needed, but do not require new Populace releases to publish regional artifacts.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in policyengine.py and trace the release/provenance surfaces referenced by the certification tests, fixtures, and bundled country metadata. Verify how regional H5 paths are resolved and tested; done means new Populace releases use one certified US H5 with scoping, reject or ignore regional paths, and historical snapshots remain readable where needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, release
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100