-
Notifications
You must be signed in to change notification settings - Fork 29
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
Data table doesn't match field documentation #5
Comments
I think you can trust the order of the field descriptions and ignore length and data type. Note that the third column includes numbers 1 through 67 and there are 67 counties in PA [Ballotpedia]. Things seem to check out if you sniff around some of the other columns too. It looks like the table in the README is just copied from the communication provided by the PA Department of State. My hypotheses are either:
|
I'll ask PA about whether the record layout changed for 2016 files and will provide a response to this. |
Is this now resolved? |
We still need to do 2016, but this issue doesn't occur for 2018 general. |
The fields documented in the README don’t appear to match those in the 2016 General data file. Here are the first few documented fields:
And these are the first few lines:
The lengths and positions don’t match, and the file is missing a header row (as in other OE data sets) to disambiguate.
The text was updated successfully, but these errors were encountered: