open-data-standards / permitdata.org

:hammer: A website for the BLDS Data Specification
https://permitdata.org
39 stars 7 forks source link

"Jurisdiction" - unique ID #70

Open adamajm opened 9 years ago

adamajm commented 9 years ago

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"?

mmartin78 commented 9 years ago

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.

mheadd commented 8 years ago

@adamajm That's a good question. The field is not required, and there is also an optional Publisher field. There are several examples of jurisdictions publishing BLDS data without that field.

That said, this should probably be an item for discussion at some point

jwthomp1313 commented 8 years ago

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.

ARolek commented 7 years ago

@mmartin78 where are you obtaining your list of census jurisdiction ids? FIPS codes work for counties and states, but AFAIK not for cities.

mmartin78 commented 7 years ago

@ARolek Please see here: http://www2.census.gov/geo/docs/reference/codes/files/national_places.txt

ARolek commented 7 years ago

@mmartin78 thanks for the link. Is there a shapefile with polygon boundaries that accompanies this list?