> Gesendet: Dienstag, 16. Januar 2018 um 13:06 Uhr > Von: "Mateusz Konieczny" <matkoni...@gmail.com> > An: "Christian Müller" <cmu...@gmx.de> > Cc: tagging@openstreetmap.org > Betreff: Re: [Tagging] Sidewalks and cycleways as tags vs as extra lines > > On Tue, 16 Jan 2018 11:17:31 +0100 > "Christian Müller" <cmu...@gmx.de> wrote: > > > cycleway=* and sidewalk=* should be marked deprecated/legacy, > > in favor of the colon variants. > > I strongly disagree, cycleway=opposite is for example easier to use > than cycleway:left=opposite that carries no useful additional > information (and in many cases people using this tagging scheme > use :left :right incorrectly what needs to be cleaned up).
No, cycleway=opposite is actually harder to use. Without the wiki documentation noone knows what this actually means, it is not self- explanatory. Besides, using a value "opposite" for this is actually a sloppy shortcut for saying cycleway=yes cycleway:oneway=-1 https://wiki.openstreetmap.org/wiki/Tag:cycleway%3Dopposite and https://wiki.openstreetmap.org/wiki/Tag:cycleway%3Dopposite_lane instruct the reader to use those for oneway streets only (without any information to which side (or sides) of the oneway street it applies), while https://wiki.openstreetmap.org/wiki/Tag:cycleway%3Dopposite_track does not require the presence of a oneway street to use it!? If the suffixes :left, :right, and :both are used, they precisely state which side of the road a tag value applies to, independently of that value /and/ independent of the presence and value of a oneway tag in combination, making this approach more versatile and hazzle-free. All lanes or tracks described with :left or :right suffixes may need clarification on the direction of traffic flow. But why is it current practice to mix this information with the type and location of the cycleway itself? For example, the tag value opposite_lane is a mixture of two different tags, which becomes apparent when compared to the tag sets used on separate, parallel cycleways/ sidewalks, if present. So indeed cycleway:left=opposite_lane is very useful. It says that there is a cycling lane to the left of the osm way where cyclists run in the opposite of the direction which would normally be expected for this lane in the respective country. If we are to keep this semantic density for convenience and because it is "established tagging practice" it may be nice to supplement the existing values, i.e. opposite_* forward_* both_* You see there are three possible values for direction of traffic flow (just as for oneway=* of course), so currently it is wrong to assume that the values opposite_lane and lane unambiguously describe all possible real world cases (because you cannot know if lane means forward_lane, this is: the strict opposite of opposite_lane, _or_ a lane in which both directions of traffic flow are allowed). Greetings cm _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
