For years the danish community has generally been following this recommendation: https://wiki.openstreetmap.org/wiki/Da:Cykelstivejledning on when to use cycleway=track and when to use separate cycleways. I'd like to express the opinion that cycleway=track is NOT bad and actually in many situations is preferable to separately mapped cycleways.
On torsdag den 27. april 2017 10.14.18 CEST Martin Koppenhoefer wrote: > 2017-04-27 9:19 GMT+02:00 joost schouppe <joost.schou...@gmail.com>: > > So not all of the cases are an error, but many of them. > > I would like to come to a common agreement and document that > highway=cycleway on distinct geometry is preferable to having just a > cycleway=track attribute on a road. In the past some of the separate > cycleways I had mapped have been deleted in favor of attributes on the > road. The latter is an inferior representation (IMHO) because: > > 1. it makes it harder to add more attributes to the cycleway (including > maxspeed, surface, turn restrictions, width, access restrictions) > > 2. it makes it unclear or at least much more error prone to determine which > attributes of the road also belong to the cycleway (and vice versa) > > 3. it removes the geometric details (position, shape, unclear position of > things between (or not) the cycleway and the road like grass, guard rails, > telephone booths, poles, crossings between driveways, etc.) > > Therefore I believe we should recommend that fixing duplicates as of this > thread should be done by removing the attribute cycleway=track, not > deleting the highway=cycleway. > > Cheers, > Martin _______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
