From OpenStreetMap Wiki
Jump to navigation Jump to search

cycleway:lane=doorzone says

  • 37% advisory
  • 22% exclusive
  • 13% shoulder
  • 13% doorzone

Since this tag hasn't gone through a proposal process, we are left with two conflicting "in use" tagging schemes.

cycleway:lane=doorzone has been used to mark out cyclelanes which are within the doorzone of parked vehicles (shorthand for parking:lane:parallel). This is independent of advisory/exclusive so we need a way to tag both. --Aharvey (talk) 03:32, 3 May 2020 (UTC)

Well, I do not exactly know what shoulder and doorzone is actually used for. Anyway, there is a problem with these two: Whether the cycle lane is in the doorzone is a property of a cycleway lane (like "width", "smoothness", ....) rather than a different type of cycleway lane.
Documenting these as viable options is problematic, because encouraging to use these values amounts to redefining the advisory and exclusive tag values. For example, if someone documented highway=narrow_residential to mean residential streets that allow only one car to go through, it would be a redefinition of highway=residential because then, it implicitly narrows the definition of highway=residential to only residential streets that are wide enough: Suddenly, it would be unknown for all highway=residential whether they have simply not been retagged to highway=narrow_residential yet or if they are really wide enough. This'd be a really bad situation.
By documenting cycleway:lane=doorzone, you create a similar situation for cycle lanes because you implicitly changed the definition of cycleway:lane=advisory and even cycleway:lane=exclusive to only those advisory and exclusive cycle lanes that are either wide enough or separated enough from the parking lane.
It is reasonable of course to record the information whether cycle lanes are in the doorzone of parking cars or not, but the "type of cycle lane tag" is the wrong place in my opinion, it should be an own tag, like cycleway:lane:doorzone=yes, cycleway:lane:parking_lane_spacing=0.0 or something like that. --Westnordost (talk) 12:19, 3 May 2020 (UTC)
Also, note that doorzone is just used 252 times (so about 4%), as opposed to 2022 times for advisory and 2271 times for exclusive (You have to look at left and right too) --Westnordost (talk) 12:27, 3 May 2020 (UTC)
I'm just documenting tags that are currently in use, so don't agree that this is redefining anything (after all the cycleway:lane=doorzone tag was in use before this wiki page was created), you're right there is an inherent problem with this tagging but that already exists as the tag is used in the database, and documenting this doesn't change that. Moving forward we can work out what's the best way to tag all of these things, through a formal proposal process. I've raised a discussion on the tagging list as a starting point. The tag I'm liking so far from that discussion is cycleway:lane:doorzone=yes/no/buffered similar to what you've mentioned here and leave cycleway:lane=advisory/exclusive. So once there is some consensus we can put together a proposal, hope it's approved by voters and then update the wiki accordingly. Fair point about my numbers missing :left and :right, I didn't think of that. --Aharvey (talk) 12:56, 3 May 2020 (UTC)

How to distinguish advisory and mandatory lane in a doorzone?

How to distinguish advisory and mandatory lane in a doorzone? Mateusz Konieczny (talk) 08:15, 22 January 2021 (UTC)

Same issue as above, I agree tagging doorzone in cycleway:lane leads to conflict, so I don't recommend tagging this way. See proposal Proposed_features/Key:cycleway:doorzone--Florimondable (talk) 17:09, 6 February 2021 (UTC)