[Tagging] RENDER

[André Pirard]

On 2014-08-15 16:12, André Pirard wrote :
> It's a well known fact that many people complain to tag in vain
> because what they tag doesn't show on the map (e.g. mini-golf vs
> tennis pitch), because they're told to open a rendering ticket which
> replies that only official tags are supported, and because they open a
> vote for an official tag and nobody signs.
> As a result they are accused of "tagging for the renderer" instead of
> 'being forced to tag for the renderer".
>
> The solution is simple however.  A RENDER tag that, typically, would
> assign a color to an area.
> I'll let the rendering specialists define what else it can do.
> ⚠ ⚠ ⚠ RENDER only requests *by default* rendering.
> As soon as rendering is defined for an element, it is used instead and
> RENDER is normally ignored.
As you can read it, my goal is simple: stop people tagging for the
renderer by making their tagging visible on OSM.org standard map despite
a -- hopefully temporary -- lack of rendering definition.
You people focused on the choice of multicolor by the mappers to shoot
this suggestion down while there is no multicolor and not even a choice
needed at all: a single color chosen by the renderers suffices.  Hence,
the applauded smarties box mockery is ridiculous as smarties of the same
color every 50 cm make a funny present box and tagging for the renderer
makes a better looking one regarding color anyway.
On the other hand, to address another critique, RENDER can indicate that
it means that the feature is considered important either only for the
standard map or for some other categories of maps.

Pragmatically, open OSM.org and search for "mini golf"
<http://www.openstreetmap.org/search?query=mini%20golf>.  Clicking on a
result will show you the feature highlighted single color. RENDER would
render it much the same way on the normal map, but dim.
Now if the tourist returns to the normal maps, and he can or he cannot
see what he has just found, depending on its tagging for the renderer or
not. Look, dear, they say that showing our mini golfs would "break the
model of decoupling the factual mapping database from the data consumers
and their choices".
Let us try Google or Michelin maps instead, they may copy OSM data and
show it.

On one hand I advocate happy mappers tagging features that RENDER can
show and happy renderers that can make statistics of RENDER usage to see
what rendering definitions are the most needed.  As soon as a new
rendering definition is made, all the features auto-magically use it.
Should abuse of RENDER be found, an invisible rendering can be defined
for the feature.

On the other hand, you advocate unhappy mappers tagging useful features
for the renderer in order to not tag in vain.  The process is much out
of control and, should a rendering definition appear for some or those
features, the tagging already done will remain in the "for renderer",
smarties like state.

You might have a better idea or improve mine instead of disparaging it.
Up to you.
This will probably be my last message.

André.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20140825/823c52c3/attachment.html>