App slow in recalulating route

[Tim Rice]

I sometimes use the app in areas where I have local knowledge and therefore may know shortcuts. If I take one the app often takes a long time to recalculate the route and keeps suggesting a U turn to go back on the original route. It will keep doing this even when the "new" route is appreciably quicker. The last time I did this, when it eventually changed to my route it saved 15 minutes (out of a journey time of an hour). This was not using farm tracks or any different road types from the original

This is using Carplay wireless connection.

Any thought/suggestions?

Thanks, Tim

[GT JWR]

@Tim-Rice had that happen as well....the app tried to get me to make a u-turn for 23mi.....the ironic/comical thing about it is that it was in an area of local knowledge for me, and there were at least 2 other routes that would have been more ideal, yet the app insisted on the u-turn. I'll be curious to see if an answer is forthcoming.

[richtea999]

Hello Tim,

It may help if you make the faulty route public and describe where you wanted it to go. Then we can have a play!

[Tim Rice]

Thank you.
This is the original route (from Winchcombe to Bicester, with no way points), although this one is produced from the website rather than the App on my iPhone. (I do not know if I can share the one from the App.)
https://www.myrouteapp.com/en/social/route/9759726?mode=share

This is the actual route I took:
https://www.myrouteapp.com/en/social/route/9759755?mode=share

FYI the preferred route uses roads that are more fun, and avoids Stow on the Wold, which is a bottleneck.

Cheers,
Tim

[Brian McG]

Hi @Tim-Rice the link to original path (from Winchcombe to Bicester, with no way points) looks like it is a track
this thread might be discussing a similar issue https://forum.myrouteapp.com/topic/7596/keeps-sending-back-on-route-it-calculated-itself
if it is the same issue I think things are working as intended, till you get close to being back on the track it will keep trying to reroute you back to the location where you originally left the track

[richtea999]

I think Brian may well be right, but I'm no expert on tracks - I only use routes, so take my advice with a pinch of salt.

Did you use the 'create a scenic route'?
I tried that and it gave the same route - i.e. not very scenic when it involves a 5 minute wait in Stow! If you disable 'main roads' that gves a more amusing route-track, but still not a nice as yours.

I could be biased here, but two steps come to mind:
Step 1:

• use the create scenic route only as a first step
• convert it to a route ('Edit route-track', top rightish)

See if you like what's created.
If you do, then use the route with waypoints, and you'll be kept on the route.

If not, then:
Step 2:

• decrease the number of waypoints to something usable (Toolkit -> Reduce (Gold))
• then tweak the remaining waypoints where you can see obvious problems, like Stow

Now the app has planning built in all the above is possible on the fly, but it would take 5 minutes and a decent signal.
About as long as you would be sat in Stow.

[Tim Rice]

Thanks for the feedback. I may be missing the point, but the link was only to show where I was going from and to.
What I had done was to use the app on my iphone and set the end point (a Favorite) as the destination and pressed Start.

[richtea999]

@Tim-Rice Ha - more like me missing the point!

If you just route from A-B using the app I don't think you're going to get an interesting route, even if you do use the 'scenic' route options.

The problem is that the A-B scenic route doesn't offer you control over distance or time taken, so you're inevitably going to be going quite direct - hence the Stow issue.

I have suggested improving the feature, but Corjan says it's not easily improved - which is a shame. (I'm guessing MRA is using a HERE API which can't be altered/tweaked without a lot of hassle.)

In this particular case you might be better trying Calimoto or a similar app that is more geared towards creating instant wriggly A-B rides rather than planning, which is MRA's strength.

[Tim Rice]

@richtea999 I don't think that I am (for this route) that sophisticated a user.

I was aiming to get to Bicester and used the app to help (keeping an eye out for traffic, etc) while knowing a couple of the roads that are fun to use. What surprises me is that the app takes a long time to recalculate, even if I am well past the point that "my" route is quicker than the app planned one (here I am assuming it is trying to get to the destination in the shortest time - but is that how the algorithms work?).

Google seems to recalculate much quicker.