Add sldu and sldl variables for state legislative districts #7249
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds two new input variables for state legislative district assignment: - sldu: State Legislative District Upper (State Senate) - sldl: State Legislative District Lower (State Assembly/House) These variables enable state-level policy analysis by legislative district, complementing the existing congressional_district_geoid variable. The values are 3-character codes from Census Bureau Block Assignment Files. Used by policyengine-us-data's block assignment infrastructure to assign households to their state legislative districts based on Census geography. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Adds comprehensive set of geographic input variables from Census Bureau: - block_geoid: 15-digit census block identifier (most granular) - tract_geoid: 11-digit census tract identifier - cbsa_code: Core-Based Statistical Area (metro/micro area) - place_fips: City/CDP place code - vtd: Voting Tabulation District - puma: Public Use Microdata Area - sldu: State Legislative District Upper (state senate) - sldl: State Legislative District Lower (state assembly/house) These variables enable granular geographic analysis at multiple levels. All can be derived from block_geoid during dataset builds using the policyengine-us-data block assignment infrastructure. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add ZCTA (ZIP Code Tabulation Area) variable - Fix block_geoid example: Queens -> New York County (Manhattan) - Use zero-padded codes in sldu/sldl tests to match Census format Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Keep only default value tests since identity tests don't validate any logic. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
…t-variables Add zcta variable and fix documentation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds comprehensive set of geographic input variables from Census Bureau for granular geographic analysis:
block_geoid: 15-digit census block identifier (most granular geographic unit)tract_geoid: 11-digit census tract identifiercbsa_code: Core-Based Statistical Area (metro/micro area)place_fips: City/CDP place codevtd: Voting Tabulation Districtpuma: Public Use Microdata Areasldu: State Legislative District Upper (state senate)sldl: State Legislative District Lower (state assembly/house)zcta: ZIP Code Tabulation Area (Census approximation of ZIP codes)These variables enable analysis at multiple geographic granularities. All can be derived from
block_geoidduring dataset builds using the policyengine-us-data block assignment infrastructure.This is a prerequisite for policyengine-us-data#484 which adds census block-level geographic assignment that can populate these variables during dataset builds.
Test plan
🤖 Generated with Claude Code