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
{{ message }}
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
It's easy enough to make that a CSV and clean that up and include in both projects, if that's your desire.
If you're going to change the output of one to match the other, you'd break stuff depending on it -- which can be fixed and hopefully would be detected in pre-election testing.
The text was updated successfully, but these errors were encountered:
On a related note, if'n y'all wanted to take that documentation over, I'd love you to be the canonical resource I'd link to from election-results-parser. =)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Some fields appear in JSON or CSV output but not the other.
Some data is formatted differently, such as "percents" going from 0 to 1 vs. 0 to 100.
I've got partial documentation started here:
https://github.com/PalmBeachPost/election-results-parser/commits/master/fielddescriptions.xlsx
It's easy enough to make that a CSV and clean that up and include in both projects, if that's your desire.
If you're going to change the output of one to match the other, you'd break stuff depending on it -- which can be fixed and hopefully would be detected in pre-election testing.
The text was updated successfully, but these errors were encountered: