Roundtour to a dead end?
-
Every time I try to create a round tour it seems to route to a dead end?
Screenshot example.
To me it seems like that road is closed due to some restrictions, roadworks, seasonal closure.
Can you give us the link to that route, make sure the route is set to public
-
Nothing to indicate a closure on Google maps and it actually does it twice...
-
Nothing to indicate a closure on Google maps and it actually does it twice...
@HighPeakRider It depends on your intentions and how you are planning to make the scenic tour! Are you using the app while already on the motorcycle and ready to ride immediately? Or are you planning the route, for instance, the evening before while sitting at your PC? In both cases, MRA creates one or more routes for you. If you accept the route immediately and start riding directly, you might encounter a loop or be directed down a street only to be turned back. My advice would be to accept the route in the planner (by default, this is a track with just a start and end point). The planner then turns this track into a route with two via-points (start and finish) and multiple shaping-points. After this, check if there are any shaping points in illogical places and move them to a different spot on the route or simply remove them.
If you you have a gold subscription you can also highlight the traffic overlay to see if there are some traffic issues on your route.
-
Nick Carthew moved this topic from [App] Problems, Bugs and other Issues on
-
The route generator in the website is sub optimal and often the routes require tinkering. The round trip generator in the app is much better. You can be riding a route with just 3 clicks.
-
The route generator in the website is sub optimal and often the routes require tinkering. The round trip generator in the app is much better. You can be riding a route with just 3 clicks.
The TS was actually using a Round Tour.
In my experience using Round Tours they often contain roads that would require a U Turn.
I just remove them to create a continuous loop.You donβt stop riding when you get old, you get old when you stop riding.
-
The TS was actually using a Round Tour.
In my experience using Round Tours they often contain roads that would require a U Turn.
I just remove them to create a continuous loop.@Lynchy67 said in Roundtour to a dead end?:
The TS was actually using a Round Tour.
In my experience using Round Tours they often contain roads that would require a U Turn.
I just remove them to create a continuous loop.Yes, but created on the website. The one built into the app creates them not only more accurately but faster too.
Always willing to help if I can.
Triumph Tiger 1200 XRT called Tina.
MRA Navigation Next and SilverFox BJ8 -
@Lynchy67 said in Roundtour to a dead end?:
The TS was actually using a Round Tour.
In my experience using Round Tours they often contain roads that would require a U Turn.
I just remove them to create a continuous loop.Yes, but created on the website. The one built into the app creates them not only more accurately but faster too.
Doh! I didn't even realise there was an In App version.
I'll get my coat............... -
The route generator in the website is sub optimal and often the routes require tinkering. The round trip generator in the app is much better. You can be riding a route with just 3 clicks.
@Nick-Carthew the UI / UX of the app is indeed better.
It really is however the same roundtour calculations with similar flaws
-
@Nick-Carthew the UI / UX of the app is indeed better.
It really is however the same roundtour calculations with similar flaws@Corjan-Meijerink said in Roundtour to a dead end?:
@Nick-Carthew the UI / UX of the app is indeed better.
It really is however the same roundtour calculations with similar flawsMaybe I donβt notice the flaws because it creates a round trip so quickly
-
Nothing to indicate a closure on Google maps and it actually does it twice...
@HighPeakRider
To me, it looks like there's no flaw or whatsoever. First of all, at 2 locations a left/right turn was made but the route was followed as it should be (routepoint 18 and routepoint 33).If it was intended to follow the road at routepoint 18, routepoint 19 should be located at a location which follows the route after routepoint 18. Same goes for routepoint 33 and routepoint 34.
Even when i turn off seasonal closures, nothing changed on the route.
If you could elaborate which direction you prefer from routepoint 18 and routepoint 33, i could have a better look in how this went wrong in MRA.
But for now, my conclusion is, is that routepoint 18 and 33 are misplaced and should not been there.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better π
Register Login-
04107
-
716611.8k
-
010192
-
0341.3k
-
33156
-
06124
-
05306
-
023611
