Ferry Problem
-
I have noticed a problem when a route includes a ferry using HERE routing. For example, look at the following test route:
https://www.myrouteapp.com/route/open/3550405
With a waypoint on either side of the ferry, HERE creates a route that bypasses the ferry in favor of a much longer circuitous route. A workaround is to select Toolkit/Avoid/Highways, but that is not a good solution if you don't want to avoid highways.
The problem does not occur with either Tomtom or OpenStreetMap routing.
I haven't checked to see if this occurs within the navigation app.
If this is a problem with HERE routing, it probably exists within the navigation app.
How can this be elevated for Garmin to check?
Gil
-
@Gil-Yoder Place a route point on either side of the crossing and then use ‘skip’ on the route point on the far side of the crossing. This draws a straight line and effectively turns navigation off to stop re-routing.
-
@Gil-Yoder Skip selected on RP 2
-
@Nick-Carthew Skip works fine in the web app, but it doesn't help in the Navigation app. When the route is loaded in the Navigation app, the route is recalculated without the skip.
And the Nav app behaves the same as the web app. The ferry is avoided unless "Avoid highways" is enabled.
Working this out in my head, I guess the thing to do is to use skip to include the ferry when "Avoid highways" is disabled, complete your route with expanded waypoints to force routing on highways, and then enabled "Avoid highways" in the nav app to include the ferry.
That's kind of convoluted, but I think it would work.
-
@Gil-Yoder I haven’t tested the Nav app for this, but I’ll set up a test route and report back with my findings.
-
@Gil-Yoder The Nav app should take you to the ferry, ignore it if it tries to re-route you. It should then re-calculate when you arrive on the other side.
-
@Nick-Carthew said in Ferry Problem:
@Gil-Yoder The Nav app should take you to the ferry, ignore it if it tries to re-route you. It should then re-calculate when you arrive on the other side.
This makes sense, Nick. Thank you for your help.
