<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div style="16px" text-align="left">5 Jun 2019, 19:55 by martin@templot.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div style="16px" text-align="left">But on the OSM standard map, the common boundary is shown as a bold green line, which bears no relation to anything on the ground and could be misleading for visitors.<br></div></blockquote><div style="16px" text-align="left"><div style="16px">Note that maps are not aerial images - there is often significant level of abstraction and<br></div><div style="16px" text-align="left">especially for borders there is often nothing visible on the ground.<br></div><div style="16px" text-align="left"><br></div><div style="16px" text-align="left">This rendering was used as compromise between several different problem.<br></div><div style="16px" text-align="left"><br></div><div style="16px" text-align="left">Note also that the same styling applies to all nature reserves across the world.<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div style="16px">Is there a better way to map this?<br></div></blockquote><div style="16px">There are two nature reserves there, right?<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div style="16px"> If I combine them as a single nature reserve<br></div></blockquote><div style="16px">sounds like tagging for the renderer - <a href="https://wiki.openstreetmap.org/wiki/Tagging_for_the_renderer">https://wiki.openstreetmap.org/wiki/Tagging_for_the_renderer</a><br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div style="16px">Is there a way to show the common boundary less prominently?<br></div></blockquote><div style="16px">This is on side of renderers. This one has repository at<br></div><div style="16px"><a href="https://github.com/gravitystorm/openstreetmap-carto/">https://github.com/gravitystorm/openstreetmap-carto/</a><br></div><div style="16px">where proposals to improve it or pull requests with code improving it may be submitted.<br></div><div style="16px"><br></div><div style="16px" text-align="left">Though again, the same rendering rules are applied globally, and for every single one<br></div><div style="16px" text-align="left">there are cases where it fails horribly. Improving one specific place may have really bad <br></div><div style="16px" text-align="left">results elsewhere.<br></div><div style="16px" text-align="left"><br></div><div style="16px">On the data side - I would consider tagging borders on the shared way (mapping boundaries<br></div><div style="16px" text-align="left">as multipolygons), currently each nature reserve is a separate way.<br></div><div style="16px" text-align="left">https://www.openstreetmap.org/way/694760748#map=17/52.37217/-2.28169<br></div><div style="16px" text-align="left"><br></div><div style="16px" text-align="left">(it would not change rendering, at least on default OSM map)<br></div></div><div style="16px" text-align="left"><br></div> </body>
</html>