BaseCamp flagging intersections on Zumo 66X

People riding MC like routes on twisty roads but don't like the Zumo display being cluttered with flags and the headset announcing route points not needed. We used to be able to prepare routes in MapSource with viapoints on intersections. That would prevent flags and announcements for the Zumo 66X and Zumo 550. With BaseCamp that does not seem to be possible anymore. We had a discussion on that on the Zumo Forum from where I quote:

quote ..

I noted the suggestion by Dave that it could be a problem with BaseCamp. I normally make and modify my routes in MapSource (taking advantage of snap-on to intersections) and then copy/paste the route to a list in the BaseCamp database from where I download whatever routes I want to the Zumo.

I made a test by downloading the route to the Zumo directly from MapSource bypassing BaseCamp entirely. Guess what - no flags except my one intentional waypoint.

It does appear that BaseCamp does some strange things to route points, both via and shaping, that cause flags to appear on routes in some random fashion on the Zumo 66X. I really like the folder/list structure of BaseCamp and would hate not being able to use it.

I plan on raising this concern also on the Garmin BaseCamp Forum.

.. unquote

I attach two screendumps, one with the route downloaded from BaseCamp, the other from MapSource. BaseCamp is V 4.1.2.

Please make BaseCamp consistently honor the intersection facility for non-announcements when downloading routes to the Zumo 66X/550. If BaseCamp would also allow the snap-on facility then I could drop MapSource entirely.
  • Put via points on intersections or roads with no address and then never move them?

    Yes, but that's not really an option when you want to reshape a route...
    An alternative is not to move the via points, but instead insert a new one and delete the incorrect via point. Snapping works when inserting via points.

    but are you really certain about the 550/660?

    Yes, I've tested it, and it works.

    Implement snap-on as for MapSource and review the subclass codes generated by BaseCamp?

    Both ofcourse, but the second one should be handled automatically when the first one is implemented properly.

    There are some other things that should be implemented in BaseCamp:
    1. Adjusting the subclass codes of via points to the current map when importing or recalculating a route (both weren't implemented in MapSource either).
    2. Relocating via points to the nearest road segment when recalculating. Why: there are always some (slight) differences in the geometry of roads; even between subsequent versions of CN maps (or even between the NTU and NT version of the same map). When you recalculate a route made on a different map this often results in tiny "spikes" where via points are positioned slightly off road. Those via points won't get a proper subclass code when #1 is implemented, and they cause some serious trouble on the zumo 350 (erratic instructions or even crashes).
    I've created a program to eliminate these spikes, but it would be preferable when BaseCamp handled this properly.
  • Thanks Javawa. I just need to clarify one thing from this discussion: By "non-alert" or "non-announcement" I understand that both the orange flags and the verbal announcements are eliminated for properly placed via points. Your understanding also?