2009/11/26 Tobias Knerr <o...@tobias-knerr.de> > All of these tags were previously documented to imply oneway=yes. Now > only the page for highway=motorway_link still contains that implication. > > Generally, I don't think it's acceptable to change the definitions of > tags in this way.
+1 > > I also wonder how we should deal with this specific situation. Can we > still assume any default oneway information for *_link values (whether > it's yes or no) or is oneway=yes/no a required second tag for *_links? > > no, IMHO we shouldn't generally "imply" but tag explicitly, otherwise consistency is at risk. > Should an application developer decide to assume oneway=no (which might > lead to longer-than-optimal routing results) yes, oneway=no is the default for all streets unless explicitly stated. Even for motorways I wouldn't assume oneway=yes (it could still be that a motorway is not yet mapped as dual carriage-way). cheers, Martin
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
