lanes:bicycle=* and lanes:foot=*
If you want to get specific, like, on a typical major thoroughfare on
Portland's westside on the approach to an intersection, you'd have
something like...
highway=primary
name=Southwest Murray Boulevard
cycleway=lane
lanes:forward=5
lanes:backward=3
bicycle:lanes:forward=yes|yes|yes|designated|yes
motor_vehicles:lanes:forward=yes|yes|no|yes
bicycle:lanes:backward=yes|yes|designated
motor_vehicle:lanes:backward=yes|yes|no
turn:lanes:forward=left|none|none|through|right (bicycle lanes always have
a specific arrow in Oregon, usually through, which can lead to situations
where bicycles are given a through-only option at a t-intersection one-way
to the left; in which people just treat the bike lane as an outside left
turn lane in practice for physical practicality; your mileage and regional
sanity will vary)
Pepper to suit, since postal service and public transit vehicles may
briefly use the bicycle lane as well to load or unload, with something like
psv:lanes:forward=yes|yes|destination.
On Sat, Aug 2, 2014 at 3:06 PM, Janko Mihelić jan...@gmail.com wrote:
2014-08-02 16:00 GMT+02:00 Volker Schmidt vosc...@gmail.com:
Do I need to use lanes tagging for this, which is completely different
form the cycle lane tagging?
I think lanes tagging is the best solution. It will be consistent with
road lane tagging so that renderers, routers and mappers won't have to
discover new schemes. We just need a few more definitions that are targeted
at pedestrians and bicycles.
Janko
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
