[Tagging] cycleway:lane=advisory

[Paul Johnson]

On Tue, Feb 2, 2021 at 7:23 AM Tobias Zwick <osm at westnordost.de> wrote:

>
> Option 1:
> ------
> Use a subtag to define what kind of cycleway=lane it is in more detail.
>
> This is done almost everywhere. type of bollards, type of surveillance,
> type of artwork, of memorial, of recycling, of bench, of doctor, etc
> etc. etc.
>
> This is the least invasive approach. Data consumers who are just
> interested in a lower level of detail, f.e. only process that there is a
> doctor, but not what type of doctor; only process that there is a cycle
> lane but not what type - are not affected.
>

I like this one.  Mostly follows the KISS principal.


> Option 2:
> ------
> Deprecate cycleway=lane because it is ambiguous and migrate to
> cycleway=exclusive_lane and cycleway=advisory_lane instead.
>

Which ultimately isn't a value add versus motor_vehicle/access:lanes=yes/no
combined with bicycle:lanes=designated/yes

To my mind it seems like a dedicated bicycle lane is much more concisely
handled with the rest of lane tagging.  Just give it access:lanes=no
bicycle:lanes=designated for a reserved lane (traditional or buffered),
access:lanes=yes bicycle:lanes=designated for a shared lane, and perhaps
both yes or a no and a yes for an advisory lane.  This seems much more
accessible and flexible for data consumers since the two most important
parts, who can use it and where on the road it is, are presented up front.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20210202/fac2159b/attachment-0001.htm>