Expand

[Martin Woodford]

Hi @peter-zehentreiter
Thanks for the reply. The problem happened with waypoints the MRA expand funtion placed, not with waypoints I manually added. Because I used the split function from a longer route the start and end points (both via points) of the shorter route were there, plus some number of other waypoints, all in the correct numbered sequence. When I used the expand function MRA added higher numbered waypoints between lower numbered ones.

[Brian McG]

@Martin-Woodford I understand exactly what you are seeing, splitting routes is standard practice for many MRA users & using the "Expand" function is the lazy way to add additionally points but it comes with risks
I have also had the issue you describe on routes I create if I add a large number of "Expand" points, hence my suggestion to add fewer "Expand" points
Sorry if my post above does not help

[Martin Woodford]

Hi @brian-mcg
Thanks, your post is really useful. The way you do it sounds like an excellent idea. As you mention, it was when I noticed the distance between start and finish had changed that I knew something was wrong.
Cheers

[Don Stauffer]

I just encountered this issue today, and it caused me some grief. I double checked my route, then used the Expand feature to create 20 shaping points to keep my Garmin on track. I loaded the track into my GPS, and did not notice the issue until after the lunch break, which I was tracking on my Garmin. After lunch, I discovered that it was 6 hours to my final destination, instead of 2 hours. Fortunately, I had saved the hotel address in my Zumo XT as a 'saved place' as a safeguard against this kind of problem. After my ride ended, I saw that indeed I had a higher numbered waypoint inserted in the list of lower numbered waypoints. In the future I will check the route AFTER expanding, but I wish that this kind of error could be eliminated by the software.

[Brian McG]

Hi @Don-Stauffer yes unfortunately the "Expand" function is not perfect, it is useful but you do need to check what it has done

Not only do you need to check that the overall mileage for the route has not changed (normally an increase)
but you should check the location of EVERY point it has added, tiresome I know

If you blindly assume it has put the added points in the perfect location you will be sadly mistaken
The "Expand" function often places points on or very near too junctions
If an MRA route with a point located on or near to a junction is transferred to another navigation system, it is highly likely that the poorly placed points will lead the other navigation system to take a different path from that junction

as you suggest it would be nice if these types of errors could be eliminated but with the present system if you don't check then the error is yours

When transferring routes from MRA to any other navigation system it is always wise to check that the overall mileage of a route has not changed

I include the MRA mileage in the route name so that when I open a route to navigate I can check that it has been calculated for navigation correctly
I still do this even when I am using MRA Navigation just out of habit from many years of routes going wrong
this is crude check, it is not infallible but at least it is a check

[Martin Woodford]

It would be nice if someone from MRA would comment on this. In particular what they're doing to fix it.

[Marinus van Deudekom]

@Martin-Woodford looking at your original post you asked how it is possible that shaping points added to the route where placed in a wrong order.
That can only happen if your route contained some faults like your shaping points not put in the correct order. This happens when you double a piece of the route. That can ben seen by the darker black line in your route.
Please share the url from one of those routes so we can help you. Make sure it's set to public.
The expand function only puts extra points between points from the original

[Brian McG]

@Marinus-van-Deudekom said:
That can only happen if your route contained some faults like your shaping points not put in the correct order.

Sorry @marinus-van-deudekom this is not true, when using the expand function it can incorrectly place a point, possibly on top of a bridge / overpass or on the wrong side of a divider on the exit of a round about
These errors will lead to the route changing, sometimes quite significantly

[Martin Woodford]

OK. So here's my original route, (377.32 miles) I hope it's public
https://www.myrouteapp.com/route/open/13569227
When I use expand to add just one more point (15, up from 14) it becomes 480.85 miles and point 8 has been added between poins 5 and 6, both of which are on the correct side of the road.

[Brian McG]

@Martin-Woodford try deleting the 2 points on the UK side of the channel then use the expand function
I think the ferry / tunnel maybe has something to do with the order / timing in this example getting really mixed up
after I did that then it was just the usual overpass errors

[Martin Woodford]

Hi @brian-mcg
Thank you. Yes, that works. I very much appreciate the experience you've shared in this thread.
However - to the MRA team, the expand function is part of what we pay for. I don't expect to have to rely on the knowledge and goodwill of forum members to make something work properly.

[Marinus van Deudekom]

@Martin-Woodford The first impression on opening your route

You can see that the point 6, 7 and 8 are not in a logical order resulting in a dark black line as I suspected

next problem is indeed like @brian-mcg suspected the starting point on the other end off the tunnel / ferry witch resulted in the route being verry long. Deleting the first 2 points will result in the route being expanded like you want. In my case I expanded to 20 points.

[Marinus van Deudekom]

@Martin-Woodford I have to put in a good word for the team. As you can see part of the failure was due to a mistake in your route. The other part is that you didn't know that expanding a route in witch a tunnel or Ferry plays a roll, you"ll get strange results. So no mistake by MRA.
Beeing a RouteXpert myself I must confess, witch rarely happens, that I didn't know the Ferry bit myself.

[Martin Woodford]

Absolutely not. This is my original 14 point route
https://www.myrouteapp.com/route/open/13569227

[Martin Woodford]

The new point number 8 can be identified as an MRA expand point because it's labelled "waypoint" the ones I manually placed have road numbers

[Martin Woodford]

I don't see how "expanding a route in witch a tunnel or Ferry plays a roll, you"ll get strange results. So no mistake by MRA" can be the case. Why should a tunnel or ferry mean the results are strange ? I'm in Norway at the moment, there are hundreds of tunnels and ferries should I expect strange results everytime one is on my route ?

[Marinus van Deudekom]

The problem occurs when you expansie the route.
In your original route you can see that the order of the shapingpoints is not logical. See my screenshot.

[Martin Woodford]

Hi @marinus-van-deudekom
Thanks for your comments. The screenshot you show is from the expanded route. This is my original 14 point, 377.32 mile route. In a moment I'll expand it in MRA and screenshot it again (MRA makes the changes in realtime and I don't know how to save versions of the original and expanded route)

[Martin Woodford]

Hi @marinus-van-deudekom
This is the expanded version. Please note the location of the new waypoint 8 and it's description.

[Martin Woodford]

I will now reset the original in MRA