Newbie basecamp question

Former Member
Former Member
I wonder whether someone can help. I have a Zumo 350lm. I have used basecamp to create a basic route with three way points. I transferred it to the 350lm and can see the waypoints in favourites and the route in Trips. So far, so good.

I have also tried converting a track to a route. In doing so I set the maximum number of via points to 10...(i also tried this with auto). However looking the route in basecamp it seems to be littered with little dots along the route ( I assume they are via points????). When I transferred this to the satnav it appears to have broken the route down into numerous sub-trips. Not ideal.

I have also tried importing a few GPX routes (down loaded from various websites) into basecamp and subsequently transferring them to the satnav. They too seem to be full of via points (??) and create multiple trips when transferred to the satnav.

What I'm I doing wrong?

Also when the sat Nav is connected to basecamp, why can't the routes on the sat be deleted via the PC?

Thanks. Jeremy
  • First, while you can send stuff from Basecamp to your Zumo you cannot delete anything on your Zumo from within Basecamp, you must do it on the Zumo itself.

    Second, your Zumo uses 'trips' not 'routes'. Sending any file with lots of vias will give the problem you've experienced.
  • Former Member
    0 Former Member
    SUSAMB is correct the 350LM implements "trips" and not "routes". You can tell because the specs page says

    routes: 100


    Other Zumo's (e.g. the 660LM and 665LM) implement real routes.

    Routes 20 (additional storage on microSD™ card)
  • Former Member
    0 Former Member
    your Zumo uses 'trips' not 'routes'. Sending any file with lots of vias will give the problem you've experienced.


    Understood, so why does base camp create all of the vias when converting a track? I assume all of the little dots are vias?
  • Former Member
    0 Former Member
    BaseCamp doesn't your Zumo 350LM does. It's converts routes to trips. In short routes are broken up into smaller parts--trips.

    This whole subject is constantly discussed here and there are a great many threads about it.

    You'll find that many of us "oldies" won't purchase newer models because of the "Trip Planner". All my devices support routes--real routes.
  • Former Member
    0 Former Member
    BaseCamp doesn't your Zumo 350LM does. It's converts routes to trips. In short routes are broken up into smaller parts--.


    I think I understand the difference - thanks. However when converting a track to a route in basecamp it asks you to confirm the maximum number of vias. It seems to ignore this. Am I right in thinking that the little dots on a route viewed in base camp are vias?
  • Former Member
    0 Former Member
    Am I right in thinking that the little dots on a route viewed in base camp are vias?
    Yes they are. Actually by KGANSHIRT's definitions they're "Shaping Points". It's all very confusing as the terminology has changed over time... For example I've always referred to via's as the points (small black squares) created when drag'n'droping a route line.

    You might find this thread useful.

    POIs, Waypoints, Via-Points, Shaping Points 101
  • Former Member
    0 Former Member
    Many thanks for you continued help- much appreciated. That now make sense. Final question ... When I convert a Track to a Route in basecamp... Why does basecamp ignore my request to limit the via points to say 10. It seems to create a Route withe the same number of points contained within the Track.
  • Not sure, but you might like to look at the Basecamp help page http://static.garmincdn.com/basecamp/en/Default.htm and look at the part about filtering track points, it might help :)

    I too though am having the same problem trying to do it the way you do, and can't understand why. It looks like entering the maximum number of via points simply doesn't work ... I've raised it with one of the BC developers to see if he can explain.
  • Former Member
    0 Former Member
    It's a bug. We are aware of it and will fix it in a future release (not 4.2).
  • Former Member
    0 Former Member
    It's a bug. We are aware of it and will fix it in a future release (not 4.2).


    I'm surprised that this won't make it into v4.2. I guess the Win-BC community doesn't use Track to Route conversion much. Glad it's not broken on Mac-BC.