<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 04/07/19 20:09, Janko Mihelić wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAA=vpS9xU=OfxThadpdjy-0F=0ckL+arrDbMC2aMWcN2s-FuLA@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=utf-8">
      <div dir="ltr">
        <div>I've been tagging it with an empty amenity=school polygon
          around everything, and then two points with amenity=school +
          name=* + all the other specific tagging. <br>
        </div>
      </div>
    </blockquote>
    <br>
    I too have used similar. <br>
    Usually a polygon/way with one school on it and then a node inside
    it for the other school, or schools if more than one. <br>
    <br>
    <br>
    <blockquote type="cite"
cite="mid:CAA=vpS9xU=OfxThadpdjy-0F=0ckL+arrDbMC2aMWcN2s-FuLA@mail.gmail.com">
      <div dir="ltr">
        <div>But if mapped like that, a data consumer would see 3
          schools. I like your solution with overlapping multipolygons.</div>
        <div><br>
        </div>
        <div>Janko<br>
        </div>
      </div>
    </blockquote>
    <br>
    On one occasion I have separated then into 2 separate ways, I am
    certain that some of each area will be shared from time to time, but
    it seams to be a good compromise. Every other time I have not had
    any reasonable chance of doing this. <br>
    <br>
    Most people would consider amenity=school to be a land use, along
    with other tags such as leisure=recreation_ground. <br>
    <br>
    <blockquote type="cite"
cite="mid:CAA=vpS9xU=OfxThadpdjy-0F=0ckL+arrDbMC2aMWcN2s-FuLA@mail.gmail.com">
      <div dir="ltr">
        <div> </div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">čet, 4. srp 2019. u 09:58
          Martin Koppenhoefer <<a
            href="mailto:dieterdreist@gmail.com" moz-do-not-send="true">dieterdreist@gmail.com</a>>
          napisao je:<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 dir="auto">The one feature page states:
            <div>
              <ul style="margin:0.3em 0px 0px 1.6em;padding:0px">
                <li style="margin-bottom:0.1em"><span
                    style="background-color:rgba(255,255,255,0)">More
                    than one of something on the same site e.g. two
                    schools sharing grounds. Normally if the schools are
                    separate they would have separate neighbouring
                    grounds, but if the only thing defining a separation
                    between two schools is their buildings, then the
                    containing area should be tagged with a suitable <tt
                      dir="ltr"
                      class="gmail-m_-817457083380637591mw-content-ltr"
                      style="direction:ltr;line-height:1.6"><a
                        href="https://wiki.openstreetmap.org/wiki/Key:landuse"
                        title="Key:landuse"
                        style="text-decoration:none;background-image:none"
                        target="_blank" moz-do-not-send="true">landuse</a>=*</tt>,
                    and the buildings tagged individually.</span></li>
              </ul>
              <div><br>
              </div>
            </div>
            <div>from </div>
            <div><a
href="https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element#Examples_of_bad_situations"
                target="_blank" moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element#Examples_of_bad_situations</a></div>
            <div><br>
            </div>
            <div>I don’t believe this is common practice, e.g. there
              isn’t even a landuse value for schools.</div>
            <div>I would rather tag 2 schools with distinct buildings
              and shared grounds as 2 overlapping amenity=school areas
              with the “other buildings” (those of the other school)
              excluded via multipolygon inner roles.</div>
            <div><br>
            </div>
            <div>If we did like currently suggested in the wiki it would
              also loose the information about the grounds (only the
              buildings would result as schools).</div>
            <div><br>
            </div>
            <div>Cheers, Martin </div>
            <div><br>
              <br>
              <div id="gmail-m_-817457083380637591AppleMailSignature"
                dir="ltr">sent from a phone</div>
            </div>
          </div>
          _______________________________________________<br>
          Tagging mailing list<br>
          <a href="mailto:Tagging@openstreetmap.org" target="_blank"
            moz-do-not-send="true">Tagging@openstreetmap.org</a><br>
          <a href="https://lists.openstreetmap.org/listinfo/tagging"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/tagging</a><br>
        </blockquote>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Tagging mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/tagging">https://lists.openstreetmap.org/listinfo/tagging</a>
</pre>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>