Re: [Tagging] bicycle:lanes=designated|... vs cycleway:lanes=lane|...

2015-01-14 Thread Martin Vonwald
2015-01-14 17:02 GMT+01:00 fly : > Am 13.01.2015 um 13:38 schrieb Martin Vonwald: > > When writing the :lanes-proposal I used those tags in an example. But in > > my opinion bicycle:lanes=...|designated|... fits better. > > I was irritated by your example, as well. Maybe, you can rework some > exa

Re: [Tagging] bicycle:lanes=designated|... vs cycleway:lanes=lane|...

2015-01-14 Thread fly
Am 13.01.2015 um 13:38 schrieb Martin Vonwald: > When writing the :lanes-proposal I used those tags in an example. But in > my opinion bicycle:lanes=...|designated|... fits better. I was irritated by your example, as well. Maybe, you can rework some examples and add them to the wiki. At least, mar

Re: [Tagging] bicycle:lanes=designated|... vs cycleway:lanes=lane|...

2015-01-13 Thread Hubert
Well then: +1 to all. No exceptions. Am 13. Januar 2015 14:01:16 MEZ, schrieb Martin Vonwald : >2015-01-13 13:52 GMT+01:00 Hubert : > >> +1 to all. Except "none" in this case was meant to be the default >value >> from the :lanes proposal. >> > >The "default value" is always an empty value, e.g. mi

Re: [Tagging] bicycle:lanes=designated|... vs cycleway:lanes=lane|...

2015-01-13 Thread Martin Vonwald
2015-01-13 13:52 GMT+01:00 Hubert : > +1 to all. Except "none" in this case was meant to be the default value > from the :lanes proposal. > The "default value" is always an empty value, e.g. minspeed=|80|50. The value "none" might be defined by the main key, e.g. maxspeed=none. If the main key do

Re: [Tagging] bicycle:lanes=designated|... vs cycleway:lanes=lane|...

2015-01-13 Thread Hubert
+1 to all. Except "none" in this case was meant to be the default value from the :lanes proposal. Am 13. Januar 2015 13:45:24 MEZ, schrieb Martin Vonwald : >2015-01-13 13:38 GMT+01:00 Hubert : > >> I would not. IMO bicycle:lanes is an access Tag while cycleway:lanes >> defines es the type. So one

Re: [Tagging] bicycle:lanes=designated|... vs cycleway:lanes=lane|...

2015-01-13 Thread Martin Vonwald
2015-01-13 13:38 GMT+01:00 Hubert : > I would not. IMO bicycle:lanes is an access Tag while cycleway:lanes > defines es the type. So one could have cycleway:lanes:forward=none | lane > and bicycle:lanes:forwad= yes | designated , for example. > That's correct. AFAIK it is common understanding, th

Re: [Tagging] bicycle:lanes=designated|... vs cycleway:lanes=lane|...

2015-01-13 Thread Hubert
I would not. IMO bicycle:lanes is an access Tag while cycleway:lanes defines es the type. So one could have cycleway:lanes:forward=none | lane and bicycle:lanes:forwad= yes | designated , for example. Am 13. Januar 2015 13:28:22 MEZ, schrieb Andrew Shadura : >Hi, > >Some places in the wiki menti

Re: [Tagging] bicycle:lanes=designated|... vs cycleway:lanes=lane|...

2015-01-13 Thread Martin Vonwald
When writing the :lanes-proposal I used those tags in an example. But in my opinion bicycle:lanes=...|designated|... fits better. "mass-replace" is a word that might cause some adverse reactions on this mailing list ;-) Have fun, Martin 2015-01-13 13:28 GMT+01:00 Andrew Shadura : > Hi, > > Som

[Tagging] bicycle:lanes=designated|... vs cycleway:lanes=lane|...

2015-01-13 Thread Andrew Shadura
Hi, Some places in the wiki mention cycleway:lanes:* tags, and those are indeed used in a few places (31 uses currently). It seems to me these tags are obsolete and have been replaced by bicycle:lanes:*, is that correct? Should I probably mass-replace them? -- Cheers, Andrew _