As per the encouragement from HQ we have mapped ferry prices in the UK, however this has highlighted a confliction with how users expect the app to behave. For prices to show in the app the ferry segment has to be mapped with the toll attribute set.
When a user wants to avoid ferry routes they must toggle the option in the app, this allows them to avoid ferries but continue to be offered toll roads. For users that are happy to use ferry routes must ensure both avoid ferries and avoid toll roads are toggled off, this is not obvious to users.
Avoid Toll off / Ferry on - Waze avoids ferry routes - correct
Avoid Toll on / Ferry off - Waze avoids ferry routes - wrong
Avoid Toll on / Ferry on - Waze avoids ferry routes - correct
Yes users have to pay to use the ferry but this is not seen as a toll road as you must make a conscious decision to board a ferry and therefore expect to pay for this service. Am I missing anything obvious :?:
They could change the routing algorithm to ignore the toll flag on the ferry routes, but then they may argue that they would be providing a toll route to someone who explicitly asked for a toll-free route.
I would still agree with you that what you say is a more desirable configuration, but it’s just not supported by Waze at the moment out of the box (you can’t tell Waze: please avoid the toll on the freeway 1 but allow the toll on freeway 2).
So I guess that unless Waze decides to change that, you’ll have to explain the issues to the users every time.
Are there ferry routes anywhere that are free? That would complicate things even more. Then you need something like ferry on, ferry on even if toll (that ignores the toll settings for ferry segments) , ferry off. This would actually just be one simple setting change with no side effects in other components (it only affects the routing request).
