myroute web bug report

[ginogino]

The fact that I use the “Expand” function at the last, after checking the whole route for any problems and after using Expand I don't do any more checks, which is why until now I thought the problem was due to the navigation app on android.

[Tony 13]

very odd. I tested a few of my routes, and there were were a couple that changed by around 0.5km. Otherwise OK.
If you can share your route we might be able to help see what is causing the issue.

[paul69]

hi @ginogino

i referenced this problem in another thread, it is quite clear the problem is the waypoint placement. i occasionally use the function on MRA planner however i have learned the hard way, to always check every waypoint by zooming in to max.
in your example the routing engine has done a very good job of planning a route taking into account the waypoints.

obviously you would not want to ride this route, and this is the reason for checking only takes a short amount of time.
but again kudos to the routing engine great job.

[Jörgen]

Hi, it is difficult for an algorithm to place WP correctly during expansion or reverse, especially on streets with more than two lanes. You need manual check it.
It would be easy to see when there is something wrong on your route if you change the "Route transparency" to 60% in the Toolkit. Streets that will be used twice are now pure black.

[ginogino]

@Tony-13

The route link is in the first post, click on tour.

@paul69

I always carefully check where I place the waypoints, I didn't think I had to check those automatically placed by myrouteweb as well.

[paul69]

@ginogino said in myroute web bug report:

I always carefully check where I place the waypoints, I didn't think I had to check those automatically placed by myrouteweb as well.

it cannot be 100% relied upon to be accurate, I do it, if only to make sure they are correct, usually they are not far off, I also like to move them away from junctions, bridges, roundabouts etc

[Con Hennekens]

@ginogino, the need for checking of automated waypoints is well known indeed. What surprises me is that you did not recognize this problem immediately after expanding, since also in the webplanner you will usually see more or less distortion of your route.

Also the manual states:

CAUTION! Always check after expanding that all waypoints are still properly placed on the roads and thus after intersections, traffic circles, exits etc.

Personally, if I feel the need to add waypoints, I'd rather do that manually using my own gut-feeling

[ginogino]

@Con-Hennekens

I simply trusted the work done by myroute web and the problems I had on the road I blamed on the android app, from now on I will no longer use the “Expand” function and will only use waypoints placed by hand.

[RetiredWingMan]

@ginogino I use the expand function and then go back and verify the location of every waypoint.

[Con Hennekens]

@ginogino, well there is no need to abandon the function, just be aware how it works . The problem with automatic placement I think is that it tends to place waypoints at locations where bends and curves occur. Often that is at junctions and crossings. Exactly where you don't want waypoints... The function can be handy to up the number, quickly, but refined manual placement is still a must.