> > Personally, I have no problem with oneway=yes having different > implications depending on the value of the highway key. In general I > would expect the oneway value to align the predominant use of the > highway in question. > > More specifically: > > - I would expect a oneway=yes tag apply to foot traffic on footway. > No. There are thousands of footways with bicycle=yes|official|designated to make them mixed foot-cycleways
- I would also expect a oneway=yes tag to apply to foot traffic on > pedestrian, path, and cycleway -- unless explicitly nullified with a > oneway:foot=no tag. > No. There are thousands of pedestrain, path, cycleway with bicycle=yes|official|designated to make them mixed foot-cycleways - I would not expect a oneway=yes tag to apply to foot traffic on > track, service, unclassified, residential, or any larger roadway, unless > made explicit with a oneway:foot=yes tag. > OK Of course I understand that from a data consumer's point of view it's > irritating when a tag has different meanings in different contexts -- > especially if these differences are not formally documented. > It also drives the mappers mad Volker
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
