Closed saylorsd closed 8 years ago
Lol OK
Looks to still be UTF-8-BOM or other encoding.
Yeah, on that note, I did a quick and dirty read of the first couple bytes on new one and it starts with 0xef
, 0xbb
and 0xbf
, so I think it is UTF-8 BOM
You can test that by trying to open the file in python with the encoding
utf-8-sig
On Jan 27, 2016 10:59 AM, "Steven Saylor" notifications@github.com wrote:
Yeah, on that note, I did a quick and dirty read of the first couple bytes on new one and it starts with 0xef, 0xbb and 0xbf, so I think it is UTF-8 BOM https://en.wikipedia.org/wiki/Byte_order_mark#UTF-8
— Reply to this email directly or view it on GitHub https://github.com/UCSUR-Pitt/wprdc-etl/pull/33#issuecomment-175744881.
Good to know. Thanks!
Steven Saylor
412-918-9630
From: Ben Smithgall [mailto:notifications@github.com] Sent: Wednesday, January 27, 2016 12:01 PM To: UCSUR-Pitt/wprdc-etl wprdc-etl@noreply.github.com Cc: Saylor, Steven David steven.saylor@pitt.edu Subject: Re: [wprdc-etl] fixed pli_violations mock data (#33)
You can test that by trying to open the file in python with the encoding
utf-8-sig
On Jan 27, 2016 10:59 AM, "Steven Saylor" notifications@github.com<mailto:notifications@github.com> wrote:
Yeah, on that note, I did a quick and dirty read of the first couple bytes on new one and it starts with 0xef, 0xbb and 0xbf, so I think it is UTF-8 BOM https://en.wikipedia.org/wiki/Byte_order_mark#UTF-8
— Reply to this email directly or view it on GitHub https://github.com/UCSUR-Pitt/wprdc-etl/pull/33#issuecomment-175744881.
— Reply to this email directly or view it on GitHubhttps://github.com/UCSUR-Pitt/wprdc-etl/pull/33#issuecomment-175746301.
Current PLI data taken directly from http://pittsburghpa.gov/pli/files/vet/pliExport.csv.
Don't ask me how, or why, but apparently it's now comma delimited.