Problems with the "Avoid Toll Roads" option
-
Since the last update (Version 4.4), when you select the "Avoid Toll Roads" option, the app assumes you shouldn't use highways. It's as if the app can't identify which highways are toll roads and which aren't. Examples:
In this example, a route has been created where the "Avoid toll roads" option has not been chosen, and the app goes through the M-45 motorway (Madrid), which is not a toll road.
In the same example, the option "Avoid toll motorways" has now been chosen, and as can be seen, the app avoids using the M-45 motorway (Madrid), identifying it as a toll motorway when it is not.
-
Since the last update (Version 4.4), when you select the "Avoid Toll Roads" option, the app assumes you shouldn't use highways. It's as if the app can't identify which highways are toll roads and which aren't. Examples:
In this example, a route has been created where the "Avoid toll roads" option has not been chosen, and the app goes through the M-45 motorway (Madrid), which is not a toll road.In the same example, the option "Avoid toll motorways" has now been chosen, and as can be seen, the app avoids using the M-45 motorway (Madrid), identifying it as a toll motorway when it is not.
@Giancarlo-e, You are showing route calculations on the WEB-planner. Therefore your assumption that it has to do with the APP version holds no ground. Changes in the app do not reflect anything in the web-planner. Also I see "Usar segmentos" enabled, which indicates you are using the OSM map, while the app only uses the HERE map. Not a solution for your problem, but just some observations
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
@Giancarlo-e, You are showing route calculations on the WEB-planner. Therefore your assumption that it has to do with the APP version holds no ground. Changes in the app do not reflect anything in the web-planner. Also I see "Usar segmentos" enabled, which indicates you are using the OSM map, while the app only uses the HERE map. Not a solution for your problem, but just some observations
@Con-Hennekens Thank you for your comment. However, your observation doesn't change the final result. Whether on the web or in the app, the final result is the same. Whether with more OSM or with HERE maps, the result is the same. So I don't fully understand the reason for your comment. The problem is that the web and the app misinterpret the "Avoid toll roads" option.
I'm also an avid MRA user. I think it's an excellent app and I've recommended it to many friends. But I have to admit that in the latest updates, or whatever you want to call them, the web or the app, they do things they didn't do before. Even on my Blackview 8900 Pro phone, since the last update, the app doesn't work. I load the app and the screen goes black. I don't know if it's the update or something, but the truth is that the problems coincide with the update. -
@Con-Hennekens Thank you for your comment. However, your observation doesn't change the final result. Whether on the web or in the app, the final result is the same. Whether with more OSM or with HERE maps, the result is the same. So I don't fully understand the reason for your comment. The problem is that the web and the app misinterpret the "Avoid toll roads" option.
I'm also an avid MRA user. I think it's an excellent app and I've recommended it to many friends. But I have to admit that in the latest updates, or whatever you want to call them, the web or the app, they do things they didn't do before. Even on my Blackview 8900 Pro phone, since the last update, the app doesn't work. I load the app and the screen goes black. I don't know if it's the update or something, but the truth is that the problems coincide with the update.@Giancarlo-e you are not the only one with problematic app after the update. i'm in the same situation unfortunally. I've had to revert back to update 4.3.9 to use the app at this moment.
-
@Giancarlo-e you are not the only one with problematic app after the update. i'm in the same situation unfortunally. I've had to revert back to update 4.3.9 to use the app at this moment.
@Manzo91 I didn't know you could reinstall a previous version... Can you tell me how to do it? Thanks.
-
@Manzo91 I didn't know you could reinstall a previous version... Can you tell me how to do it? Thanks.
@Giancarlo-e Install Aptoide from Google. Uninstall version 4.4.0, look for MyRoute App in Aptoide and select "Older Versions" and get V 4.3.9 and log in with your account.
Good Luck ! -
@Giancarlo-e Install Aptoide from Google. Uninstall version 4.4.0, look for MyRoute App in Aptoide and select "Older Versions" and get V 4.3.9 and log in with your account.
Good Luck !@Manzo91 thank
-
@Con-Hennekens Thank you for your comment. However, your observation doesn't change the final result. Whether on the web or in the app, the final result is the same. Whether with more OSM or with HERE maps, the result is the same. So I don't fully understand the reason for your comment. The problem is that the web and the app misinterpret the "Avoid toll roads" option.
I'm also an avid MRA user. I think it's an excellent app and I've recommended it to many friends. But I have to admit that in the latest updates, or whatever you want to call them, the web or the app, they do things they didn't do before. Even on my Blackview 8900 Pro phone, since the last update, the app doesn't work. I load the app and the screen goes black. I don't know if it's the update or something, but the truth is that the problems coincide with the update.@Giancarlo-e said in Problems with the "Avoid Toll Roads" option:
Even on my Blackview 8900 Pro phone, since the last update, the app doesn't work. I load the app and the screen goes black. I don't know if it's the update or something, but the truth is that the problems coincide with the update.
I cannot speak for your black screen problem, but the misinterpretation of your toll-road example has definitely nothing to do with any app update. I checked your situation against the TomTom and HERE maps, and they both do NOT show the same problem:
This leads me to believe there is a map-error on the OSM map. You can apply for a change here: https://www.openstreetmap.org/fixthemap
The reason for my earlier comment is that it is illogical to plan routes you want to navigate using the MRA app with any other then the HERE map, since the MRA Navigation module uses HERE maps exclusively. If you take notice of my advice, it definitely changes your result
-
I am a beginner user and think I had a similar issue. Or possibly a similar issue. I planned a route from north to south of France. I had waypoints in the route. I set options to use motorways, avoid tolls and fastest. When I opened route it did give me route violation warning. But did not say where or offer an alternative. On 3 separate occasions the guidance took me on a toll road. Which is I guess the only way to get me to my next waypoint. (This is usually avoided when using Garmin devices.)I think possibly the weighting and priority of the route planning should firstly avoid tools, then compute fastest time. Or not allow route creation. It’s hard to avoid a toll when you’re on the approach road!
-
Share a link to the route and make the route public. We can review the route to try and solve the issue.
-
Since the last update (Version 4.4), when you select the "Avoid Toll Roads" option, the app assumes you shouldn't use highways. It's as if the app can't identify which highways are toll roads and which aren't. Examples:
In this example, a route has been created where the "Avoid toll roads" option has not been chosen, and the app goes through the M-45 motorway (Madrid), which is not a toll road.In the same example, the option "Avoid toll motorways" has now been chosen, and as can be seen, the app avoids using the M-45 motorway (Madrid), identifying it as a toll motorway when it is not.
Hi @Giancarlo-e I can replicate what you see in MRA with the OSM routing
Inspecting the OpenStreetMap data on the OSM site, it has no tags for tolls on this section of motorway
Replicating the same route in Osmand with the Avoid Tolls option enabled it routes correctly along the motorwayThe only conclusion I can come to is that the MRA version of the OSM data must have an incorrect Toll tag on this section
-
View 'To Levigniac' in MyRoute-app! https://www.myrouteapp.com/route/open/11805038 There were sections of this router prior to starting point but I deleted them after use and only have this section left
-
I am a beginner user and think I had a similar issue. Or possibly a similar issue. I planned a route from north to south of France. I had waypoints in the route. I set options to use motorways, avoid tolls and fastest. When I opened route it did give me route violation warning. But did not say where or offer an alternative. On 3 separate occasions the guidance took me on a toll road. Which is I guess the only way to get me to my next waypoint. (This is usually avoided when using Garmin devices.)I think possibly the weighting and priority of the route planning should firstly avoid tools, then compute fastest time. Or not allow route creation. It’s hard to avoid a toll when you’re on the approach road!
@Donovan-Smith said in Problems with the "Avoid Toll Roads" option:
When I opened route it did give me route violation warning.
Planning a route in OSM will start the "Navigate Route as a Track" feature, because Navigation uses the HERE map. Navigating a track does not give room for alternative routing. So if you plan your route in OSM (which obviously has a problem in that area concerning toll roads) and start navigating in the MRA app (using HERE as the only option) things like this happen.
-
I planned it on the web through the web app. So can I assume the web app is osm ? I know the the Next App is here maps.
-
I planned it on the web through the web app. So can I assume the web app is osm ? I know the the Next App is here maps.
@Donovan-Smith the navigation app on your mobile uses the Here routing algorithm
the Here algorithm is the one used for navigation by MRAon the Web planner when you are planning you can choose which routing algorithm you wish to use either OSM, TomTom or Here
You should choose the algorithm that matches your navigation device
So if your using MRA or a Garmin to navigate it is best to use the Here routing algorithm
If your using a TomTom obviously best to use the TomTom algorithm
If your using Osmand then best to use the OSM algorithm
The TomTom & Here routing algorithms are not available with a basic web account, you need either a Gold or Navigation subscription to access themThe map layers are just graphic overlays they just show you where the roads are, they are not responsible for calculating the routing
