Skip to content
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

Integrate Opencivicdata identifiers #56

Open
showerst opened this issue Mar 7, 2017 · 14 comments
Open

Integrate Opencivicdata identifiers #56

showerst opened this issue Mar 7, 2017 · 14 comments

Comments

@showerst
Copy link

showerst commented Mar 7, 2017

Understanding this is a massive lift, it would be really cool if you could add OpenCivicData identifiers to the metadata where possible.

I know openelections uses them, so maybe it can be integrated into your workflow somehow.

@nvkelso
Copy link
Owner

nvkelso commented Mar 8, 2017 via email

@migurski
Copy link
Collaborator

I'm also interesting to know more about OCD identifiers. Who issues them, and how are they used?

@showerst
Copy link
Author

OCD's division IDs are an attempt at a common standard for identifying political divisions.

The nice thing about it is that there's some uptake from a variety of projects; Google's Civic information API, Open Elections, and the OpenCivicData Legislative Scrapers.

The value here would be being able to cross reference these with all their data without writing translation layers. I'm not actually involved in the OCD Division IDs other than as a user, but the repo is being run by a bunch of known characters in the civic data world.

If everything in this project will likely have a FIPS code it's less of an issue since those are well standardized, but if you're looking at other levels of division it would be a good standard to pick. I'll ask @jamesturk if there's an easy FIPS->OCD mapping somewhere, and either PR or at least link it so you can consider it.

@jamesturk
Copy link

In addition to the uses mentioned above (Google clearly being the biggest force driving adoption) I'm told they are now used in some company's voterfiles as well, driven by their use in the Voting Information Project: https://votinginfoproject.org/

At yesterday's Google-hosted gathering for people working on this data I was actually surprised to see how ubiquitous they'd become among people working w/ election geographies.

FIPS codes are definitely good for state & county, but if you want to have identifiers to link to other data at a level beneath that (SLDL, SLDU, precinct, school board, etc.) OCD Division IDs are probably the way to go. Other IDs you'll find (Census geoid, etc.) aren't available across all data sets and aren't stable.

If it'll be helpful, a FIPS mapping would be a good idea and a pretty easy lift from OCD's end.

@migurski
Copy link
Collaborator

Thanks James! Do they exist for precincts, and is such a list gettable someplace?

@jamesturk
Copy link

https://github.com/opencivicdata/ocd-division-ids/tree/master/identifiers/country-us there are precinct IDs but they're at ~2 years old right now. it looks like Aaron Strauss and Mike Jensen were maintaining them

@migurski
Copy link
Collaborator

Thanks! I don’t see a place in the identifiers for a year. Since districts and precincts may change from year to year, how do OCD identifiers track that kind of change?

@jamesturk
Copy link

jamesturk commented Mar 15, 2017 via email

@migurski
Copy link
Collaborator

Thanks for the clarification, James. I’d like to push on that a little: in the case of legislative districts and voting precincts, the meanings can change over time. Today’s “5th District” is only the same as yesterday’s in the sense that it’s the fifth item on a list. OCD identifiers would be helpful here if they offered some promise of uniqueness and stability, rather than restating other parts of a unit’s name. Is this a situation you’ve encountered with OCD before?

@jamesturk
Copy link

jamesturk commented Mar 16, 2017 via email

@migurski
Copy link
Collaborator

Sure, yeah. If you look at Florida’s 5th, it’s changed substantially in the past year. The pre-2016 and post-2016 areas it covers are almost disjoint, so there’s not really a meaningful way for a single OCD ID to point to them both.

Florida 5 now looks like this:

Previously, it looked like this:

Conversely, Barbara Lee has been my representative for almost 20 years, but during that time her district has been the 9th and later the 13th district of California.

@jamesturk
Copy link

jamesturk commented Mar 17, 2017 via email

@migurski
Copy link
Collaborator

That’s helpful clarification, thank you. OCD seems a bit less helpful if it doesn't deal with uniqueness, but it sounds like it might still help with external concordances as a long as a user understands that the same OCD ID may or may not identify the same entity across time.

@migurski
Copy link
Collaborator

migurski commented Mar 18, 2017

Okay, followup question. http://editor.opencivicdata.org/geo/select/ is down, so what would be a correct pattern for a precinct like we're storing here?

ocd-division/country:us/state:{postal-abbrev}/county:{name}/precinct:{?}

They’re also variously called "wards" and confusingly "districts" in other contexts, and the names can be complex, e.g. "Town Of Brighton Ward 1" for an example in Wisconsin:

ocd-division/country:us/state:wi/county:kenosha/precinct:Town Of Brighton Ward 1

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

No branches or pull requests

4 participants