<div dir="ltr"><div>Daniel, I don't know about standardization of rendering, but I would say the advice on the wiki is followed by OSM mappers much more often than some veterans think.<br><div> <br></div></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">2014-07-08 20:05 GMT-03:00 Daniel Koć <span dir="ltr"><<a href="mailto:daniel@xn--ko-wla.pl" target="_blank">daniel@xn--ko-wla.pl</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
W dniu 08.07.2014 20:04, yvecai napisał(a):<div class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
However, if rendering is an interesting topic, wiki is full of<br>
rendering examples and advices that aren't followed anywhere. Let the<br>
</blockquote>
<br></div>
You don't even realize how sad is this observation for me...<br>
<br>
What is the role of writing documentation than - and approving it or declining? You can always use the tags as you like it, and they will be rendered this way or another (or not a all), so why waste the time proposing and documenting?<div class="">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
renderer render and the cartographer style the map, and trust them to<br>
understand tags of interest to them.<br>
</blockquote>
<br></div>
You have no choice but to trust external rendering services - they will do what they think is important anyway. And we show this trust by OSM license.<br>
<br>
But inside the project I think we need some more coherency. If there's an approved proposal with rendering hints, at least the default render should take it into account. Ideally I think all such features should be rendered - and if not, the documentation should be revised by rendering team explaining what is the problem. Eventually the consensus can be reached. Otherwise, if OSM is basically the GIS database, why the main project page has the map instead of big red "Download the data!" button?<br>
<br>
In my case it was as simple as taking the template and filling it up. "Rendering" section in this template (and the field in the proposition infobox) means it's not unusual that the tagging can have rendering implications. And I see the difference in scale of peaks type, which should be properly visualised to not make default map cluttered with unnecessary details (like <a href="https://github.com/gravitystorm/openstreetmap-carto/issues/689" target="_blank">https://github.com/<u></u>gravitystorm/openstreetmap-<u></u>carto/issues/689</a> ). But I just gave rough idea - the rendering team may feel some other settings would be better.<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Mambałaga</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
______________________________<u></u>_________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" target="_blank">https://lists.openstreetmap.<u></u>org/listinfo/tagging</a><br>
</div></div></blockquote></div><br></div>