Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > aus.computers > #50242
| From | "Rod Speed" <rod.speed.aaa@gmail.com> |
|---|---|
| Newsgroups | aus.computers, comp.mobile.android, misc.phone.mobile.iphone |
| Subject | Google Maps updates, fark |
| Date | 2016-01-14 02:55 +1100 |
| Message-ID | <dfnaauF47beU1@mid.individual.net> (permalink) |
Cross-posted to 3 groups.
Previously I have seen google maps update some errors on their maps so quickly that I have regretted not checking the maps hourly to see just how quickly the change was done. This time, with a VERY basic error on their part, its taken the best part of 3 fucking months to actually get the update made. The problem was that one road, Snaidero Rd, somehow managed to get changed from that correct spelling to Snaldero Rd, presumably either some stupid keyed it in wrong or and someone stupidly used an OCR system to update it etc. I know that the person who the road is named after didn't request a spelling change because I know the family personally and know that it was originally spelt correctly. Reported it at least 3 times, the last time with a rather snide remark about why it was taking so long for someone to fix it. Still took at least 2 months from the last notification to get the change made. Not clear why it took so long this time when I have had at least 4 other reported errors fixed very quickly indeed in the past. Maybe this one happened as a result of where they get the bulk of their data from making the original error and it took that long to get them to check that they had made an error or something, even tho google maps obviously had the original correct spelling in their own system for years. Maybe they assumed that the change was correct and needed to get whoever made the change to confirm that it wasn't or something. This is in contrast to Apple maps which has never acknowledged any error at all and has never fixed any of them. And still has this error, so its not as if the main data supplier fixed the problem themselves unless its taking longer for Apple to get that change thru their system. Unlikely its that tho because google maps did tell me when they had fixed the error.
Back to aus.computers | Previous | Next — Next in thread | Find similar
Google Maps updates, fark "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-01-14 02:55 +1100
Re: Google Maps updates, fark Chris in Makati <mail@nospam.com> - 2016-01-14 08:17 +0800
Re: Google Maps updates, fark felix <me@nothere.invalid> - 2016-01-14 11:25 +1100
Re: Google Maps updates, fark "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-01-14 14:22 +1100
Re: Google Maps updates, fark "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-01-14 14:18 +1100
Re: Google Maps updates, fark "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-01-14 14:23 +1100
Re: Google Maps updates, fark Anssi Saari <as@sci.fi> - 2016-01-14 09:40 +0200
Re: Google Maps updates, fark "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-01-14 19:28 +1100
csiph-web