Will Mapshares carry over to new map?

[Harry6]

This has probably come up before, but ...

I have made quite a few mapshare corrections, both shared and personal.

Will both the shared and personal mapshares carry over to a new edition map?

Thanks,
Harry

 

[dhn]

No, you have to start all over.

 

[canderson]

No, you have to start all over.

Um.. a person CAN save the requisite files and carry over their own mapshare changes - just the same way you can "share" your personal changes between two units. We've had that done before.

 

[dhn]

Can you list the files again, please?

Are you sure it works 100% of the time, canderson? I thought I've seen posts where some users copied the requisite files but their corrections were not reflected on the new map??

Could be wrong, of course.........

 

[canderson]

Can you list the files again, please?

Are you sure it works 100% of the time, canderson? I thought I've seen posts where some users copied the requisite files but their corrections were not reflected on the new map??

Could be wrong, of course.........

Dunno about 100% - just worked the times I've suggested it. Last user had a pair of 340's and wanted to clone the changes to the 2nd unit. If I recall correctly (might have to do some thread searching if not)

From the map folder: mapuserpatch.dat, mapsettings.cfg
From the root: UserPatch.dat

Can't recall if mapsettings.cfg is actually required. Can't hurt - has other good stuff in it as well.

If I were the OP, I'd give this a try:

Back up the three files mentioned above BEFORE doing the map update.
Do the map update.
Back up those same three files after the update (someplace other than your original set of 3).
Copy your original 3 to your unit and see if your changes are intact after a reboot.
Worst case is it's a bust and you copy the new 3 back so that it looks like it did after the map update.

 

[Rick F.]

I saved those 3 files before upgrading to v860 map a few months ago and the speed limit corrections I made were there on the new map.

I seem to remember though that the 'mapsettings.cfg' file is being protected by HOME now... and also one of the others. But not the third one. I believe (but not sure) that the file in the 'root' directory was not saved during my last update. Sure doesn't hurt to back up these 3 files to be safe though and then restore them.

 

[canderson]

I seem to remember though that the 'mapsettings.cfg' file is being protected by HOME now...

Only appears to be the case for units with Navcore 9.XXX, and we don't have any idea yet what unit the OP has or what firmware. Can't hurt to be safe.

 

[Harry6]

I really appreciate the considerable expertise, and the willingness to share it, on this forum.

I have the xxl 540, and latest firmware, and will follow your instructions when I upgrade to the new map...

Thanks so much for your help.

Harry

 

[canderson]

I have the xxl 540, and latest firmware, and will follow your instructions when I upgrade to the new map...

Keep us posted on how it worked out for you. I've seen success on units with similar firmware. I know how frustrating it can be to get an area 'cleaned up' with changes, only to see them disappear when the new maps being sent don't include them.

 

[gatorguy]

If the mapshare changes carried over, how would conflicts between the new map data and old correcttions (road geometry changes, roads removed altogether, name change or even corrected, etc.) be resolved? Seems like it could create some unique issues.

 

[canderson]

If the mapshare changes carried over, how would conflicts between the new map data and old correcttions (road geometry changes, roads removed altogether, name change or even corrected, etc.) be resolved? Seems like it could create some unique issues.

For name changes, the saved information would continue to override the new map data. The more problematic issues of roads being moved are interesting. Since you can't save an "added" road in your personal changes, that never comes up as an issue. However, if a road were to disappear or be realigned, it would be interesting to see what the personal changes cause - one would assume the conflict would be where the personal change was to 'block' a non-existent road so as to make it unavailable, and the map change would be to make that road disappear altogether. Haven't yet run across a situation like that. The stupid roads persist from map to map even after I've blocked them in Mapshare. Until that time comes, I'm doing OK with my changes "sticking".

 

[Andy_P]

... how would conflicts between the new map data and old correcttions (road geometry changes, roads removed altogether, name change or even corrected, etc.) be resolved? Seems like it could create some unique issues.

I don't think your own corrections are "carried over" in that way.... for that very reason.

What people usually mean by "carried over to a new map" is that corrections that have been actually agreed and shared by TomTom are finally being ported over to a new map if they have not been properly corrected by the map makers already.
This never used to happen at all.

 

[gatorguy]

I didn't think they did, the reason for posting the probable reason why not. But there's apparently some confusion whether they do or not?

 

[Andy_P]

Sorry, I wasn't quoting you to disagree with you , but to agree!

 

[canderson]

I didn't think they did, the reason for posting the probable reason why not. But there's apparently some confusion whether they do or not?

No. I think we all agree that they are NOT retained through a map update. What we've been discussing are ways to get around that. You can fix up all the problems in your area just to have them all wiped out by the next map that comes along that (if you're REALLY lucky) might have just one of your changes in it - more likely none - leaving you to enter them all again. PITA. That's why we're experimenting with the files that contain the data.

 

[gatorguy]

OK, thanks Canderson. Understood.

 

[mvl]

When I've upgraded maps on app 9.x, I've found that updates that you share with Tomtom are not saved. And updates that you choose not to share are saved.

 

[canderson]

When I've upgraded maps on app 9.x, I've found that updates that you share with Tomtom are not saved. And updates that you choose not to share are saved.

Now there's an interesting new data point. I always "Share", hence I always have to carry over the files from one map update to another. Kind of a raw deal - certainly doesn't encourage users to share their updates, does it?