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

[HUGE ISSUE] rewrite backend to use unique location identifiers #195

Open
3 tasks
jeffzyliu opened this issue May 10, 2023 · 1 comment
Open
3 tasks

[HUGE ISSUE] rewrite backend to use unique location identifiers #195

jeffzyliu opened this issue May 10, 2023 · 1 comment

Comments

@jeffzyliu
Copy link
Member

Description

Big issue--RD spelling is constantly out of sync. Solution--have RD unique identifiers.
Applies somewhat to county too with FIPS--this makes things more robust, and enables functionality such as multi-state-selections.

To do this, schemas need to change, and also indices. Instead of year state location, maybe year uniqueID? or year state uniqueID? not super clear honestly.

Frontend will need some rewriting to be compatible with database indexing changes etc, but it will make mapbox much cleaner and not buggy.

Finally the DBs will need to be re-seeded from scratch, which will take a lot of data cleaning to do for pre-2021 summarized county/rd data as well as cleaning county and RD spots to agree with the unique identifiers.

Type of Issue

  • New feature
  • Bug fix
  • Documentation update
@jeffzyliu
Copy link
Member Author

reconnect frontend to use the most recent mapbox tileset after this is done, because that tileset is going to need the RD identifiers

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

1 participant