I am creating a route for a walking tour of a town. There are multiple waypoints in the same block. When I create a route with these waypoints, Basecamp goes to the first waypoint fine, but to get to the next waypoint, it returns to the beginning of the block. In other words, it backtracks to the beginning of the block, reverses, passes by the first waypoint to get to the second waypoint. It will repeat this behavior for each waypoint in the same block. If the next waypoint is in the next block, it will go directly there. But the backtracking will reoccur for any other waypoints in that next block. I am using the latest version of Basecamp (4.4.6) and City Navigator NT 2015.3. I am also using the Walking profile with default settings. If I load the route into MapSource and recalculate, it routes fine. I can even save the route in MapSource and load it into Basecamp with the correct routing. In other words, if I use the Playback feature, the backtracking is gone. But if I recalculate the route in Basecamp, the backtracking returns. Any ideas?
I don't believe it's a map error I tried different maps with the same result. I think it's a BaseCamp error unless SUSSAMB has a better idea the only thing I think would help is for one of Garmin's Desktop App Developers to see this. I know they monitor the forums.
As a workaround until the bug is fixed I would create the route with no more then 1 point in the same block. If you have more stops on a block you could then make waypoints that are not part of the route. They will display on the map screen. You could also set up a Proximity Alarm on them if you would like your GPS to beep when you get to them.
Thanks for your help. I already changed the most current routes with this problem and added the proximity alerts. It would still save time if the routing worked as expected. I guess I can hope the developers have a solution.
They should really start a forum dedicated to the Christmas Present Crowd. :) ...ken...
Oh no, that'll never happen. With the excellent coordination between the Garmin devices and the Basecamp team, everything will work seamlessly. Plus which the BC documentation is completely up-to-date and easy to find. It'll be wonderful.
On the other hand, someone getting a Garmin device for the first time who wants it to do something besides take them to an address might decide that taking the gas pipe is a better option than learning how to get to be where most of us are.
I noticed a behavior with my 62s recently that may or may not be related to this. I travel by train frequently and set up routes from station to station as waypoints as a direct or point-to-point route. On a recent trip, while traveling between point 1 and point 2, I was actually became closer to point 3. The track shows an "S" curve. The 62s now showed point 3 as the next point, bypassing point 2 - the GPS essentially skipped point 2. Even when I was again closer to point 2 than 3, that point was still bypassed. The same behavior was observed on the return trip in the reverse direction. It appears the GPS thinks I bypassed the point and moved on to a further point as "next" because it saw a further (closer) point as next. In this case, using direct as the mode of routing, its easy to see what happened.
That's normal behaviour if you have off road transition set to auto, if you set it to manual or distance the behaviour will change.
If activity is set to "Direct Routing", why would Route Transition (set to auto) and Lock On Road (set to off) be a factor? I'm navigating direct - "as the crow flies", not on a road or trail. I don't understand what a Route Transition of Manual or Distance would do vs. Auto while using direct routing.
Manual will keep you pointing at the next waypoint until you either hit it or manually select another. Distance will switch when you get within the set distance. Auto will switch if the next but one waypoint is closer than the next waypoint.
