<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">15 dec. 2020 kl. 08:26 skrev Anders Torger <<a href="mailto:anders@torger.se" class="">anders@torger.se</a>>:</div><br class="Apple-interchange-newline"><div class=""><meta charset="UTF-8" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Verdana, Geneva, sans-serif; font-size: 13.333333015441895px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">And about wasting mapper's time. What about that we have to punch holes and make river areas for rivers nowadays? Punch holes for waters in forest areas?<span class="Apple-converted-space"> </span></span></div></blockquote><br class=""></div><div>Anecdote: When I first started toying with rendering about ten years ago, I had problems with lakes disappearing under forests. I thought it was completely unrealistic to expect mappers to punch holes in forests for lakes, especially as everything looked fine on <a href="http://osm.org" class="">osm.org</a>, so I added a rule that smaller areas always render on top of larger areas. Then the map at <a href="http://osm.org" class="">osm.org</a> changed to requiring holes, and for a very long time most lakes in Sweden had little trees growing on them on <a href="http://osm.org" class="">osm.org</a>. I think most of them have been multipolygon-ized by now.</div><div><br class=""></div><br class=""></body></html>