If oneway=unknown is not present then it already is implicitly there. Too many tags showing that something is unknown may not be needed.
On Wed, Jun 3, 2015, 6:49 AM Richard <[email protected]> wrote: > On Wed, Jun 03, 2015 at 12:44:13PM +0200, Martin Koppenhoefer wrote: > > > > > > > > > > > Am 03.06.2015 um 12:18 schrieb Richard <[email protected]>: > > > > > > oneway=uknown > > > > > > for the cases where soemone is not sure? Without a possibility to > express > > > that possibility armchair mappers can either stop mapping roads they > dont > > > know or make a mess of the data. > > > > > > armchair mappers without local knowledge are not the preferred source > anyway, but foo=unknown is a really bad idea that should not become > standard. > > > > Otherwise a lot more tags can be added with very few benefit: > > maxheight =unknown > > maxspeed, maxwidth, snowmobile, horse, foot, bicycle, hgv, hazmat, > surface, name, ref, lanes, start_date, width, operator, cycleway, bus, psv, > etc =unknown > > constructive criticism please. You can ridicule whole OSM like this if you > substitute the "unknown" for "no". Nobody is saying that those should be > used on every object but judicious use may be better than the alternatives. > > Better ideas? > > Richard > > _______________________________________________ > Tagging mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/tagging >
_______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
