You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Washington has a diversity of results in varying formats and data structure, especially at the precinct level.
However, through 2007, the results are from the same database dump and have a consistent format. Following that there are consistently county-level results available in CSV. Starting in 2012, there are precinct-level CSV files available.
When implementing the loader, get the 2000-2007 results working first, then county/precinct-level CSV. Excel/PDF precinct level data should be the last priority.
The text was updated successfully, but these errors were encountered:
I ran into this today with my loader: most of Washington's CSV files for the counties don't have any relevant information. Since openstates doesn't really want "SCHOOL DISTRICT 128 - LAMONT Position 5", the loader ends up ignoring like 2/3 of all the files.
Update the Washington loader to use _xls_file_path property of
BaseDatasource instead of the old, poorly named _xls_file_handle
method. The Datasource API was changed in
5870dd6
Addresses #149
Add comment specifying that the CSVs are missing and the Excel
files are hard to deal with. Order files by election, in
ascending order, for easier future review.
Addresses #149
Washington has a diversity of results in varying formats and data structure, especially at the precinct level.
However, through 2007, the results are from the same database dump and have a consistent format. Following that there are consistently county-level results available in CSV. Starting in 2012, there are precinct-level CSV files available.
When implementing the loader, get the 2000-2007 results working first, then county/precinct-level CSV. Excel/PDF precinct level data should be the last priority.
The text was updated successfully, but these errors were encountered: