Mac and Zumo - Same Maps - Zumo has to recalculate on transfer

Read through this thread

https://forums.garmin.com/showthread.php?142138-Garmi-CSR-is-recommending-Zumo-550-66X-users-go-back-to-MapSource&p=399376#post399376

Thanks for the reply - not too useful though.

The thread you provide suggests that I should use MapSource. MapSource does not appear to be available for Mac OS X however.

Furthermore, there doesn't appear to be much development being done on MapSource. The most recent version is dated Oct 25, 2010.

And Basecamp has been working fine for me ever since I have owned the Zumo 660, and the issue I mentioned above has only appeared since I updated both Mac and Zumo to the newest Australian maps.

I understand your issues and my thought was the thread might explain why it was happening, there does appear to be issues with certain Zumos and Basecamp, exactly what they are I can't say as I don't have a Zumo. I also understand Mapsource can be made to run on a mac using various 3rd party programs and I know some do run Mapsource on macs, this is just one website that explains how Win can be made to run on a mac http://www.howtogeek.com/187359/5-ways-to-run-windows-software-on-a-mac/

However I agree from what you say that that may not be the issue in your case. Note that since you've updated your maps it's common that routes may need to be recalculated, since certain roads may be different from ones on earlier map versions. In your case I'd try recalculating them in Basecamp using the new map then send them again to your Zumo, having deleted the previously loaded routes on your Zumo. See if that now works as before.

Many thanks, SUSSAMB.

I'll try the measures you outline in your second paragraph. I did have a few routes sitting in Basecamp in preparation for a long trip in a few days. I'll delete them and rebuild them, clear out the Zumo too, and try to transfer them again. I'll report back in a day or two.

I'm not prepared to go to the lengths of installing Windows software on my Mac, though - I know how to do it, but I don't want to.

George,

This happens with most every map update. Over the years I've learned to 1) do a master reset on the 660 after the update and then run through the checklist of my prefs and settings, 2) Recalc each route in BC and then save it as a GPX file to the SD card in my zumo, 3) allow the route to recalc when I import on the zumo and check to make sure it hasn't been butchered, 4) set the zumo to prompt before doing a recalc and while riding decide if I want it to or not (usually not).

One way to sandbag against recalc butchery is to use enough shaping points that your intended route can survive a recalc.

I realize all this is a PITA, which is why I sometimes skip map updates -- the hassle of doing all this 4 times a year is often not worth the benefit of updating IMHO.

-dan

This goes back aways, but in the old days, the real map names differed on some devices from the names humans used to refer to them, e.g. the 378 device vs the 376. Perhaps something similar is happening here where the internal map name installed and used on the Zumo is different than the internal map name used and installed on the computer but we humans call them both NA 2015.2 or whatever.

Perhaps this problem could be avoided by keeping the Zumo connected during the trip planning and doing your planning using the maps contained in the Zumo. Its a PITA but it my also work if you followed the procedure of copying the Zumo internals onto an SD card to create a fake Zumo to plan on.

Many thanks to everyone for their assistance.
I decided I'd try Killtimer's method and change the Zumo 660 map name to match the Basecamp name using JaVaWa: he's right - there is an extra 0 in the Zumo map name.
That fixed the problem.