Priority for 2022: Incorporate New Vote Data Source
Past due by about 3 years
25% complete
Use Legiscan to import vote data.
Previously used OpenStates.org, which is now defunct for Texas.
- downloaded JSON files from Legiscan, because the Legiscan API sucks.
- https://legiscan.com/datasets
- Click on "data sets" in top menu bar
- Then go to Texas
- You can download the entire 86th session in a JSON file. It contains bills people and votes. (There may b…
Use Legiscan to import vote data.
Previously used OpenStates.org, which is now defunct for Texas.
- downloaded JSON files from Legiscan, because the Legiscan API sucks.
- https://legiscan.com/datasets
- Click on "data sets" in top menu bar
- Then go to Texas
- You can download the entire 86th session in a JSON file. It contains bills people and votes. (There may be an ID problem with Jarvis Johnson from District 139. Otherwise, it's pretty bug-free.)
- As far as we know, it is accurate. You can spot-test accuracy (using the Legiscan Search box on the home page), and it seems to be accurately collecting all the actions of bills and correctly identifying the final votes.
**(They) tried to use the Legiscan API and it sucked. That's why they went the download route. Also, interestingly enough, the Legiscan IDs correspond with https://votesmart.org/ (which is another service that sucks).
Implement our own data gathering methods.
Purpose:
- Remove dependence on external sources.
- Improve accuracy and consistency.
- Allow for importing historical data.
- Allow importing from different sources.