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

Clarify ReadMe on newest data location #22

Open
michaelblyons opened this issue Dec 7, 2018 · 2 comments
Open

Clarify ReadMe on newest data location #22

michaelblyons opened this issue Dec 7, 2018 · 2 comments

Comments

@michaelblyons
Copy link

In the ReadMe, it says

For example, GeoJSON for New York's 1st district can be found at:

https://theunitedstates.io/districts/cds/2012/NY-1/shape.geojson

The 2012 here refers to the year that these districts came into effect, and is the most current districts. "At Large" districts, where only 1 person represents an entire state or territory, are coded with a district number of 0 (e.g. WY-0 and PR-0).

I expected this to mean that a given year's folder only contained states whose district boundaries were changed in that year. The 2018 folder has only PA, but 2016 has everybody (not just VA, FL, and NC). Which way is intended? Either way, if the "and is the most current districts" line could be clarified to match the expectation, I think that would be good.


If the intention was to avoid data duplication in the repo, here's what I'd suggest: What are the odds that a special directory (now, current, etc.) could be created in cds that contained symlinks to the current map files? It would link to the 2012 districts for NY, to 2016 for FL, and (soon) to 2018 for PA. Then you could drop the states from 2016 who do not have changes and avoid adding everyone (again) to 2018.

@michaelblyons michaelblyons changed the title Clarify ReadMe Clarify ReadMe on newest data location Dec 7, 2018
@Andrew-Chen-Wang
Copy link

Andrew-Chen-Wang commented Apr 28, 2021

3 Years late but for anyone else who needs double clarification, OP is correct. 2018 is when Pennsylvania's Supreme Court forced PA legislative body to redraw the map due to illegal gerrymandering. Technically, we're supposed to only redraw every 10 years when the decade census comes out, but sometimes states redraw districts. Same can be said of #24

edit: if anyone needs one geojson file that has the most up to date cds data, visit: https://github.com/Andrew-Chen-Wang/district-autoupdate/blob/checking-if-geojson-worked/districts.geojson It's still using this repository's data!

@NickCrews
Copy link

Total drive by here: In general I would avoid anything that labels data with relative things like current. They inevitably get out of date. Instead, just label with the absolute years/dates the data is for, and then it is the client's responsibility to get the maximum/closest to the current year.

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

3 participants