Remove regional H5 path templates from US Populace release contract
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
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.
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.
- Dominant language
- Python
- Stars
- 7
- Forks
- 9
- Avg merge
- 12h 29m
- Merged PRs (30d)
- 10
Getting set up
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.
More from PolicyEngine/policyengine.py
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PolicyEngine/policyengine.py#473 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PolicyEngine/policyengine.py#436 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PolicyEngine/policyengine.py#408 ·
-
Map the stored WIC take-up draw (would_claim_wic) onto takes_up_wic_if_eligible when loading US dataOpen
Difficulty 4/5 3-5 days Newbie friendliness 64/100
PolicyEngine/policyengine.py#530 ·
-
Design note: a weighted module inside policyengine.py, replacing the microdf dependencyPossibly taken @MaxGhenis claimed this 4 days ago. Open
PolicyEngine/policyengine.py#528 · 1 assignee ·
All issues in PolicyEngine/policyengine.py
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
kristofdegrave/homeassistant-smart-charging#1413 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
nasa/earthdata-varinfo#113 ·
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
githubnext/gh-aw-workshop#3849 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day