I am not really sure what this article is trying to say. Like Mateusz, I object to the line -
... "Important is that every mapper does not only note if the object or quality he has searched for is there, but also has to note if it is not there." There is wide agreement that many objects have default values, Mateusz mentions Oneway and Toll on ways. Lets not make the database any bigger than it need be to specify data that has a default. I don't understand what sort of "structural element" might exist on one side or the other of a road and a mapper cannot determine which ? I agree that "tagging for the renderer" is not always inherently evil (but can very easily be so). Certainly, exercising our rights to make up tags can be fun but unproductive and I generally agree with that block of text. And what follows. So, is it fair to say that this article is urging better interaction between mappers and renders ? I'd support that but I am afraid I don't find the article clearly leads me there. Problem is, IMHO, in the early parts of the article, its a distraction. David On Thu, 2014-12-18 at 15:28 +0100, Ulrich Lamm wrote: > https://wiki.openstreetmap.org/wiki/User:Ulamm/Mappers,_evaluators_and_feedback > > This article is an attempt to write down basic rules of/for OSM > that had been forgotten to fix in the very beginning. > > I had started that page with an invitation on the discussion page to do the > move now done by Frederik Ramm, if anybody would disagree. > As you can see, there was a considerable discussion. > > Therefore I dared to remove the original invitation after a month. > > If now still somebody considers anything of this short text wrong, please > tell it. > > Ulrich > > > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging