-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Jurisdiction" - unique ID #70
Comments
I would recommend to use the census id. For OpenPermit which schema is compliant with BLDS we specify census id, but I believe BLDS has left it open. |
@adamajm That's a good question. The field is not required, and there is also an optional That said, this should probably be an item for discussion at some point |
We're currently using it to differentiate between county jurisdictions (Douglas County, Town of Parker, etc.) when looking to combine data from separate government entities. We could conceivably switch to census id, however. |
@mmartin78 where are you obtaining your list of census jurisdiction ids? FIPS codes work for counties and states, but AFAIK not for cities. |
@mmartin78 thanks for the link. Is there a shapefile with polygon boundaries that accompanies this list? |
Sorry if this is covered somewhere and I missed it, I'm moving our City of Raleigh data to this standard and wondering if you are using a national database (census?) for unique identifiers for city/county/etc jurisdictions, or are you just using the name = "City of Raleigh"?
The text was updated successfully, but these errors were encountered: