<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Feb 7, 2020, at 7:48 PM, Peter Elderson <<a href="mailto:pelderson@gmail.com" class="">pelderson@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 18px; 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="">If area=yes is added to say a leisure area surrounded by a hedge, that is a mapping mistake. If that results in the area displaying as a hedge area, the mapper has to correct that, not the renderer.</span></div></blockquote></div><div class=""><br class=""></div><div class="">exactly!</div><div class=""><br class=""></div><div class="">If I want a hedge around a tennis court, I draw a hedge around a tennis court. </div><div class=""><br class=""></div><div class="">if a traffic island has a large triangle shaped hedge, then I draw a large triangle shaped hedge with area=yes. </div><div class=""><br class=""></div><div class="">Mappers can’t mix area and way tags on the same object if they depend on area=yes to define what they are. </div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>