Route overshoots points

When creating a route using the Hiking profile, I am finding that the route overshoots the points I have added.

See the attached screen recordings. In route_no_direct.mov, you can see as I add the points that the route overshoots. When I play the route, the pointer therefore goes back and forth along the path, lengthening the route.

In route_with_direct.mp4, I hold the Cmd button while adding some points to use Direct. This makes the overshoot visible on the shape of the route.

Is this a bug or am I just doing it completely and utterly wrong?

Thanks,

Mark

0 SUSSAMB over 2 years ago

I can't view your videos but when hiking I always use the direct profile as it gives me more control over what the route does.

0 Mark Fisher over 2 years ago in reply to SUSSAMB

Well I would like to use the paths in the map if possible, as it saves a lot of time as opposed to creating lots of points, or else approximating which would result in a shorter length than in reality. I have replaced the .mov files, with .mp4 files, which seems to have fixed the issue.

0 SUSSAMB over 2 years ago in reply to Mark Fisher

Still can't view them. Issue with your method is you can only use tracks marked as routeable in the map you're using so you're at the whim of the map maker.

0 Mark Fisher over 2 years ago in reply to SUSSAMB

Sorry for the delay, I am currently away. It might be caching in your browser. I can view them in Firefox and Chrome.

I can't comment on the coverage of routable paths in the map I am using as I currently don't have access to a laptop, and have only tried with the path in the video. However, I am using a very highly regarded map, and the path I have tried it on is routable, despite being far from a main thoroughfare. Even if support for routable paths were patchy, that would not be a reason for doing it the slow and inaccurate manual way even for paths that are routable.

0 Zumo117014318 9 days ago in reply to Mark Fisher

Mark, I had a similar problem with the end point in one route overshooting by 1/2 mile. The Garmin route would take me a half mile beyond the endpoint and then request a u-Turn to take me back to the actual end point. Couldn't find a solution in Basecamp but this solution worked. Created the route in Google Earth, saved as a place then imported into Basecamp as a track. I then converted the track to a route in Basecamp. You've likely found a solution over the past THREE years but this might be helpful to other browsers. I had no problem viewing your MP4s.