Expand

[Martin Woodford]

I've had two problems lately using the expand function.
I created one long route which I then broke into smaller, day sized rides using the split function. I then expanded the number of waypoints in the split routes. On multiple occasions MRA added higher numbered waypoints between the lower numbered ones which had been part of my original planning. This had the effect of making the routes hundreds of kms longer than they were originally and me going back and forth on myself - luckily I saw the problem before I actually set out to ride the routes. On another occassion MRA added a waypoint on an overbridge above the route I planned, this time I didn't notice it before hand and I started out on a wild goose chase before I realised what had happened.

[Peter Zehentreiter]

@Martin-Woodford To prevent MRA from placing waypoints at the end of the waypoint list, you need to be careful where you place the new waypoint.

Make sure you place the new waypoint close to an existing one and exactly on the line; this will ensure it is placed in the correct order and numbered correctly.

You can then move this new waypoint to the desired location.

To avoid taking detours due to incorrectly placed waypoints, it is advisable to check all waypoints after planning your route; it is also advisable to zoom in as far as possible to see whether the waypoint is placed on the road or next to it.

Please also ensure that you never place waypoints too close to junctions or roundabouts.

[Brian McG]

Hi @Martin-Woodford the Expand function is useful to help constrain your route to the path you have planned & want to take, but it is also dangerous as you have discovered

I tend to be fairly careful when using the expand function
The method I use is to slowly increase the number of points e.g. if the route I want to has 40 points I would first increase it to 50 or 60 points & check that the overall distance between start & destination does not change

If 50 or 60 works ok, I would undo this change vie the back function in the bottom right of the route map page & then repeat with say 80 & again check that the overall distance between start & destination does not change

If the distance increases then you know the path for the route has changed & you will need to investigate where it has changed
A good way to compare if a route has changed is to make a copy of the route & display the copy on the map via the "Routes" option under the 3 bar burger menu

Whenever I use the "Expand" function I do thoroughly check that each of the points in the route are located in sensible locations i.e. not right on top of a junction.
Poor placement of points whether by the "Expand" function or manually can lead to unexpected detours

[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