rcv
rcv copied to clipboard
support iVotronic format
Sample files from George:
- https://www.dropbox.com/l/scl/AAC-5xAQsSJnaBLcoYuyEi-uR1_EZjbflGE (CVR in LST format, whatever that is)
- https://www.dropbox.com/l/scl/AADyOvAwkjNUB1Dxvj8eqQkcDO7LiXC-EsU (CVR in XLSX)
- https://www.dropbox.com/l/scl/AACzSzHBw-XB0jcy-w3LkBLw0-RUrfGnW28 (tabulation in XLSM)
LST format files from ES&S iVotronic are text files that contain all the CVR data, but they are not very helpfully formatted. Unfortunately, the .xlsx files of CVRs that George posted are just as ugly as the text LST files. Probably this is a case where we would create a stand alone file converter to read in the .LST file and spit out a clean CVR file. I don't think this is currently worth doing, since we aren't likely to get live iVotronic data anytime soon, so let's put this topic on ice until further notice.
@CalebKleppner: given your last comment, should we move this to the "v1.1 Future" milestone?
Yes, definitely v1.1 Future that issue, as with other data formats that we don't have good specs for (Dominion, Hart?). I'll have to look at variations on Dominion data, but I think they key places that use it are San Francisco and Alameda County (Oakland, Berkeley and San Leandro).
Caleb Kleppner MK Election Services, LLC 203-376-4080
On 1/2/2019 12:40 AM, Louis Eisenberg wrote:
@CalebKleppner https://github.com/CalebKleppner: given your last comment, should we move this to the "v1.1 Future" milestone?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/BrightSpots/rcv/issues/104#issuecomment-450790120, or mute the thread https://github.com/notifications/unsubscribe-auth/Anh6XDci-jcPLZLk7Kmx5ncjqKd-P6_hks5u_EZggaJpZM4VrsvL.
Is this still something we're going to want to do at some point?