Consider routing over piers to get access to ferries

[rkflx]

If BRouter routed over piers, it would be far easier to use ferries when planning a route. Currently you have to force the route by using a lot of via points (which have to be placed very precisely for them to work, if they help at all), and in some cases routing fails completely (see #264).

Test case

Routing in BRouter-Web (notice missing route segments):

The pier is already mapped, though:

[abrensch]

I see. Seems there were some edit wars on the issue when iD tried to enforce validation rules to add a highway tag in such cases: https://help.openstreetmap.org/questions/69818/should-a-pier-be-tagged-as-highway

Same for railway=platform : openstreetmap/iD#6409

So maybe we should add both as implying highway=footway?

[rkflx]

Sounds reasonable.

[0709wiwiwi]

So maybe we should add both as implying highway=footway?
Yes pse. In my own (flemish) region I tagged them as highway=footway......but there are so many left still not completed.
The Elbe river is famous for this issue. (Some already where corrected in the past but not all of them)

Piers and Ferries.

Brouter.
https://t.ly/kgf_

GraphHopper.
https://t.ly/mshB

OSRM.
https://t.ly/vYw1

Openstreetmap.
https://t.ly/Jduj

[polyscias]

Yes, I think it would be good to add man_made=pier to lookups.dat, the wiki indicates it is a raised walkway over water, see also #416

A problem is maybe that there are many more man_made tags (in ways context) that are not interesting, like storage_tank, cutline, pipeline, silo:

Tag(s)	Way count
man_made=pier	538425 ways
man_made=<other>	2278655 ways

You do not want these other's to be included

Same for railway=platform : openstreetmap/iD#6409

That is tagged 1502 times. the more popular tag is public_transport=platform

Tag(s)	Way count
public_transport=platform	325976 ways
public_transport=<other>	35978 ways

[afischerdev]

Added

man_made=pier
public_transport=platform

to the #416