That’s the big question. Every route profile adds complexity to the UX as well. Having more choice might not always be better . Having buttons for options that are rarely used is also not great for users.
For routing issues, we created the beeline mode, which is the most flexible way, but you don’t have any guidance on the beeline route part.
Yes, but if many users reply here in the forum this gives us an idea of what is needed either way.
There are still problems though like when the ferry time exceeds the drive time then the Quickest Routing Profile takes you overland. In this example I want to take the ferry and not the tunnel.
I found part of the problem with ferries, Kurviger sees a ferry as a Toll Road which is technically incorrect, ferries are not roads. In my opinion this is a bug. Where / how do I submit a bug report?
Fixing this however will not fix this problem,
There are still problems though like when the ferry time exceeds the drive time then the Quickest Routing Profile takes you overland. In these two examples I want to take the ferry and not the tunnel.
I understand Beeline is Kurviger’s solution. Make what you will of it I just see this as flawed.
Okay seriously, this needs to be my last post in this thread. I know I keep saying that however I keep finding new information to add. Anyway I want to let us both move on since we are not going to change each others minds.
Now, is your expectation, that Kurviger should propose to take the ferry from Newcastle to Haarlem instead routing you over roads and tunnels?
IMHO, if I plan a ride, I’d prioritize the roads and let Kurviger plan the road route.
If I want to cross a big chunk of water, I’d first decide where I want to cross, at what times are ferries available and buy the ticket for that crossing. Then I would plan the ride to the ferry and from the ferry using Kurviger.
Normally I would not have such a big crossing every other day, so it should not be a big issue to plan longer ferry crossing outside Kurviger.
For shorter crossings, the beeline would do the job if the App does not take the ferry and you really wish to.
Does this help solve your problem or am I still missing your point?
I found part of the problem with ferries, Kurviger sees a ferry as a Toll Road which is technically incorrect, ferries are not roads. In my opinion this is a bug. Where / how do I submit a bug report?
Ok. Since I do not use ferries on a dauly basis, I would always check all ferry crossings on my route individually. For some longer crossings like that Oslo-Kiel it is not possible to just appear and buy a ticket - you meed to book in advance since the cabin may be mandatory.
Back to the Kurviger app - based on previous posts I would have following questions for the development team:
How does the App differentiate between the ferries that would be considered for the route planning and those that wouldn’t (but can still be enforced by putting an SP on the line in water)? Example: https://kurv.gr/q5NzA
Why does router assume that the ferry would turn back at SP? Example: https://kurv.gr/dteW7
Why does the router treat some ferry connections as toll roads? Example: https://kurv.gr/f3hRq
None of these are a high priority questions, as I would still plan my ferries individually, but there is obviously some unexpected behavior in the app here.
All ferries I used in Norway are “toll” i.e., I had to pay for them. I guess “free of charge” would be an exception in case of ferries.
If you compare my examples above:
#1 the route is marked as a ferry (but time and distance are inconsistent):
Is there a case where a paid Tunnel is shown as “Toll”, but the tunnel symbol is missing? I’d expect both to be reported in the route information (“i”).
Again, all these are for me “corner cases”, not a high priority. Fix/improve when you can.
yes, interesting:
The hurtigruten (first picture) is just mapped with route=ferry, no key / tag for duration - symbol ferry
Newcastle-IJmuiden (second picture) is marked as route= ferry and toll=yes and duration = 15:30 - no symbol ferry
toll: I found some ferries mapped with toll=yes, others with fee=yes. I do not know the difference.
Reroute from shaping point on ferry route back: Perhaps an idea to assume route=ferry as “oneway”, when a point is set on the ferry route. There might be possibilities to swim back, but I would rather enjoy the ferry ride. No idea, if technical feasible.
Where I live, in Washington State, USA, the ferries are in fact considered roads and carry with them a Washington State Highway designation. Drivers follow a highway (SR-nnn) to the ferry terminal. When on the ferry they are still on SR-nnn and when they get off the ferry on the other side they are still on SR-nnn.