Dartmouth, in Devon, has two vehicle ferries, the Dartmouth Higher Ferry and the Dartmouth Lower Ferry.
Each of these has bulk purchase concession tickets. I’m new to Waze, but I have a feeling these count as Local Exemptions.
The ferries each have subtly different hours
https://dkfb.co.uk for the higher, and https://www.southhams.gov.uk/dartmouthlowerferry for the lower
How might this be updated into the Waze system, please?
We have not included the frequent user saver voucher discounts due to the number of variations that are used based on how many bulk journeys you pay for, if you pay onboard, mobile, online. A similar reason why prices shown are a single journey price only.
The operating times are already mapped as a restriction to prevent Waze suggesting the route outside the operating times.
Just to confirm the toll price passes do not in any way influence routing, they do not make Waze prefer a ferry route.
I can understand that. But there is a reason for my asking.
With “Avoid Toll Roads” set ON and “Avoid ferries” set OFF Waze does not plan the route by using the ferry. It only uses the ferry when Avoid Toll Roads is set OFF.
Is this something I’m doing or is it a gremlin, please?
You are correct, and raise a valid point, all ferries are mapped with the toll attribute when they charge for the crossing, this is done as they are effectively a short section of toll road and prevents users being given a route which they find they can’t use without making a payment.
Now that we have the ability to show a price in the app this may need reviewing.
I think and hope regular ferry users would appreciate a review of this area. I was so happy to see that I might be able to say “Yes” to ferries and “No” to toll roads, though I recognise that a ferry is a toll, and on the rather wet part of the road
Following some discussion, the UK Champs and Admins agree that ferries should not be mapped as toll roads now we have the ability to show prices in the app…
However, this has highlighted an issue with the system/code Waze uses. To be able to show the price the ferry route has to be mapped as a toll road, without the toll attribute set the app will not display the price. Therefore our only options are to remove the toll attribute and therefore have no prices, or leave mapped as a toll so prices can be shown.
I have asked the wider global community for their thoughts, and if necessary I will raise it directly with the toll pricing team.
A mechanism to solve this might be to allocate the attribute of price to a ferry route in the same manner that it is attributed to a toll road. This would remove the confusion, though require some programming and systems thought.
Do we have any visibility on a possible outcome to your wider community researches, please?
I’m not aware that any wider community has done any wider research, my post in the specific Toll pricing forum got minimal reaction, though a suggestion to improve the functionality was added to Centercode, used by Beta tester and used to be where we could suggest improvements.