Repository navigation
Filling in Missing Zoning GEOIDs - #147
Merged
Merged
Conversation
duaneatat
approved these changes
Oct 1, 2026
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
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.
This PR addresses the 132 missing GEOID districts in the raw zoning dataset. The fix lives in the
data_cleaning/clean_zoning.pyThe fixes:
3 districts had missing
GEOIDs ANDMunicipality_Name(Peru, Westmore, Newport Town)Municipality_Nameto match theDistrict_Name(they were the same) and attached the corresponding Censusgeoidsfrom thelake.RAW.vt_town_linestableMunicipalities outlined in issue 132 district records have no geographic identifier #116 had missing
GEOIDfeaturesgeoidsfrom thelake.RAW.vt_town_linestableUpdated the docs/datasets/zoning.md documentation to record the GEOID column fix
Closes #116