AndyPoms wrote:Waze has stated that they are working on ways to support Ferry (Fairy) properly. I suggest waiting to write this page until their system comes out.
Also, I've seen serious problems when a Ferry is mapped here in CT - which is why none of ours are mapped at this time.
There are GPS traces that run across Long Island Sound and they get REALLY wide in the middle (just about 5000 meters wide = ~3 miles). I don't think Waze will snap users to that.
I think we need some plan for these routes. Other countries are supporting them now and I get the impression they are working at some level.
Sounds like you saw problems. Can you give a quick summary of the issues for those who may not have seen the threads, or point to the main forum entry that discussed the problems you saw?
Why does not snapping to the route suggest we don't draw it in? I would think having something spanning the water to enable Waze to route across is better than it always suggesting go around or no route possible.
CBenson wrote:I agree that the suggestions, except the suggestion to use parking lot road type make sense.
I also agree the parking lot road type is a problem, but I am not sure it matters what we use from the standard list of routing roads. Seems it should match the road types on either side, but calling it a freeway does not meet the current definitions.
Timbones wrote:Need to add some guidelines about when to map a ferry. Our general rule-of-thumb is to only map ferry crossing where you a) can buy a ticket on arrival, rather than pre-booking, and b) you stay in your vehicle during the crossing. None of the major Channel crossings meet either of these criteria, and so should not be mapped. The GPS tends to vary wildly too, making Waze pretty useless.
I don't understand b) staying in your vehicle. Why does that matter?
I don't use ferries so I don't understand the multiple comments around the GPS varying and how that matters if the start and end are hard known points along the short to link the road between.