While we’re all jumping on the band wagon of pointing out that iOS6 Maps having bad maps (it does by the way, truly awful maps), let’s not forget that no body is perfect…
Not the first issue that I’ve found on Google Maps, let’s not forget what I found on a TomTom satnav a while back, Google AND Apple were based on Telemaps which meant that the same issue crept onto Google Maps too. Thankfully, TomTom got in touch on that occasion and fixed the issue quickly.
Remember this photo that I took? Well after receiving over a thousand hits on Flickr I received a comment posted by TomTom themselves stating that after seeing the photo, which I geotagged on Flickr to show where it was taken, they have now corrected the route along with some cheeky/light hearted advice on how people can submit changes to be made on their mapping service.
Hi Andy – we spotted your photo on FlickR, and wanted to let you know that we have corrected this on our maps, and it will be available in new map releases. Thanks for bringing it to our attention! It’s worth adding, that we always appreciate feedback from our users, and the more conventional (!) route for logging map errors is through this link: mapinsight.teleatlas.com/mapfeedback/index.php Come and see us on www.facebook.com/TomTom ;-)
You may also recall that I showed that Google Maps displayed the same error while Yahoo Maps did not. Well it turns out that Google receives its data from TeleAtlas, which as it would happen, is owned by TomTom. Therefore I expect the same correction that TomTom has made will appear on Google Maps thus helping not just owners of TomTom devices but also those using GPS devices that rely on Google Maps.
It’s good to know that TomTom provide a system for feedback and I’m sure I may well submit more corrections in the future.