<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hey Ben and others,<div><br></div><div>Yep, spot on, rendering hints but only related to zoom levels. I realise that it's matter of opinion what roads to be rendered at what levels etc and why rendering hints are not considered "factual data" and not preferred.</div><div><br></div><div>Changing the road classification is an option but are likely to cause side effects. For example, tagging what is a territory road as a primary so that it will be rendered earlier on in the zoom level has the potential of polluting the data, making it less useful for other purposes such as routing etc. </div><div><br></div><div>Another positive of the rendering hints approach is that the tags themselves are completely optional so it's up to the rendering engine to take advantage of them. If ignored, it's like they</div><div><br></div><div>Also these tags are only really needed in more regional / outback areas, such as the Great central rd, Tanami track, French line etc so it's lightweight and won't add much size to the database.</div><div><br></div><div>I plan to start a new project for mapping off road and regional areas of Australia and these rendering hints will certainly make a huge difference in rendering. There are already quiet a few of interested in this project and was planning to start a new project page on the Aus Wiki to coordinate this effort. We were hoping to include the rendering tags among the guild line and hope you guys agree.</div><div><br></div><div>Li</div><div><br></div><div><br><div><div><div>On 01/11/2012, at 3:31 PM, Ben Kelley wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p>Hi.</p><p>I think tagging for the renderer is a bad idea.</p><p>Essentially you are talking more about render hints, but I think that becomes a matter of preference pretty fast. Especially when OSM data can be rendered in a number of ways.</p><p>I think it is worth considering what about a road makes you want to render it as a different type of road.</p><p> - Ben Kelley.<br>
</p>
<div class="gmail_quote">On Nov 1, 2012 3:01 PM, "Li Xia" <<a href="mailto:lisxia1982@gmail.com">lisxia1982@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><span style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><font color="#232323" style="">Hey everyone, have an idea about map rendering and want to get your thoughts.</font><div style="">
<font color="#232323"><br></font></div><div style=""><span style="line-height:19px"><font color="#232323">One of the challenges is in rendering a useful map for recreational use is displaying roads, tracks, trails and to some degree water lines at appropriate zoom levels in more remote regions where the density is lower compared with urban regions.</font></span></div>
<div style=""><span style="line-height:19px"><font color="#232323"><br></font></span></div><div><font color="#232323" style=""><span style="line-height:19px">In my opinion, most map service online services or offline vector engine experience the same issue. Here are some illustrations of the issue, by comparing Google / OSM / Raster map of the same region:</span><br>
</font><div style=""><font color="#232323"><br></font></div><div><font color="#232323"><a href="http://www.mud-maps.com/li_temp/1211/Screen%20Shot%202012-10-25%20at%204.42.31%20PM.png" target="_blank">Google</a></font></div>
</div><div style=""><br></div><div><font color="#232323"><a href="http://www.mud-maps.com/li_temp/1211/Screen%20Shot%202012-10-25%20at%204.42.26%20PM.png" target="_blank">OSM</a></font></div><div style=""><br></div><div><font color="#232323"><a href="http://www.mud-maps.com/li_temp/1211/Screen%20Shot%202012-10-25%20at%204.42.22%20PM.png" target="_blank">Raster map</a></font></div>
<div style=""><br></div><div style=""><font color="#232323"><div style=""><font color="#232323">As you can clearly see, at that zoom level, there's no deal on either OSM or Google maps, where as the raster map is useful. yes you can zoom in on Google or OSM, but with a smaller viewing port, orientation is more difficult and you loose that overview which is try handy for trip planning.</font></div>
<div style=""><font color="#232323"><br></font></div><div style=""><font color="#232323">By using a tag specific for rendering purposes, this issue can be overcome. Rendering engines can take advantage of these tags to "optimise" rendering of various regions.</font></div>
<div style=""><font color="#232323"><br></font></div><div style=""><font color="#232323">The tags are fairly self explanatory. By tagging a road with render_as:trunk, this feature can be rendered at the same zoom level as a trench road. Each class of road will have it's own tag so if a highway:territory should be rendered at the same zoom level as a primary, then tag render_as:tertiary.</font></div>
<div style=""><font color="#232323"><br></font></div><div style=""><font color="#232323">What do you guys think?</font></div><div style=""><font color="#232323"><br></font></div><div style=""><font color="#232323">Cheers </font></div>
<div style=""><font color="#232323"><br></font></div><div style=""><font color="#232323">Li.</font></div></font></div></span>
</div>
<br></div><br>_______________________________________________<br>
Talk-au mailing list<br>
<a href="mailto:Talk-au@openstreetmap.org">Talk-au@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/talk-au" target="_blank">http://lists.openstreetmap.org/listinfo/talk-au</a><br>
<br></blockquote></div>
</blockquote></div><br></div></div></body></html>