Miriam at Solasdesign has been doing a series of blog posts about the process of updating erroneous underlying map data from TeleAtlas and Navteq. Miriam’s client had a business on a street in Hayward, Wisconsin that was not shown in Google Maps, MapQuest, Yahoo or MSN. Currently Navteq provides map data to MapQuest, Yahoo and MSN while TeleAtlas provides it to Google Maps.
Today she posted about an actual phone conversation with Mapquest where they clarified the timeframe for NavTeq to get the underlying data fixed:
On a quarterly basis, Navteq sends out drivers (yes, actual drivers in cars) to problem areas that have been reported and they can then update their data with the correct information the drivers collect.
The not-so-great news is that this a long queue process and by the time the data gets corrected by NavTeq (for our client’s town this will be in Navteq’s Jan-March 1st quarter of the year, based upon the time we reported the error), and the corrected data gets sent out to entities like MapQuest, MSN or Yahoo! who are using Navteq data, we would be looking at resolution coming no earlier than May-June of 2009. That’s a long time to wait, but at least we’ve been given a goal to look forward to. I can’t overstate the value of that.
Google switched to using TeleAtlas in a mid September timeframe. The reports of serious underlying map data problems have poured into Google Groups since that time. Miriam first reported this mapping problem to Google shortly after October 18th. How long will it take for the corrections to wind their way into Google Maps?
In general, given that the amount of missing Teleatlas maps data is significant and the high visibility of they have received from their inclusion in Maps causing increased reports, it would be likely to assume that the time to typically fix Google Maps/Teleatlas map data problems could be significantly longer than the 7 to 10 months stated for Navteq if TeleAtlas were using the standard drive and compile strategy.
However, yesterday, TeleAtlas announced a program of broad based integration of community edits into their map data update strategy. I will be reporting on this announcement latHow long does it take to fix an map data error? by Mike Blumenthal