Query - Arriving at the Start Point of a Route

[jfheath]

I have never noticed this behaviour before....

A simple route created on the XT screen. A Start Point and an End Point. Save the Route. Go!

The start point (as always) is up the road, about half a mile away. It is correctly located. But after I have passed the start, the screen displays a question on the left hand side - Skip ? . With Yes / No buttons. Nothing to indicate what I am skipping. I say no, and it continues towards the end point.

Skip used to be displayed when a route point was missed completely. I haven't seen that for a long time. I thought that it was a feature that had been removed.

In repsonse to some technical support following up on my Broken Track logs, I have removed the SD card, reomved the OSM maps from the system and wiped out all of my data and performed a complete system reset. I am trying to make the broken track log problem re-appear. But thats a different issue. I've just come across this odd Skip after passing the start. I wonder if anyone else has encountered it ?

[Peobody]

Skip used to be displayed when a route point was missed completely. I haven't seen that for a long time. I thought that it was a feature that had been removed.

Hmmm... Now that you mention it, I recall being prompted to skip but, like you, haven't seen it in a long time.

I've just come across this odd Skip after passing the start. I wonder if anyone else has encountered it ?

I planned on taking a ride this afternoon on my Kawasaki that doesn't have a GPS mount but has new front brake lines that need testing. I will first take a ride on the 'wing with the XT. I have never created a route on the XT so this will be a new experience. I will report back.

[Oop North John]

Skip used to be displayed when a route point was missed completely. I haven't seen that for a long time. I thought that it was a feature that had been removed.

I think I saw "skip" when the XT was getting it's knickers in a twist over going off a Basecamp planned route which had waypoints, and I went another way. But, it wasn't wanting to skip the next point, but the one after.

[FrankB]

Never had this issue, or at least I did not notice.

Recently I tested the 'margin', based on that test I found that it was at least 30 Meters, 100 feet.
see: viewtopic.php?t=1998&start=10
If the problem is with the GPS signal of your unit, it's 'way off'. Good luck.

[jfheath]

I think I saw "skip" when the XT was getting it's knickers in a twist over going off a Basecamp planned route which had waypoints, and I went another way. But, it wasn't wanting to skip the next point, but the one after.

The one after ? Hmm. I wonder if that is what mine was trying to do - trying to skip the end point ? That is worth investigating. Thank you.

[Peobody]

I'm back after my afternoon ride which included two test routes. Both routes were created on the XT. All points were created by selecting spots on the map (on streets).

Route 1 contained a start point 1/2 mile from home and an end point 6 miles from home. I used the start point as the entrance point. The XT behaved as expected. There were no skip prompts.

Route 2 had a start point that was 1/4 mile away from the Route 1 end point, one interim point, and the end point was 1/4 mile from home. I intentionally turned off this route just prior to the interim point. I responded Yes to the recalc prompt then was prompted to u-turn 11 times before I hit the Skip button and told it to skip the interim point. It then calculated a logical route to the end point. At the 11th u-turn prompt I was much closer to the end point than the interim point so if there was going to be an automated 'skip' prompt it should have happened by then.

As I typed this it dawned on me that I wish I had thought to rerun Route 2 after changing the interim point to a shaping point to see if there was a difference in behavior.

[jfheath]

Thanks for that @Peobody

Do you have your track logs active ?
If so, can you take a look in CurrentTrackLog for the route you followed with loads of U turn requests please - Display it in Basecamp - they show as Active Logs in the lower left hand pane.

Is it fragmented ? ie broken into small sections with small gaps between each section ?

[Peobody]

Do you have your track logs active ?

If this is part of the travel history setting then the answer is No, otherwise I don't know. When looking at internal storage with Basecamp I only see my routes, the associated waypoints, and a track that was created from a Basecamp route. I plan to ride my Route 2 again tomorrow taking the same off-route roads home that I took today. I will do it with track logs enabled (tell my how if it is something other than travel history). I will then ride it again after changing the interim point to a shaping point.

Should entry point be a consideration (route start point vs closest entry point)?

Edit: BTW, I don't think the u-turn persistence I experienced in this case was abnormal since it was trying to get me back to the interim point which was a destination point. It routed appropriately once I skipped it. It would have been nice if the XT had recognized that I was moving away from that point and asked me if I wanted to skip it. It also would have confirmed the existence of an automated skip prompt mechanism.

[jfheath]

Yes, the active logs are controlled by the Travel History tick.

My feeling is that Closest Entry may have an effect. I can't say why I think that though. I start my route away from my current position and drive through the start point.

The U-turn request in my couple of recent tests to were also 'normal'. It was trying to get me back on to the route. It was just doing that by going back - because I had turned 180 degrees away from the plotted route.

I compared the gpx files for a Basecamp route with the same route calculated by the XT. BC uses far more decimal places for the via points than the XT uses. Ive yet to work out what the difference is in distance, but that may be why it didn't think I had passed through the start point - hence the 'Skip'.

[Peobody]

I compared the gpx files for a Basecamp route with the same route calculated by the XT. BC uses far more decimal places for the via points than the XT uses. Ive yet to work out what the difference is in distance, but that may be why it didn't think I had passed through the start point - hence the 'Skip'.

I was surprised by how nearly impossible it is to place a point exactly on a road when creating a route on the XT. Missing these points due to a proximity issue seems very likely.

I will be heading out shortly to do more rides of my test route. I think I will do three, restarting the XT between each one.
1. Use start point as entry point, go off route just before the interim destination point, allow u-turn prompts while logging.
2. Use closest entry as entry point, go off route just before the interim destination point, allow u-turn prompts while logging.
3. Change interim destination point to a shaping point, use start point as entry point, go off route just before the interim destination point, allow u-turn prompts while logging, be attentive to any difference in u-turn prompt behavior.