"Maps Not The Same" Warning

Falagar -- In the older thread about the new features of 4.0.1, the bug of getting an incorrect warning about maps not being the same between a device and BC was discussed:

=======================
Originally Posted by FALAGAR
Yes, that is exactly why. BaseCamp doesn't read maps that were created by MapInstall. If BaseCamp can read the map from the SD card, then there should be no warning.
You can ignore the warning if you are sure you have the correct map installed.
---------------------
Thanks, Falagar. I can surely respond "no" to recalc each time I send to device no problem. But installing maps on the SD card is quite common practice now on Zumos since they don't fit in memory, and Zumo recognizes main and supplamental maps seamlessly, so it does seem BC should as well, after all the warning is factually incorrect. Could this be corrected in a future release? TIA.
=======================

There continues to be discussion about this warning over on the Zumo forum since nowadays it is common to install the maps, which are now too large for the internal memory, on the sd card. It leads to unnecessary concerns about maps not being installed correctly, re-installing, etc. Can you give us some encouragement that this will be fixed soon? Surely BC should recognize supplamental maps when doing this route-transfer check. Thanks!
  • Former Member
    0 Former Member over 12 years ago
    Thanks for bringing this back to our attention.

    We'll see what we can do.
  • Thanks much, Falagar. If I could suggest, I would treat this a high priority, as it is causing people unnecessary concern. I would go so far as to suggest that if it can't be fixed in 4.2, it should be disabled for now until it can be. I think a false warning is worse than none, after all we got along without such warnings fine for a long time, and most users have maps synched anyway, I think.

    If it helps in diagnosis, I note that only routes with added via points (shaping points) cause the warning. I just sent 7 routes to my Zumo, 6 had only waypoints for start and end, one had 1 via point. When the warning came up and I clicked "more info", only the one with a via point was listed as using different maps between BC and the device. All my 2013.4 mapset is in gmapsupp.img on the sd card, and 2013.4 is also on my computer for BC use.
  • Former Member
    0 Former Member over 12 years ago
    It leads to unnecessary concerns about maps not being installed correctly, re-installing, etc.

    Out of curiosity how do these concerns come about?

    To my knowledge all Garmin models allow you to determine what maps are loaded. BaseCamp also shows you what maps are in use.

    So is the problem ignorance or something else?
  • Perhaps you haven't encountered the error message. The background as I understand it is that with BC v4, Garmin introduced a new check that it does when sending routes to a device, it checks to see if the maps on the device are the same version as those that were used to create the routes in BC. If they are, no error message. But if they aren't, an error message comes up: . The problem is that the way the check routine was written, it does not correctly recognize maps on the sd card, which is common these days, so even if your maps on the device match exactly the ones on your computer, it can still give this warning. Even though the warning acknowledges that it doesn't recognize some supplemental maps, it is still not clear to everyone and when the warning is seen for the first time, it is disconcerting. (See Zumo forum http://www.zumoforums.com/index.php?topic=16368.0 for an example of the discussion.)

    So, ignorance? Yes, I guess, but the warning is factually in error and could be corrected so it doesn't appear when the map versions do in fact match. At least that's my thought.
  • Former Member
    0 Former Member over 12 years ago
    Ok. Thanks for clarifying. The issue is an erroneous message.