<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Totally agree, Eugene.<br>
      Much better with consistent data, with one way to tag a certain
      thing, than to have different processes adapt to incorrect tags,
      regardless of how frequent. Besides, anyone calling McDonalds a
      *restaurant* clearly needs to get out more! :)<br>
      Ronny.<br>
      <br>
      On 25/05/14 04:44, Eugene Alvin Villar wrote:<br>
    </div>
    <blockquote
cite="mid:CAPhqi6LkVu-6MyKB6c59RNadHoEvz8+xv7itm77Ez_oC912BQA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div>
                <div>Hi Mark,<br>
                  <br>
                </div>
                I think it would be better for all users of the data in
                the long run that the inconsistent name field is the one
                corrected instead of your system adjusting for it.<br>
                <br>
              </div>
              Let's say that you have a "rule" that says that that
              name=McDonald's with amenity=fast_food gets the Golden
              Arches icon.<br>
              <br>
            </div>
            Now let's say you have other rules that detect stuff that
            are probably McDonald's: name=McDonalds amenity=restaurant<br>
            <br>
          </div>
          Instead of tagging stuff like this with an additional tag
          icon:ph=mcdonalds.png, it would be better to correct those
          POIs that don't follow the correct tagging. If you have a
          system that detects such near-misses, then I'm sure the
          community would like to get a list of them so that they can be
          corrected.<br>
          <br>
        </div>
        I hope other mappers and users can chime in with their ideas.<br>
        <div>
          <div>
            <div><br>
              <div><br>
              </div>
            </div>
          </div>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Thu, May 22, 2014 at 6:32 PM, Mark
          Cupitt <span dir="ltr"><<a moz-do-not-send="true"
              href="mailto:markcupitt@gmail.com" target="_blank">markcupitt@gmail.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div dir="ltr">Folks, have been thinking about how we
              specify Icons for POI's in the Philippines OSM Map. I have
              Icons for most of the PH specific businesses, like
              Jollibee, Banks, and so on and would like to use them<br
                clear="all">
              <div>
                <div dir="ltr">
                  <div><br>
                  </div>
                  <div>At the moment, the only way to do this is to run
                    through the database checking the name tag and
                    seeing if it starts with jollibee, BDO mcdo, etc.
                    This is a very intensive effort on a million+
                    points. I am doing the code for it now and it has to
                    be run on a very regular basis to pick up new POI'S
                    from the daily diff updates. It also suffers form
                    spelling errors, and fomat errors, for example "the
                    jollibee" will to be identified as the name has to
                    start with "jollibee" (in text string searches in
                    postgres do not use indexes, and are too expensive
                    on the database, so we have to assume that the name
                    starts with the search text.</div>
                  <div><br>
                  </div>
                  <div>I will publish the icons we have at some stage
                    very soon where they can be viewed by anyone.</div>
                  <div><br>
                  </div>
                  <div>To make it very easy to have granular control
                    over icon display, I propose that we do the
                    following:</div>
                  <div><br>
                  </div>
                  <div>Add an icon:ph tag to nodes as they are created
                    that contains the filename of the icon to display
                    (from the list published)</div>
                  <div><br>
                  </div>
                  <div>For example, a node of a Mcdonalds might have a
                    tag amenity="fast_food" name="Mcdonalds Quezon City"
                    and a icon:ph="mcdonalds.png"</div>
                  <div><br>
                  </div>
                  <div>The system will first check if the icon:ph exists
                    and use the icon specified in that. if not, it will
                    fall back to database determined value done on a
                    weekly or monthly basis, with all the inherent
                    pitfalls in the use of the name field. If that does
                    not work, it will display a generic icon which is a
                    Red Dot.</div>
                  <div><br>
                  </div>
                  <div>One big advantage of this proposal is that people
                    can submit their own logos in icon form, they are
                    easy to add to the system, them specify them for
                    specific businesses, leisure, bars, etc. on the
                    actual poi ..so the value added to the map will be
                    tremendous in the future.</div>
                  <div><br>
                  </div>
                  <div>Thoughts, flames, thumbs up, thumbs down, rounds
                    of applause on this proposal very much appreciated
                    ..</div>
                  <div><br>
                  </div>
                  <div>Regards</div>
                  <div><br>
                  </div>
                  <div>Mark Cupitt</div>
                  <div><br>
                  </div>
                  <div>"If we change the world, let it bear the mark of
                    our intelligence"</div>
                  <div><span></span><span></span>
                    <div><br>
                    </div>
                  </div>
                  <div><a moz-do-not-send="true"
                      href="https://www.openstreetmap.org/user/Mark_Cupitt"
                      target="_blank">See me on Open StreetMap</a><br>
                  </div>
                  <div><br>
                  </div>
                  <div><a moz-do-not-send="true"
                      href="http://ph.linkedin.com/in/markcupitt"
                      target="_blank">See me on LinkedIn</a></div>
                  <div><img moz-do-not-send="true"
src="http://s.c.lnkd.licdn.com/scds/common/u/img/webpromo/btn_myprofile_160x33.png"><br>
                  </div>
                  <div><span style="font-family:arial black,sans-serif"><b><br>
                        <a moz-do-not-send="true"
                          href="http://gis.stackexchange.com/users/17846/mark-c"
                          target="_blank">See me on StackExchange</a></b></span></div>
                  <div><img moz-do-not-send="true"
                      src="http://gis.stackexchange.com/users/flair/17846.png"><br>
                  </div>
                  <div>===============================================================================================</div>
                  <div>The contents of this email are intended only for
                    the individual(s) to whom it is addressed and may
                    contain</div>
                  <div>confidential or privileged information. If you
                    are not the intended recipient, you must not
                    disclose, copy, distribute,</div>
                  <div>or use the contents of this email. If you have
                    received this email in error, please notify the
                    sender immediately and</div>
                  <div>delete the email and any attachments.<br>
                  </div>
                  <div>
===============================================================================================
                  </div>
                </div>
              </div>
            </div>
            <br>
            _______________________________________________<br>
            talk-ph mailing list<br>
            <a moz-do-not-send="true"
              href="mailto:talk-ph@openstreetmap.org">talk-ph@openstreetmap.org</a><br>
            <a moz-do-not-send="true"
              href="https://lists.openstreetmap.org/listinfo/talk-ph"
              target="_blank">https://lists.openstreetmap.org/listinfo/talk-ph</a><br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
talk-ph mailing list
<a class="moz-txt-link-abbreviated" href="mailto:talk-ph@openstreetmap.org">talk-ph@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-ph">https://lists.openstreetmap.org/listinfo/talk-ph</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>