Back in October of last year, I wrote this post where I said that I sent a correction request off to NAVTEQ to correct the name of a road in the New River Beach area of New Brunswick. They had incorrectly labeled “Haggerty’s Cove Rd” as “Maggery’s Cove Rd”. I sent, as supporting proof, this photo, which doesn’t technically show the road name – but rather the area name. I didn’t have a photo showing the actual road sign so my hope was that they’d be ok with just seeing the name of the area and extrapolating from that. :)
I got an email on May 2nd stating that they have completed their investigation of my map report. Their resolution was:
Our Resolution Outcome is: Database Updated – Naming
Details: The naming for Haggerty’s Cove Rd in New River Beach, NB, has been updated in the database.
NAVTEQ’s website, under their Support FAQ states the following, “At NAVTEQ, we make every effort to resolve most issues within 90 days of the date submitted.” They go on to say that, “We prioritize map reports by the nature of the request.” This makes sense of course, and I certainly wouldn’t consider my request high priority. However, given how easy a change it was, and the supporting evidence I gave for the change, I wouldn’t have expected it to take too long. In my particular case, it took 193 days for me to get an email confirming the update. Even if you take out the 54 days worth of weekends then it still took 139 days – a long ways off the estimated 90 days. Not that I’m complaining, I’m actually impressed that I got a response at all to be honest. It still hasn’t shown up on the maps on their website yet – despite the fact that the ticket says their database has been updated, and I think it’ll be a long while before I can check Google Maps and see the correct name there.
I’ve got mixed feelings on this one I guess. The change has (supposedly) been made, but it took a LONG time.

Nice work! How many people can say they corrected the map.
It would be interesting to learn how it could take that long. I can’t imagine anyone having a queue that long. My guess is that it went stale — lost in process — and ether a duplicate report revived it, or a clean up activity. I’m a QA geek, so I find this interesting.