{"action":"created","issue":{"url":"https://api.github.com/repos/cgeo/cgeo/issues/5338","labels_url":"https://api.github.com/repos/cgeo/cgeo/issues/5338/labels{/name}","comments_url":"https://api.github.com/repos/cgeo/cgeo/issues/5338/comments","events_url":"https://api.github.com/repos/cgeo/cgeo/issues/5338/events","html_url":"https://github.com/cgeo/cgeo/issues/5338","id":123972892,"number":5338,"title":"Allow switching off coord parsing from personal note","user":{"login":"Lineflyer","id":949669,"avatar_url":"https://avatars.githubusercontent.com/u/949669?v=3","gravatar_id":"","url":"https://api.github.com/users/Lineflyer","html_url":"https://github.com/Lineflyer","followers_url":"https://api.github.com/users/Lineflyer/followers","following_url":"https://api.github.com/users/Lineflyer/following{/other_user}","gists_url":"https://api.github.com/users/Lineflyer/gists{/gist_id}","starred_url":"https://api.github.com/users/Lineflyer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Lineflyer/subscriptions","organizations_url":"https://api.github.com/users/Lineflyer/orgs","repos_url":"https://api.github.com/users/Lineflyer/repos","events_url":"https://api.github.com/users/Lineflyer/events{/privacy}","received_events_url":"https://api.github.com/users/Lineflyer/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/cgeo/cgeo/labels/Bug","name":"Bug","color":"e10c02"},{"url":"https://api.github.com/repos/cgeo/cgeo/labels/Feature%20Request","name":"Feature Request","color":"02e10c"},{"url":"https://api.github.com/repos/cgeo/cgeo/labels/Feedback","name":"Feedback","color":"FAB028"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-12-27T11:10:19Z","updated_at":"2015-12-28T09:42:29Z","closed_at":null,"body":"..or improve it to make it more reliable.\r\n\r\nSeveral users contact us regularly having problems with strange waypoints automatically created by parsing of the personal note. There seem to be cases, where we parse nonsense.\r\n\r\nOne example I received today:\r\nPersonal note content:\r\n```\r\n   A=6 B=0 C=5 D=4 E=13\r\n\r\n   N 48° 53.(A*C*E)+194   E 009° 11.((D*71)-0)-1\r\n   N 48° 53.(6*5*13)+194  E 009° 11.((4*71)-0)-1\r\n   N 48° 53.(390)+194     E 009° 11.((284)-0)-1\r\n   N 48° 53.584           E 009° 11.283\r\n```\r\nc:geo creates the following waypoint as parsing result:\r\n```\r\nN 48° 53,000  E 006° 00,000\r\n```\r\n\r\nThis means users might see a lot of incorrect waypoints on their map without a possibility to permanentely remove them.\r\n\r\nSo I suggest to either improve the parsing or add an option to disable it in general so that affected users have a solution."},"comment":{"url":"https://api.github.com/repos/cgeo/cgeo/issues/comments/167527234","html_url":"https://github.com/cgeo/cgeo/issues/5338#issuecomment-167527234","issue_url":"https://api.github.com/repos/cgeo/cgeo/issues/5338","id":167527234,"user":{"login":"samueltardieu","id":44656,"avatar_url":"https://avatars.githubusercontent.com/u/44656?v=3","gravatar_id":"","url":"https://api.github.com/users/samueltardieu","html_url":"https://github.com/samueltardieu","followers_url":"https://api.github.com/users/samueltardieu/followers","following_url":"https://api.github.com/users/samueltardieu/following{/other_user}","gists_url":"https://api.github.com/users/samueltardieu/gists{/gist_id}","starred_url":"https://api.github.com/users/samueltardieu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/samueltardieu/subscriptions","organizations_url":"https://api.github.com/users/samueltardieu/orgs","repos_url":"https://api.github.com/users/samueltardieu/repos","events_url":"https://api.github.com/users/samueltardieu/events{/privacy}","received_events_url":"https://api.github.com/users/samueltardieu/received_events","type":"User","site_admin":false},"created_at":"2015-12-28T09:42:29Z","updated_at":"2015-12-28T09:42:29Z","body":"I also think a \"parse waypoints from note\" button would give the user more flexibility. The user is going to use cgeo anyway to find the cache, and having them in control of the waypoints parsing also lets them check that everything went fine. A keyword would need to be cgeo-specific; if every geocaching application did this, the user would have to include all the keywords in the description instead of pressing a button in the one application they are eventually using to find the cache."}}