@John-Gower-0 Place a route point at the landing place of the ferry and then use the ‘skip’ function on that RP. 1D83B6E4-ED03-454C-B868-35992AB7EB6F.png

@Christian-Schrenk “The more waypoints are set, the more accurately the route is transmitted.“ Local conditions like heavy traffic or road closures can affect your TT and maybe cause it to take a diversion. Placing more waypoints does not make the route more accurate. In fact, it multiplies the chances of an inaccurate route if all waypoints are not fully checked as previously mentioned. And as you said, it makes rejoining your original route difficult.
And the language used on the maps is out of the control of MRA like @Hans-van-de-Ven-RouteXpert said in a previous reply, but I think we have found you a solution. 👍🏼

@Dave-Edge They are generated by the map suppliers Dave.

@Nick-Carthew-RouteXpert Thanks Nick, Just seems that HereMap does some odd routing choices as opposed to Google Maps. If the offer of route planning on Google Maps is made on the mapping choice its a shame it doesnt transfer onto mobile devices. Thanks again

@Nick-Carthew-RouteXpert
Thanks for the reply.
I guess my take from what you've just said is that it is the Route Navigation algorithms which make up the journey time in the Itinerary, not the Myroute app and thus it would be difficult to implement I get that.

I would dispute the too many variables to be useful comment.

Bear in mind that I'm not talking about dynamic timings whilst riding most Nav apps are pretty good at ETA's and you learn with experience

I'm talking about what is, for me at least, one of the primary differentiators of MRA. Ease of Route Planning for use on a variety of devices.

Its the easiest to use and most versatile route creation tool I've found, by a country mile.

I would argue that for route planning and producing an itinerary these variables, think Fuel stops, Photo Opportunities, Cafes, Restaurants, Museums Etc take up a significant part of the day, especially with a large group or a "sightseeing" type of trip. Route planning without taking these variables into account only produces a useless itinerary!.

The current process is iterative - create a rough route and planed stops. Manually allow for the variables above, realise that the planned stops don't work together. Modify the route and/or or stops, recalculate. Repeat until we have a route that arrives at museums when they are open, and planned food breaks and final destination at about the "right" time.

If MRA used the journey time data from the nav app but enabled users to allow for these waypoint variables to produce a detailed Itinerary with modified timings when creating the route, it would significantly simplify this process, and produce a reasonable itinerary first time every time. I would consider that to be useful to me and presumably others too. 😀

@Reinhard-32 danke