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?
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.
Ah, thanks! I wonder if anyone ever thought of putting stuff like this in the user guide? :rolleyes:
No idea but it's like that for every Garmin handheld I've owned/tried. I guess at some stage it may have been in a user manual, but as they got less and less useful more features were left unexplained :)
Just checked and it is though explained on Page 37 of the Etrex 20 manual.
Edit: and on page 36 of your manual I've just read
OK...I think I interpreted the statement "Automatically routes you to the next point" as the "next" point being the next point as listed in the route, NOT the nearest point to your current location. I'm done...thanks!
