Using ferries within the APP
-
I recently planned a route as usually on the web and included a ferry. I used the known technique with skip point on the far end of the ferry and everything looked fine on the web. So now I have driven the route with the APP and instead of suing the same direct link to the far end of the ferry connection, it routed the distance between the 2 ferry points via roads and bridges, ignoring my setting from the web page.
Any ideas What have a made wrong?
Greetings
Tom
iphone 12 Pro (iOS 18.1)
iPad Pro (iPadOS 18.1)
MyRoute-APP (4.3.3 - 357, Lifetime Gold)
on KTM 1290 Super Adventure R (model 2022) -
@TomOnTour this is completely "normal" as the Navigation app cannot distinguish the normal from the skipped waypoints! They trick is solely for the planner!
You shall make the entrance to the ferry a via point so your always navigated up to the ferry, then simply wait to get to the other side and there proceed with nav as usual! It'll pick up there.
Sometimes the nav can actually route over the ferry crossing as soon as you're right in front of it, but from a far away distance somehow it cannot.Manks bu'j te bange.
-
@Stefan-Hummelink it picked up the route properly on the other side, butI still think this is some kind of an „bug“ as for example Garmin Navigation systems can use ferries as „normal roads and use the automatically.
So, MRA team: take this as a suggestion to implement something, that you can automatically (when it makes sense with the remaining routing settings) use ferries as eventually a special type of road.
Nothing so important, but something for our backlog
Tom
iphone 12 Pro (iOS 18.1)
iPad Pro (iPadOS 18.1)
MyRoute-APP (4.3.3 - 357, Lifetime Gold)
on KTM 1290 Super Adventure R (model 2022) -
@TomOnTour said in Using ferries within the APP:
suggestion to implement something,
Having the app only being able to distinguish skipped and normal waypoints is almost 100% sufficient for this issue and that app-feature will be worked on in the future.
-
@TomOnTour said in Using ferries within the APP:
I still think this is some kind of an „bug“
It is not a bug, but a "not yet implemented" thingy
I have been warning about this on many posts about the "trick".
It will most definitely be added, ETA unknown.
