kentsmith9 wrote: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.
I don't understand b) staying in your vehicle. Why does that matter?
If you're sat in the vehicle during the crossing, then there's a chance you'll have Waze running and it'll be collecting data, etc. On large ferries where you leave your car, then there's not much point keeping Waze running is there? On a 5-6 hour crossing from France, I'll probably be asleep and the battery wouldn't last that long anyway.
The 'stay in your vehicle' guideline is mainly a way to distinguish between small ferries (which are typically on a short, fixed route and regular crossings) and large ferries (which tend to be much longer and more variable, with fewer crossings).
kentsmith9 wrote: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.
I'm not sure if the drive merge process uses just the start/end points, or if it attempts to snap to the geometry along the length of the segments. If there happens to be a node in the middle of a ferry crossing, then it's unlikely to collect any useful timing data.