mvl
Moderator
- Joined
- Dec 19, 2008
- Messages
- 5,469
- Location
- Boston, MA, USA
- Country
- TomTom Model(s)
- Tomtom GO for Android
My buddy just got a one 130 and did LMG to map 825, so I took a look to see if any of my map 815 errors were fixed. (I wrote them down preparing for the subscription service).
Disappointingly, only 2 of my 20 corrections made it in. But here's the weird thing: one of those changes (a road deletion) didn't make it yet onto teleatlas.com. So tomtom and teleatlas must still be running separate map databases (prior to the merger, tomtom said it does independent validation of vendor map changes).
Also, I've noticed that teleatlas.com (and google maps) has a few new introduced map errors in the Feb 09 update, that are within 0.1 miles of a similar correction I reported. Eg (I reported a blocked/dead end road, and an incorrect dead end appeared 0.1 miles away). Maybe tomtom got the coordinates wrong on a correction file. So far none of these errors made it onto map 825.
Anyone else notice something similar?
Disappointingly, only 2 of my 20 corrections made it in. But here's the weird thing: one of those changes (a road deletion) didn't make it yet onto teleatlas.com. So tomtom and teleatlas must still be running separate map databases (prior to the merger, tomtom said it does independent validation of vendor map changes).
Also, I've noticed that teleatlas.com (and google maps) has a few new introduced map errors in the Feb 09 update, that are within 0.1 miles of a similar correction I reported. Eg (I reported a blocked/dead end road, and an incorrect dead end appeared 0.1 miles away). Maybe tomtom got the coordinates wrong on a correction file. So far none of these errors made it onto map 825.
Anyone else notice something similar?