function EXPAND
-
So probably a bug, because I used this feature once and it worked as it should. Now it's unusable. Thank you for your efforts. Is there any way to send this bug to the developers?
-
Yes, contact the support.
-
I am a bit confused? I usually use the same process with open street maps. I have no idea why you get a totally different route when you expand with more waypoints.
@Jörgen said in function EXPAND:
I am a bit confused? I usually use the same process with open street maps. I have no idea why you get a totally different route when you expand with more waypoints.
I am not so sure. This is not my method of creating routes, but isn't it so that Curvy options have some kind of randomness in it, exactly to prevent always getting the same roads? I am not surprised that this happens, I would be surprised about how it worked before when it did not change the route
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 -
@Jörgen said in function EXPAND:
I am a bit confused? I usually use the same process with open street maps. I have no idea why you get a totally different route when you expand with more waypoints.
I am not so sure. This is not my method of creating routes, but isn't it so that Curvy options have some kind of randomness in it, exactly to prevent always getting the same roads? I am not surprised that this happens, I would be surprised about how it worked before when it did not change the route
@Con-Hennekens I've created a route using that tool in the TomTom map and couldn't get rid of the algorithms when I extended the route with a piece of highway. The way out was then to export the curvy part as a gpx track with I then uploaded in MRA. Yep a bit complicated
-
So I found a bug. when I perform the same action on the base of TOM TOM maps, the "EXPAND" function works as I want. On the OSM base it generates a different route. I attach a video of the creation on TOM TOM
video TOM TOM (there is OK):
https://k00.fr/n1vrs605video OSM (wrong route):
https://k00.fr/kvxz2d3t -
@Con-Hennekens that is also not my usually method.
But when I create a curvy route (with what ever map) it should be possible to use them in MRA navigation as created.
So, why is the exported gpx file already total different to what was seen on the screen?
And why do I get a totally different route, when I expand what I see on the screen? -
So I found a bug. when I perform the same action on the base of TOM TOM maps, the "EXPAND" function works as I want. On the OSM base it generates a different route. I attach a video of the creation on TOM TOM
video TOM TOM (there is OK):
https://k00.fr/n1vrs605video OSM (wrong route):
https://k00.fr/kvxz2d3t@Karel76 said in function EXPAND:
So I found a bug. when I perform the same action on the base of TOM TOM maps, the "EXPAND" function works as I want. On the OSM base it generates a different route. I attach a video of the creation on TOM TOM
video TOM TOM (there is OK):
https://k00.fr/n1vrs605video OSM (wrong route):
https://k00.fr/kvxz2d3tThat is not a bug. TomTom and OSM use different card material and different algorythms for calculation of the route. Compared with different setting like cury route, restrictions like don´t use highways, etc. that behaviour is absolutely normal.
-
@erdna, you may be right. But this is not the point. Why is MRA making a totally different route when waypoints are added (with openstreet map)?
WP should be added to the route that was created with OPM as well as it is done with TT map.Hardware
iPhone 12 pro (iOS 180.2)
Oukitel RT3 (Andr. 12)
Samsung XCover 4 (Andr. 9 Pie)
Wireless CarPlay mit (Elebest C650)
Wired CarPlay (SEAT Arona - 2021)
For more information, (Workshops) click here -
@erdna, you may be right. But this is not the point. Why is MRA making a totally different route when waypoints are added (with openstreet map)?
WP should be added to the route that was created with OPM as well as it is done with TT map.@Jörgen said in function EXPAND:
Why is MRA making a totally different route when waypoints are added (with openstreet map)?
Seemingly that is due to a randomize function in the automatic creation of scenic routes. A curvy route between 2 points can be different from a curvy route between three points, even when the middle point is on the original 2-point route. That does not sound completely illogical to me.
WP should be added to the route that was created with OPM as well as it is done with TT map.
Remember that routes are calculated by the map-providers, not by MRA. Each map provider does things differently. That is nothing new.
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 -
OK,
I'll leave MRA and a software problem aside for now.
Adding loads of shaping points seems impractical to me.
There is <Compare route calculation with>.
Then you set shaping points to make the routes congruent. Incidentally, that was one of the parts involved in the creation of MRA
Or you can display the route as an overlay (on the left side of the menu). This would also work with a track log. Or simply the desired route. And on this basis, you then create a new route with the route engine of your choice.
I find the first alternative nicer and faster.
Interesting topic, maybe I'll add it to my to-do list for the next video conference.
RTTranslated with DeepL.com (free version)
-
@Jörgen said in function EXPAND:
Why is MRA making a totally different route when waypoints are added (with openstreet map)?
Seemingly that is due to a randomize function in the automatic creation of scenic routes. A curvy route between 2 points can be different from a curvy route between three points, even when the middle point is on the original 2-point route. That does not sound completely illogical to me.
WP should be added to the route that was created with OPM as well as it is done with TT map.
Remember that routes are calculated by the map-providers, not by MRA. Each map provider does things differently. That is nothing new.
@Con-Hennekens said in function EXPAND:
@Jörgen said in function EXPAND:
Why is MRA making a totally different route when waypoints are added (with openstreet map)?
Seemingly that is due to a randomize function in the automatic creation of scenic routes. A curvy route between 2 points can be different from a curvy route between three points, even when the middle point is on the original 2-point route. That does not sound completely illogical to me.
WP should be added to the route that was created with OPM as well as it is done with TT map.
Remember that routes are calculated by the map-providers, not by MRA. Each map provider does things differently. That is nothing new.
Ok, I understand that different maps generate different routes. The curvy function in OSM and TT are fine. And with TT generated routes, I can take them nearly 1:1 when I add WP to use with HERE (and navigation).
But why does it not work with OSM (nearly like in TT)?
If I can not use the generated route, what sens does this function make?
Or, how to solve this issue easily? (ok, you could add WP manually -
@Jörgen said in function EXPAND:
Why is MRA making a totally different route when waypoints are added (with openstreet map)?
Seemingly that is due to a randomize function in the automatic creation of scenic routes. A curvy route between 2 points can be different from a curvy route between three points, even when the middle point is on the original 2-point route. That does not sound completely illogical to me.
WP should be added to the route that was created with OPM as well as it is done with TT map.
Remember that routes are calculated by the map-providers, not by MRA. Each map provider does things differently. That is nothing new.
@Con-Hennekens said in function EXPAND:
@Jörgen said in function EXPAND:
Why is MRA making a totally different route when waypoints are added (with openstreet map)?
Seemingly that is due to a randomize function in the automatic creation of scenic routes. A curvy route between 2 points can be different from a curvy route between three points, even when the middle point is on the original 2-point route. That does not sound completely illogical to me.
Sorry Con, but it is totally illogical. With this tool, one expects MRA maintains the route. The route is already calculated, why not put the new added points on the route "as is", that would be logical. There is no use of a "new calculation" because the parameters for calculating the route didn't change.
Geluk/verliefdheid is net als in je broek plassen. Iedereen ziet het alleen jij voelt het.
-
By the way, I was there in that area, it is very nice!
https://routes.lexwill.cyou/cabriotour-tsjechie-2025/Geluk/verliefdheid is net als in je broek plassen. Iedereen ziet het alleen jij voelt het.
-
@Con-Hennekens said in function EXPAND:
@Jörgen said in function EXPAND:
Why is MRA making a totally different route when waypoints are added (with openstreet map)?
Seemingly that is due to a randomize function in the automatic creation of scenic routes. A curvy route between 2 points can be different from a curvy route between three points, even when the middle point is on the original 2-point route. That does not sound completely illogical to me.
Sorry Con, but it is totally illogical. With this tool, one expects MRA maintains the route. The route is already calculated, why not put the new added points on the route "as is", that would be logical. There is no use of a "new calculation" because the parameters for calculating the route didn't change.
@Lex.Kloet.RX said in function EXPAND:
With this tool, one expects MRA maintains the route.
Sorry Lex, but MRA maintains nothing except a web planner tool. Calculations are done by mapproviders. Each adding of a waypoint triggers recalculations. Rest assured: I really don't know whether OSM has randomize functions in it's curvy routes calculations or not. But what happens here makes me think so. And it would have a purpose. No one wants the exact same route each time they create a roundtour from home.
But I agree completely that the difference shown by in the first post are pretty dramatic.
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 -
By the way, I was there in that area, it is very nice!
https://routes.lexwill.cyou/cabriotour-tsjechie-2025/@Lex.Kloet.RX said in function EXPAND:
By the way, I was there in that area, it is very nice!
https://routes.lexwill.cyou/cabriotour-tsjechie-2025/Saved for later!
Thanks! -
@Lex.Kloet.RX said in function EXPAND:
With this tool, one expects MRA maintains the route.
Sorry Lex, but MRA maintains nothing except a web planner tool. Calculations are done by mapproviders. Each adding of a waypoint triggers recalculations. Rest assured: I really don't know whether OSM has randomize functions in it's curvy routes calculations or not. But what happens here makes me think so. And it would have a purpose. No one wants the exact same route each time they create a roundtour from home.
But I agree completely that the difference shown by in the first post are pretty dramatic.
@Con-Hennekens I didn't wrote, that MRA calculate the route, only that the route has been calculated, and therefore the gray line is somewhere stored. The only thing MRA has to do with the expand, is follow that line and put shapingpoints on that line
Geluk/verliefdheid is net als in je broek plassen. Iedereen ziet het alleen jij voelt het.
-
@Con-Hennekens I didn't wrote, that MRA calculate the route, only that the route has been calculated, and therefore the gray line is somewhere stored. The only thing MRA has to do with the expand, is follow that line and put shapingpoints on that line
@Lex.Kloet.RX, the grey line is not stored, it gets calculated each time. Only waypoints are stored.
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 -
@Lex.Kloet.RX, the grey line is not stored, it gets calculated each time. Only waypoints are stored.
@Con-Hennekens said in function EXPAND:
the grey line is not stored, it gets calculated each time. Only waypoints are stored.
The calculated route must be stored in some way. If I calculate a route with OSM, I can navigate "route as track" in the original shape, regardless of how HERE calculates the route.
-
@Con-Hennekens said in function EXPAND:
the grey line is not stored, it gets calculated each time. Only waypoints are stored.
The calculated route must be stored in some way. If I calculate a route with OSM, I can navigate "route as track" in the original shape, regardless of how HERE calculates the route.
@Martin-Wilcke, Yes, a low resolution track is stored with each route for use with the "route as track" feature. This has been added pretty recent. It is however NOT used in any planning features though, and that is only logical because we are talking routes and not tracks. The web planner is a route planner not a track planner.
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 -
@Martin-Wilcke, Yes, a low resolution track is stored with each route for use with the "route as track" feature. This has been added pretty recent. It is however NOT used in any planning features though, and that is only logical because we are talking routes and not tracks. The web planner is a route planner not a track planner.
@Con-Hennekens
Ahh, thanks, got it. But the "low resolution" track looks pretty detailed
