[Tagging] Feature Proposal - RFC - (Obligatory vs. optional cycletracks)

[fly]

As we have tags for different kind of *lane the only problem is
cycleway=track.

Now we have two solutions:

1. deprecate cycleway=track in favour of cycleway=*_track
2. add a new key like bicycle_track=*

My two cents

fly

Am 22.12.2014 um 12:30 schrieb Hubert:
> The need to distinguish between obligatory and optional cycle ways
> isquite common. Right now it’s done by distinguishing between
> bicycle=official/designated and bicycle=yes or bicycle=officialand
> bicycle=designated/yes.
> 
> In a similar way, I think it is better to use something like
> bicycle=obligatory instead of cycleway=optionalsince it is more of an
> access problem, than a type problem.(I alsodon’tlike
> cycleway=opposite)After all the only difference is where one may or must
> ride. The cycle way itself does look the same, except for the missing sing.
> 
> OnMontag, 22. Dezember 2014 02:20Ulrich
> Lamm<___ulamm.brem at t-online.de_<mailto:ulamm.brem at t-online.de>> wrote:
> 
>> Hi all,
> 
>> 
> 
>> I've written a proposal for the tags cycleway=obligatory and
> 
>> cycleway=optional.
> 
>> 
> 
>> Now I hope for your comments.