Skip to content

Select UK local-authority lookup by dataset - #542

Closed
anth-volk wants to merge 3 commits into
mainfrom
feat/dataset-aware-uk-local-authorities
Closed

anth-volk wants to merge 3 commits into
mainfrom
feat/dataset-aware-uk-local-authorities

Conversation

@anth-volk

Copy link
Copy Markdown
Contributor

Fixes #541

Adds typed bundle metadata for the LAD22 and LAD23 lookup assets. Explicitly listed legacy UK dataset identities resolve to LAD22; every other identity defaults to LAD23. Managed lookup files are verified against pinned SHA-256 hashes before use, while an explicit caller-owned path remains an intentional override.

The local-authority output accepts the managed dataset identity so service callers can select metadata that matches the codes emitted by the dataset.

Test plan:

  • make format
  • make lint
  • uv run --python 3.13 --extra dev pytest tests/test_uk_geography_assets.py tests/test_local_authority_impact.py tests/test_uk_regions.py tests/test_bundle.py tests/test_bundle_metadata.py -q
  • uv run --python 3.13 --extra dev python scripts/bundle.py check

@anth-volk

Copy link
Copy Markdown
Contributor Author

Superseded by PolicyEngine/policyengine-sim-api#705. The replacement identifies the authority roster from actual la_code_oa values and does not route lookup data by dataset name or release identity, so no PolicyEngine.py change is required.

@anth-volk

Copy link
Copy Markdown
Contributor Author

Update: the replacement simulation API work is now PolicyEngine/policyengine-sim-api#706. GitHub closed #705 when its branch was renamed.

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.

Select UK local-authority lookup by dataset identity

1 participant