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 seem to be blocked from uploading files. Is there a trick to it? BTW, I did try it with other profiles and other maps. For example, I used a 24K topo map. In the latter case, there could be less backtracking, because the map has more detail (intersecting dirt roads, etc.). It seems to be tied to the route segments Garmin uses internally - it returns to the beginning of each segment.
I can reproduce this in BaseCamp 4.4.4 I haven't upgraded to 4.4.6 yet. I tried walking, bicycling and driving. I also tried City Navigator and Openfietsmap. The error is there in all cases. I have attached a screen shot and added text showing the order it routes the points and corners. If I send the route to my GPS it looks good on it.
I can reproduce this in BaseCamp 4.4.4 I haven't upgraded to 4.4.6 yet. I tried walking, bicycling and driving. I also tried City Navigator and Openfietsmap. The error is there in all cases. I have attached a screen shot and added text showing the order it routes the points and corners. If I send the route to my GPS it looks good on it.
It also looks good on my nuvi. Prior to discovering this issue, I also encountered the problem others have mentioned regarding Basecamp using direct routes to get from a given waypoint to the start of the next internal route segment (instead of following the road). This was fixed in a recent update (4.4.4). I wonder if this is related. Basecamp can now figure out how to route properly from the first waypoint in a given segment to the next segment, probably by tracking back to the start of the current segment and then tracing that whole segment. Somehow, the algorithm is able to eliminate the part of the route already traversed. If it encounters a second waypoint in the same segment, it gets confused, maybe because it gets more difficult to keep track of the route traversed and/or the programmers were leery of adding recursive operations. I know this falls in the realm of pure speculation, but all evidence seems to point to a bug in the routing algorithm. Since I use Basecamp fairly often for walking tours, this creates problems for me. The route may actually work properly on the device, but Basecamp will grossly overestimate the time and distance, and testing the route with the playback function is confusing at best. Your thoughts? Workarounds?
Tried again using points very close together and can now see the issue, guess I didn't realise how close you were keeping the points as difficult to understand why you'd want them like that :confused:
Tried again using points very close together and can now see the issue, guess I didn't realise how close you were keeping the points as difficult to understand why you'd want them like that :confused:
Definitely seems like a bug though.
I don't understand why anyone would want points that close together ether. But it should work. The OP said "There are multiple waypoints in the same block." so I gave it a try.
For walking tours of small towns, there are often a fair number of tour stops, some in the same block. I enter the tour stops, create a route with predetermined start and end points, then use the route Optimize function to have Garmin figure out the shortest route. As a work-around, I can use the basic route but delete waypoints that are close together. These can become POI's. But I would like to report the error. Should I use the Report Map Error process? Thanks for helping me confirm the bug.
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.
