{"action":"created","issue":{"url":"https://api.github.com/repos/mhkeller/indian-ocean/issues/18","labels_url":"https://api.github.com/repos/mhkeller/indian-ocean/issues/18/labels{/name}","comments_url":"https://api.github.com/repos/mhkeller/indian-ocean/issues/18/comments","events_url":"https://api.github.com/repos/mhkeller/indian-ocean/issues/18/events","html_url":"https://github.com/mhkeller/indian-ocean/issues/18","id":92690156,"number":18,"title":"Support geocsv","user":{"login":"ebrelsford","id":375002,"avatar_url":"https://avatars.githubusercontent.com/u/375002?v=3","gravatar_id":"","url":"https://api.github.com/users/ebrelsford","html_url":"https://github.com/ebrelsford","followers_url":"https://api.github.com/users/ebrelsford/followers","following_url":"https://api.github.com/users/ebrelsford/following{/other_user}","gists_url":"https://api.github.com/users/ebrelsford/gists{/gist_id}","starred_url":"https://api.github.com/users/ebrelsford/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ebrelsford/subscriptions","organizations_url":"https://api.github.com/users/ebrelsford/orgs","repos_url":"https://api.github.com/users/ebrelsford/repos","events_url":"https://api.github.com/users/ebrelsford/events{/privacy}","received_events_url":"https://api.github.com/users/ebrelsford/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-07-02T17:28:56Z","updated_at":"2015-07-02T17:37:28Z","closed_at":null,"body":"I've started work on this in a branch (5ac1a669). The idea is that we can detect lat/lng columns in delimited text files and return GeoJSON objects rather than plain old JSON objects. This should work fine for `psv` and `tsv`, too.\r\n\r\nThoughts? My goal is to be able to plop just about anything into `indian-ocean` and get something useful to import into [tablespoon-desktop](https://github.com/ebrelsford/tablespoon-desktop), so forcing GeoJSON here makes sense to me. But I understand if it's crossing a line for you."},"comment":{"url":"https://api.github.com/repos/mhkeller/indian-ocean/issues/comments/118104143","html_url":"https://github.com/mhkeller/indian-ocean/issues/18#issuecomment-118104143","issue_url":"https://api.github.com/repos/mhkeller/indian-ocean/issues/18","id":118104143,"user":{"login":"mhkeller","id":498744,"avatar_url":"https://avatars.githubusercontent.com/u/498744?v=3","gravatar_id":"","url":"https://api.github.com/users/mhkeller","html_url":"https://github.com/mhkeller","followers_url":"https://api.github.com/users/mhkeller/followers","following_url":"https://api.github.com/users/mhkeller/following{/other_user}","gists_url":"https://api.github.com/users/mhkeller/gists{/gist_id}","starred_url":"https://api.github.com/users/mhkeller/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mhkeller/subscriptions","organizations_url":"https://api.github.com/users/mhkeller/orgs","repos_url":"https://api.github.com/users/mhkeller/repos","events_url":"https://api.github.com/users/mhkeller/events{/privacy}","received_events_url":"https://api.github.com/users/mhkeller/received_events","type":"User","site_admin":false},"created_at":"2015-07-02T17:37:28Z","updated_at":"2015-07-02T17:37:28Z","body":"I think adding it to `readCsv` is a little tricky since then there isn't a way to read in a csv that has lat/lng like column headers the normal way. It would make most sense to have a `readGeoCsv` function that attempts to read in the file and throws an error if it isn't valid geocsv. \r\n\r\nFor `readData` it would use `readCsv` if the file ends in `.csv` and `readGeoCsv` if it ends in `.geocsv` or whatever the convention is.\r\n\r\nThat way if you want to explicitly load a csv as geojson you have a function for it and your csv loading can be normal as it is."}}