{"action":"created","issue":{"url":"https://api.github.com/repos/openaddresses/openaddresses/issues/851","labels_url":"https://api.github.com/repos/openaddresses/openaddresses/issues/851/labels{/name}","comments_url":"https://api.github.com/repos/openaddresses/openaddresses/issues/851/comments","events_url":"https://api.github.com/repos/openaddresses/openaddresses/issues/851/events","html_url":"https://github.com/openaddresses/openaddresses/issues/851","id":53965062,"number":851,"title":"Korean source CSV files have an inconsistent number of columns","user":{"login":"NelsonMinar","id":382136,"avatar_url":"https://avatars.githubusercontent.com/u/382136?v=3","gravatar_id":"","url":"https://api.github.com/users/NelsonMinar","html_url":"https://github.com/NelsonMinar","followers_url":"https://api.github.com/users/NelsonMinar/followers","following_url":"https://api.github.com/users/NelsonMinar/following{/other_user}","gists_url":"https://api.github.com/users/NelsonMinar/gists{/gist_id}","starred_url":"https://api.github.com/users/NelsonMinar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/NelsonMinar/subscriptions","organizations_url":"https://api.github.com/users/NelsonMinar/orgs","repos_url":"https://api.github.com/users/NelsonMinar/repos","events_url":"https://api.github.com/users/NelsonMinar/events{/privacy}","received_events_url":"https://api.github.com/users/NelsonMinar/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-01-10T17:32:59Z","updated_at":"2015-01-10T17:39:19Z","closed_at":null,"body":"The `kr-seoul-*` files name CSV sources stored in our own S3 bucket, at URLs like http://s3.amazonaws.com/data.openaddresses.io/cache/kr-seoul-songpagu.zip\r\n\r\nThe CSV files stored there are not well-formed. They mostly have 12 columns per row, but occasionally a  row has 13 columns. Is this fixable in the data source?\r\n\r\nAn example source with this problem is kr-seoul-chongnogu. Here's 5 rows from it, the middle row has an extra column. Note that the source encoding is EUCKR.\r\n\r\n````\r\n서울특별시,종로구,명륜2가,4,0,창경궁로,265,0,아남아파트,102동,199967.6616,454036.4788\r\n서울특별시,종로구,명륜2가,4,0,창경궁로,265,0,아남아파트,103동,199970.6174,453969.5493\r\n서울특별시,종로구,명륜2가,4,0,창경궁로,265,0,아남아파트,경로당,관리사무실,199985.4176,453957.7999\r\n서울특별시,종로구,효제동,98,0,대학로,28,0,,D동,200272.9246,452712.8438\r\n서울특별시,종로구,효제동,98,0,대학로,28,0,,,200237.5673,452699.3256\r\n````\r\n\r\nHere's [a Python script](https://gist.github.com/NelsonMinar/f67a5900c9e81d2c111d) to help identify problem CSV files. A quick shell snippet to find 13 column rows:\r\n\r\n````\r\niconv -f EUCKR -t utf-8 < /tmp/korea/kr-seoul-chongnogu.csv | egrep '(.*,){12}'\r\n````"},"comment":{"url":"https://api.github.com/repos/openaddresses/openaddresses/issues/comments/69464248","html_url":"https://github.com/openaddresses/openaddresses/issues/851#issuecomment-69464248","issue_url":"https://api.github.com/repos/openaddresses/openaddresses/issues/851","id":69464248,"user":{"login":"NelsonMinar","id":382136,"avatar_url":"https://avatars.githubusercontent.com/u/382136?v=3","gravatar_id":"","url":"https://api.github.com/users/NelsonMinar","html_url":"https://github.com/NelsonMinar","followers_url":"https://api.github.com/users/NelsonMinar/followers","following_url":"https://api.github.com/users/NelsonMinar/following{/other_user}","gists_url":"https://api.github.com/users/NelsonMinar/gists{/gist_id}","starred_url":"https://api.github.com/users/NelsonMinar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/NelsonMinar/subscriptions","organizations_url":"https://api.github.com/users/NelsonMinar/orgs","repos_url":"https://api.github.com/users/NelsonMinar/repos","events_url":"https://api.github.com/users/NelsonMinar/events{/privacy}","received_events_url":"https://api.github.com/users/NelsonMinar/received_events","type":"User","site_admin":false},"created_at":"2015-01-10T17:39:19Z","updated_at":"2015-01-10T17:39:19Z","body":"It looks like it's the third-to-last column that's supicious. That's labelled \"상세건물명\" or \"DET_BD_NM\", which apparently is \"Details Building Name\". A good value for that is 102동, which means \"102 East\". A bad falue for that is \"경로당,관리사무실\", which Google Translate tells me means \"Per path, administration office\". I wonder if the source data just isn't quoted properly, that the comma is intended to be part of the address rather than a field separator?\r\n\r\nI'm just going off of Google Translate; it'd be nice to have someone with Korean language skills look at this."}}