Default shaping points not always hidden?

Former Member
Former Member
As a back roads motorcyclist, I generate lots of routes that use shaping points extensively. I'm using Basecamp 3.3.2.0 and a Zumo 665. One thing that mystifies me is how come the shaping points that I have inserted occasionally show up as flags on the route despite being marked as "do not report". One thing that seems guaranteed to make this happen is not quite getting the point right on the road, but I see it happen sometimes when the point is pretty clearly on the road. At an intersection even.

I create these shaping points by using the Select Tool to drag it to intersections by panning and zooming a lot. I try to zoom in pretty closely most of the time to get it right on the intersection, which is kind of a pain because sometimes it isn't dropped there even though the intersection name shows up right as the first thing in the popup balloon. On rare occasion there is just no intersection available along a road I want to take so I resort to just picking a random spot on the road and dropping it there.

When I am all done I hit Command-I to bring up the Via Points list then select all of them but the start and finish points and hit Command-K to turn them all into "Don't Alert on Arrival (shaping point)"s. Then I load it into my GPS and discover the route polluted with several visible waypoints.

POSSIBLY related to this, though I am not sure --when I start the GPS it claims that the routes were generated with a different map set. However this message mystifies me because both BaseCamp and the Zumo claim to be using the same map (seen as "City Navigator North America NT 2013.2" in BaseCamp, "CN North America NT 2013.20" in the Zumo). And if I zoom to the highest level on the GPS at a flagged waypoint I know is on an intersection, it looks like it is right on the intersection in the GPS too.

Two additional feature requests:

* Could there please be a way to make these dragged points be shaping points by default? If I wanted the GPS to alert me to a point , I'd make a waypoint. That's a far rarer case for me than wanting a shaping point from dragging, and so having to pull up Via Points list just to mark them all is a step that could be avoided.

* Could there please be a way to snap shaping points right to the intersection by default? It would save a LOT of effort of having to zoom in to make sure you're directly right on the spot. (Closely related, is there some way I am missing that you can actually click on the intersection name in the popup balloon while dragging the route? I seem to recall that in MapSource I could.)

Thank you for any insight into how I can resolve my issues.
  • The big clue is that your zumo thinks the vias were created in a previous map set. If that were true it would be the answer. I realize you're saying it's not, so the next step is to figure out why it's doing this.

    The only thing I can think of is to force the route to recalculate, both in BC and in the zumo, and see if that fixes the via "registration" with the map set in use.

    -dan
  • Former Member
    0 Former Member over 12 years ago
    Maybe its as simple as comparing 2012.2 to 2012.20 and finding them to be unequal
    Also, perhaps "City Navigator North America NT 2013.2" is unequal to "CN North America NT 2013.20"
    Or, maybe they use a different numbering system internally to identify their map products. In the past they have been known to have factory installed maps which were actually different than store bought versions with the same name.
  • Former Member
    0 Former Member over 12 years ago
    See, as far as I can tell they really are the same map. They were both installed on the same day via the Lifetime Map Updater. I've posted a question over the the Installing and Updating Maps forum asking about that, and whether it really does boil down to a string comparison gone wrong (and, by implication in my mind, one that only shows up at point versions that are multiples of 10).

    I have no reason to believe that the maps are actually different, but how can I compare them and not just the way their names are displayed? There isn't an obvious way (to me) of to compare the md5 of the map on the Zumo mounted as /Volumes/GARMIN with that of the files in my Application Support on the local hdd. On the GPS it's just one gmapsupp.img file but on the computer itself there are a lot of individual files under Library/Application Support/Garmin/Maps/City Navigator North America NT 2013.20.gmap/.
  • One way to test is to create a new route using ONLY the maps in your GPS. Use the pulldown menu in BaseCamp to select the GPS's map, not the one installed on your computer, and create a brand new test route using no old vias or waypoints.

    Also, for future reference, do NOT use Lifetime Updater; it is buggy and causes all kinds of problems. Use the other option via myGarmin.com -- the plain old Map Updater, which works reliably.

    -dan
  • Former Member
    0 Former Member over 12 years ago
    * Could there please be a way to snap shaping points right to the intersection by default? It would save a LOT of effort of having to zoom in to make sure you're directly right on the spot. (Closely related, is there some way I am missing that you can actually click on the intersection name in the popup balloon while dragging the route? I seem to recall that in MapSource I could.)

    I too would like to see this feature add like MS had it was a great feature.

    Thank You