re joining route mid way ?

[Paul Hicks]

Thanks for the feedback. The link below is the route I set up to test and am trialing it on a daily basis. The first deliberate deviation is around the alternative roads between waypoints 1 and 2 (basically following the return route roads, waypoints 4 to 5) and the second is between 2 and 3. The first time it worked well, the second time it tried to take me back to waypoint 1. I didn't check the waypoint icon at that time, to see what was going on there. Traffic was just a little busy to concentrate on something other than the traffic.

On another trip I travelled between way point three and four without a problem. On a second trip the app tried to take me off route (M1) about 10k from waypoint 4 and put me on Old Gympie Road. That one confuses me. I have no idea what happened, unless there is some traffic congestion input? (fastest trip?). Thanks in advance for any advice that I can get.

In most of my trips there are so many dead spots with no online data available, and I have to rely on off-line. My focus is testing and understanding that, as my trip to Biggenden and back is only a couple of weeks away. But I will do a test route online and see what difference that makes.

I have made a few trips on the planner public, including the upcoming trip. Feel free to check them out. There is a Cleveland Snowy Mountains trip I did a few years ago planned in MyRoute loaded onto a Garmin Zumo. It gave 10 days, guidance didn't miss a beat. Country and city alike.

Test trip - https://www.myrouteapp.com/en/social/route/12045745?mode=share

[Marinus van Deudekom]

@Paul-Hicks hi Paul
I’ve looked at you test route. All of your shaping and viapoints are Off route.
I would suggestieve that you fix that first. If you diviate on a route like it’s now the chances Off strange behaviour are big.

[Nick Carthew]

@Marinus-van-Deudekom Are they off the route line? Not enough to make a difference when I look!

@Paul-Hicks If you want to stay true to your original route, I would recommend adding some more shaping points. If you’re navigating online there’s a chance that traffic/road conditions could have an effect on the recalculations.

[Con Hennekens]

@Paul-Hicks, Also you place waypoints too close and even ON roundabouts and crossings. That's not good practice. But also this route is a back and forth route over the same roads. I think any skipping algorithm will by fooled by that. It is not really representing a usual scenic route.

[Paul Hicks]

Marinus/Nick,
Thanks for the heads up. I am not sure if you know we drive on the left-hand side of the road down under. Checked the "Off Route" waypoints and shaping point and only had one in a property and not on route. I moved that. All other points remain as is and the app picked them all up perfectly, progressing from one to the next in logical sequence. I was following the route without deviation.

I gathered some courage from that, (lol) and went out testing the app on a scenic tour using it with Android Auto. That also didn't miss a beat once I got a couple of things sorted and until the phone battery went flat. Not sure I can blame the flat battery on MyRoute?

I am now pretty comfortable that I am not going to run into anything unsolvable when I head out in a couple of weeks. And yes, I remain a fan of MyRoute.

Con, you have the route "Zetta School Run". Here's what happened a couple of days ago when I deliberately went of course again, between points 1 and 2. The app continually redirected back to the route between point 1 to point 2 even though I was less than 300m from point 2. I cleared point 2 as a shaping point at that point and the app immediately recalculated to point 3 perfectly. Could not have been better. I am not sure of the logic as to why this was the case although I could have an educated guess. But just knowing how things behave all helps me use the app more effectively.

I appreciate all the comments and advice that I have received. PS I only had the positioning working "while using the app" option. With Android Auto it has to be all the time. I am now leaving it on that setting. Another test. :-).

[Con Hennekens]

@Paul-Hicks said in re joining route mid way ?:

Not sure I can blame the flat battery on MyRoute?

I think the power drain of the app is perhaps a bit more than seen with other apps, but in most cases not really a concern anymore. What I experienced myself is that the powerdrain of wireless Android Auto itself is quite significant. Are you using this wirelessly?

The app continually redirected back to the route between point 1 to point 2 even though I was less than 300m from point 2

This sounds as if it was still directing you to WP1, probably because you did not "hit" it at the start of your route. It is a common mistake to place WP1 at your doorstep, it should be placed a bit further down the route. On AA/CP devices there is no indication of which WP is the next target. But since WP1 is always a VIA point, it will not skip automatically.

[Paul Hicks]

I actually have a power supply in my panniers with a couple of USB chargers that I keep the phone and camera batteries plugged into on a trip. Unfortunately, the one I plugged the phone into wasn't connecting properly and it didn't charge my phone. That's entirely on me. But I admit, the app consumes some power. Without the phone on a charger I doubt if I'd get more than 2 or 3 hours before being it was flat. That's based on my experience without android auto. I wouldn't even contemplate using the MyRoute App/Android Auto without a power supply to my phone.

Sorry Con, I can absolutely assure you that Way point 1 was moved away from the start of my journey, and it was identified as I passed it. I was merrily on my way to shaping point 2 according to the app. I think, and is only a thought, that once I went off course (intentionally) the app somehow tried to get me back on course (which is logical) but without a full route recalculation to work out the shortest/fastest route to the next waypoint/shaping point. Once I cleared shaping point 2, (and I hadn't yet reached shaping point 2) the app appeared to fully recalculate and set course for the next shaping point (point 3) perfectly. Smarter men than I can ponder that one.....lol

[Con Hennekens]

@Paul-Hicks, That actually sounds like it functioning completely as intended
The app will not skip a waypoint at first occasion, but only at the second or more occasions, when certain conditions are met. Afterall, it tries to follow your meticulously planned route without skipping a lot.

[Con Hennekens]

@Paul-Hicks, I found a threat where @Corjan-Meijerink explains the skipping logic in more detail:
https://forum.myrouteapp.com/post/64435

There has been an update concerning this though:

• rule 2 says "are we moving" has been changed to "is my speed below 10 kph", to avoid unwanted recalculations while standing still, due to GPS inconsistencies.
• rule 5 says "are you more than 30 km away from the the next shapingpoint to be skipped too", this has been reduced to 20 km

I have been testing this quite extensively before and after the update, and find the logic quite satisfying, but you must keep in mind that routes are not about getting somewhere quick, but about maintaining them as much as is reasonable. The latter of course being interpretable in different ways

[Brian McG]

Hi @Con-Hennekens said in re joining route mid way ?:

this route is a back and forth route over the same roads.
I would totaly agree some navigations systems would totaly freak out at a path that returned over the same roads,
have seen many instances where Garmin systems just cannot cope with a simple figure of 8 looping route they have to be divided into out & back sections to get them even to calculate correctly

have to say I have been very impressed with how MRA handles figure of 8 routes & returning over the same roads, not personally had a falure yet