On Tue, Dec 15, 2009 at 12:47 AM, Anthony <[email protected]> wrote: > > I have to really doubt that 90% of ways tagged with path > are "probably unsuitable for any traffic other than pedestrian". Maybe 90% > are unpaved, but unpaved does not mean "unsuitable for any traffic other > than pedestrian". And there's already a tag for surface=paved/unpaved. > That's my problem with the current usage. We shouldn't have a tag for > surface=unpaved and a second tag for highway=surface_probably_unpaved.
+1 >> highway=cycleway only used for well-engineered & public/permanant cycle >> tracks (ie could you safely do 20kph on it) > > This could work too, with perhaps a jurisdiction-specific definition only > for cycleway. Shouldn't "jurisdiction-specific" labels be applied if desired with designation=*? (http://wiki.openstreetmap.org/wiki/Key:designation) > My only two (relatively small) problems are 1) something > needs to be done quickly about inconsistent data like bicycle=path + > surface=concrete/paved/asphalt/etc or bicycle=footway + > surface=grass/ground/sand/unpaved/etc, before it gets too out of hand. This only happens when tag definitions are made more complex than they need to be. _______________________________________________ Tagging mailing list [email protected] http://lists.openstreetmap.org/listinfo/tagging
