|
Hi,
Thanks for your time, Peter, and for a message which I feel like the first to want to cooperate. However, I don't feel well how your variants fit with the scenario I am dealing with, namely:
variant2: you are extending the scope to other maps whose authors said they won't support RENDER variant3: you'll never find a solution if it's not used variant4: RENDER is of course not a way to be able to tag x=y render=yes nor to choose colors; mappers are supposed to use defined and appropriate tags. Thinking in the same direction as you did may raise some ideas like this. The lack of rendering may have two reasons that lead to the same idea: 1) lack of time for rendering to follow the tag production rate 2) the tags are just too varied to find similarly varied rendering Both lead to think of classes of objects inside which each new object would be put. If an object has no specific rendering, it would inherit the rendering of its class. For example, getting back to the mini-golf, it could inherit the rendering of the class called "ground", or "park", whatever you prefer but rendered. It can be refined to a proper mini-golf later. In fact, it's nothing more than render=park, but possibly out of user control if that's what hurts. But the big, big problem with new tagging is the OSM theory that each user can invent his own tags and that they look at each other later in hope that they did the same things. That can be compatible with RENDER but certainly not with classes. Well, I said I would stop. I'll let you think. Best regards,
On 2014-08-27 19:09, Peter Wendorff wrote : Am 27.08.2014 um 17:49 schrieb André Pirard:All the replies in this thread showed absolutely no desire to join the fight and make suggestions, just to disparage the idea.I don't agree here. But the way you proposed for this fight is not a solution. It may be if what you call (and many see as) "the default osm map", namely the mapnik, now osm-carto stylesheet, would use the render-tag, but only partly.Let's imagine "the map" would support RENDER. variant 1) people stop using wrong tag to "tag for the renderer", and instead use RENDER=* to get the image they want. This only works partly, as the selection in cases of restricted place on the map cannot be solved. As a result there may be now semantic tagging for new stuff as it's more easy to use RENDER everywhere to get what I want than to propose and discuss new tags. variant 2) people use RENDER, but as render is not sufficient to support garmin maps, osmand, nominatim and others, keep tagging for the renderer to get their features used there as well variant 3) nobody uses RENDER, then it's useless of course variant 4) the best case would be that people use RENDER only on objects where there is no "right" tagging (yet). In this case it slows down tag inventions and clutters the map view by many inconsistent rendering rules, as you add a feature X somewhere in the world and let it be rendered in red, I add a feature X somewhere else and want it to be rendered blue, and some other mapper doesn't care about rendering and adds a feature X without RENDER-tag. Render would even reduce the motivation to invent and "standardize" new tags, as it's not necessary any more to get something new on the map. To summarize: Why do you think RENDER would have any benefit? I mentioned the drawbacks of it: - less motivation to get consensus on new tags - very limited motivation not to tag (wrong) for the renderer any more - inconsistent map views as a result of inconsistent RENDER-tags for the same object types I like the idea to tackle the tagging-for-the-renderer, but all arguments FOR the RENDER-tag I read yet (if I didn't miss any) are IMHO countered by the explanations and assumptions above, feel free to correct me if I'm wrong and add real benefits of RENDER. regards Peter _______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging |
_______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
