Am 29.08.2014 um 09:58 schrieb Xavier Noria: > On Fri, Aug 29, 2014 at 9:43 AM, Peter Wendorff > <wendo...@uni-paderborn.de> wrote: > >> +0.5, as UIs are decoupled from the data in OSM. You may write your own >> editor with a completely different UI, even one that doesn't know about >> oneway at all, so reasoning on UI preferences may help to get the best >> default, but not to derive rules from. > > Agreed. > > That was a way to say: if you reset the values in the database to have > no NULLs, and change the semantics of NULL to mean strictly "unknown", > not all is lost regarding convenience of data entry. iD (to put an > example) can still choose to preselect "no" for streets. Nowadays it > has a list of stuff for which "yes" is assumed: > > https://github.com/bhousel/iD/blob/master/js/id/core/oneway_tags.js > > And you increase certainty. I fear you don't. For the list you linked this is true as most ways are oneways, but in general it is dangerous. A user must be aware that he explicitly states "this way is oneway" (that is the case already due to the small arrows iD paints on the ways) or "this way is no oneway" (which is invisible, as it is the same visual appearance than no oneway tag at all).
If you don't set the tag as a default, everything is fine as nobody accidentally sets it to a wrong value. If you set it to oneway=no by default, people will start to accidentally tag oneway=no, which results in wrong information in contrast to missing inforation we have no. Of course: if you could make people aware of the tag and make sure 99% of the ways are intentionally (!) tagged with yes or no, then it's fine, but I doubt it. regards Peter _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
