function EXPAND

[Marinus van Deudekom]

2 possibilitys
When you’re done like in the first video, try to export that as a gpx track
Then upload that gpx to MRA and open it while Here is your standard map
2 put a lot shapingpoints, I mean a lot, by hand in that first route and then change the map to Here

[Jörgen]

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]

@Marinus-van-Deudekom said in function EXPAND:

2 possibilitys
When you’re done like in the first video, try to export that as a gpx track
Then upload that gpx to MRA and open it while Here is your standard map
2 put a lot shapingpoints, I mean a lot, by hand in that first route and then change the map to Here

I tried this as well and was surprised that the gpx file (the track) is different when you export (save) it from the original.

Whats wrong here?

I made routes with open street maps by using sections and curvy roads and filled it as well with waypoints to use it for navigation with Here map. I can't remember having this problem.

[Karel76]

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?

[Jörgen]

Yes, contact the support.

[Con Hennekens]

@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

[Marinus van Deudekom]

@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

[Karel76]

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/n1vrs605

video OSM (wrong route):
https://k00.fr/kvxz2d3t

[Jörgen]

@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?

[Erdna]

@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/n1vrs605

video OSM (wrong route):
https://k00.fr/kvxz2d3t

That 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.