<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><br><div dir="ltr"><br><blockquote type="cite">On Feb 28, 2020, at 12:58 PM, Warin <61sundowner@gmail.com> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><a href="#" class="_AppleShowQuotedContentButton"><div style="height: 59px !important; overflow: hidden !important;"><blockquote type="cite" cite="mid:A1D0D969-8FAF-4930-8FF6-F12AA766D904@mac.com" preoffsettop="1062" preoffsetheight="280"><pre class="moz-quote-pre" wrap="">this would interfere the least with existing mapping. </pre>
</blockquote></div></a><blockquote type="cite" cite="mid:A1D0D969-8FAF-4930-8FF6-F12AA766D904@mac.com" preoffsettop="1062" preoffsetheight="280" style="display: none;">
<pre class="moz-quote-pre" wrap="">normally mapped Ways & areas could be tagged with outdoor_event:highway=pedestrian or outdoor_event:amenity=parking (or whatever it is during the event) to show their role during the event - yet be mapped normally the rest of the time - and added as regular members of the relation.
this would interfere the least with existing mapping. </pre>
</blockquote>
<pre>I think existing mapping would ignore the tagging completely.</pre></div></blockquote><br><div>If people are tagging for the renderer by naming Landuse features or amenities the name of the festival or event, then they are interfering with proper mapping. </div><div><br></div><div>If I draw a big sand polygon out in the desert and name it “Burning Man” - it really isn’t a sandy area named that. There isn’t a park named “Summer Festival” A scheme that integrates with existing mapping would cause the least mapping for the renderer. </div><div><br></div><div>Javbw. </div></body></html>