<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 21/11/22 10:47, François Lacombe
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAG0ygLcN=Xoav+KkQBQE8a0YJHrncJ+3A9OakGwtJ3hD6Y3Tbw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Good evening,<br>
        <br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">Le dim. 20 nov. 2022
            à 17:36, stevea <<a
              href="mailto:steveaOSM@softworkers.com"
              moz-do-not-send="true" class="moz-txt-link-freetext">steveaOSM@softworkers.com</a>>
            a écrit :<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            In fact, I can imagine a variety of tags that describe much
            (approaching or even achieving?) all of this:<br>
            office=utility<br>
            utility=water;sewer;garbage<br>
            utility=accepts_payment<br>
            <br>
            utility=cable_tv<br>
            utility=allows_equipment_exchange<br>
            utility=furnishes_service_equipment<br>
            utility:payment=in_person_only<br>
            utility:payment=kiosk<br>
            utility:payment=cash_only<br>
            utility:payment=accepts_checks<br>
            <br>
            Those aren’t necessarily the exact tags OSM might eventually
            settle upon, but they do indicate what’s possible.  Again,
            it’s a pretty big universe, as “utilities” encompass more
            than power / energy, and there are a vast number of ways to
            “deal with customers at an office.”  (There’s the office
            itself, what sort of services are available, when/whether it
            is staffed (it may be simply a drop-box for payment), what
            sort of services and payments are exchanged…).<br>
          </blockquote>
          <div><br>
          </div>
          <div>utility=* key is already widely used and expect one
            single value, in every situation.</div>
          <div>Please don't introduce utility=power;gas;waste.<br>
          </div>
          <div><a href="https://wiki.openstreetmap.org/wiki/Key:utility"
              moz-do-not-send="true" class="moz-txt-link-freetext">https://wiki.openstreetmap.org/wiki/Key:utility</a></div>
          <div><br>
          </div>
          <div>I've also answered here about its usage in this proposal</div>
          <div><a
href="https://wiki.openstreetmap.org/wiki/Talk:Proposed_features/Power_utility_office#Use_sub-key_instead"
              moz-do-not-send="true" class="moz-txt-link-freetext">https://wiki.openstreetmap.org/wiki/Talk:Proposed_features/Power_utility_office#Use_sub-key_instead</a></div>
          <div><br>
          </div>
          <div>I'm not sure tagging offices with utility=* is really
            suitable for the current definition: offices aren't involved
            in production, transmission, distribution or delivery of
            power, telecommunications, gas, whatever.</div>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <p>Some offices are involved in the sale and administration of the
      utility.</p>
    <p>Buried utilities here were legally required  to be in separate
      trenches, that has changed so that one trench can be used for
      multiple utilities, so it may be required for the key 'utility' to
      accept multiple values. <br>
    </p>
    <p>Many of the present values for the key 'utility' look to be what
      is being discuses for these offices. <br>
    </p>
    <p>The key 'utility' has evolved over time from only  the key
      'marker' to also accepting the tags 'man_made=utility_pole' and
      'building=service'. Further evolution might take place. <br>
    </p>
  </body>
</html>