<div dir="ltr">On Thu, 11 Feb 2021 at 14:40, Robin Burek <<a href="mailto:robin.burek@gmx.de">robin.burek@gmx.de</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div>Am 11.02.2021 um 14:34 schrieb Paul
Allen:</div>
<blockquote type="cite">And
people get to see both icons on the map.</blockquote>
<p><span lang="en"><span><span>I
am sorry, your answer violates several good practices</span></span></span>:<br></p></div></blockquote><div><br></div><div>I am sorry, but it is your proposal that violates several good practices. <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><p>
</p>
<ol>
<li>One feature, one OSM element -> This is one shop - so it
has to get one Objekt! </li></ol></div></blockquote><div>These are two different features within one building. This is not a single</div><div>node with several features, which is what you are proposing.<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><ol><li><a href="https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element" target="_blank">https://wiki.openstreetmap.org/wii/One_feature,_one_OSM_element</a></li></ol></div></blockquote><div>There is absolutely nothing in that which prohibits two nodes in close</div><div>proximity representing two different features. Or nodes within a building</div><div>representing sub-features, such as elevators.<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><ol>
<li>Tagging for the randerer -> You tag multiple nodes for one
shop to make it visible on the map. <a href="https://wiki.openstreetmap.org/wiki/Tagging_for_the_renderer" target="_blank">https://wiki.openstreetmap.org/wiki/Tagging_for_the_renderer</a></li></ol></div></blockquote><div>I am tagging WHAT IS THERE IN REALITY. It has the side-effect of being</div><div>rendered in a useful way. It would be correct tagging if neither icon were</div><div>rendered and it is still correct tagging when both are rendered. The fact</div><div>that when I tag reality it is rendered in a useful way is a pleasant</div><div>benefit that most people would interpret as being an additional reason</div><div>to map reality.<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><ol>
</ol>
<p><span lang="en"><span><span>That
is exactly why I propose this proposal.</span></span> <span><span>Because
there is currently no way to represent something like that.<br></span></span></span></p></div></blockquote><div>And yet there is. In any shop I'm aware of in the UK that offers a post office</div><div> service the counter is physically separated by barriers from ordinary shop</div><div>counters. One counter handles postal services and nothing else.</div><div>One or more counters handle non-postal services.<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><p><span lang="en"><span><span>
We can really discuss what information we can give to an
renderer or how a renderer can display this, but to create
multiple nodes for one object is against our own rules.<br></span></span></span></p></div></blockquote><div>I have not done this. You, however, wish to use a single object to</div><div>represent multiple things and it appears you want to do this because you</div><div>don't like maintaining two sets of opening hours. You may be surprised</div><div>to learn that, in the UK, a post office counter within a shop often</div><div>has more restrictive opening hours than the shop itself.<br></div><div><br></div><div>-- <br></div><div>Paul</div><div><br></div></div></div>