<!DOCTYPE html>
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <b style="font-weight:normal;"
      id="docs-internal-guid-304e8531-7fff-9490-2ffd-ed4a74f3ece0">
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">As I posted </span><a
href="https://www.mkgmap.org.uk/pipermail/mkgmap-dev/2024q4/034350.html"
          style="text-decoration:none;"><span
style="font-size:11pt;font-family:Arial,sans-serif;color:#1155cc;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;-webkit-text-decoration-skip:none;text-decoration-skip-ink:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">here</span></a><span
style="font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;"> on 2024.12.01, I was having issues with POIs not displaying labels for some garmin devices (specifically the XT2 and Tread) when generating /img files using mp file input to mkgmap.  I did some exploration and discovered this (maybe well known but not by me):</span></p>
    </b><b style="font-weight:normal;"
      id="docs-internal-guid-304e8531-7fff-9490-2ffd-ed4a74f3ece0">
      <ul
        style="margin-top:0;margin-bottom:0;padding-inline-start:48px;">
        <li dir="ltr"
style="list-style-type:disc;font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;"
        aria-level="1"><p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"
        role="presentation"><span
style="font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">Each device model displays POIs differently (i.e., type 0x100 does not show the same thing). There seems to be no consistency across models (Felix echoed this in a follow-up post).</span></p></li>
        <li dir="ltr"
style="list-style-type:disc;font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;"
        aria-level="1"><p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"
        role="presentation"><span
style="font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">Each model displays labels for each POI type differently (some show no label, others show small vs big text).  There seems to be no consistency across models.</span></p></li>
        <li dir="ltr"
style="list-style-type:disc;font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;"
        aria-level="1"><p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"
        role="presentation"><span
style="font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">I attempted to use the custom "[_point]" feature of the mp files and mkgmap but the custom point bitmaps only work for some garmins.  Even then, it didn't help with my missing [poi] labels.</span></p></li>
        <li dir="ltr"
style="list-style-type:disc;font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;"
        aria-level="1"><p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"
        role="presentation"><span
style="font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">Prior to the labels not working on the XT2 and Tread units, I always used the 0x1400 POI code type for my labels.  With a lot of cross-model experimentation I discovered a single POI code (0x1E00) will display large text on all garmin models I was able to test with (Montana 6XX and 7XX, XT, XT2, Tread).  I have no idea if this POI code will work with all garmins that support custom maps.</span></p></li>
      </ul>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">Questions:</span></p>
      <ul
        style="margin-top:0;margin-bottom:0;padding-inline-start:48px;">
        <li dir="ltr"
style="list-style-type:disc;font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;"
        aria-level="1"><p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"
        role="presentation"><span
style="font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">Are these issues with each model behaving differently with respect to POI types well-known?  If so, how are they gotten around by (OSM) map builders?  How can a single map be built that has POIs and labels that are consistent across more than one device.  What am I missing?  </span></p></li>
        <li dir="ltr"
style="list-style-type:disc;font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;"
        aria-level="1"><p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"
        role="presentation"><span
style="font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">How does OSM handle this?  I presume that an OSM map generated for an area works on all garmin devices?  I will admit that I don't know what the OSM map limitations are across garmin models.  Does the JOSN model allow the devices POI maps to be loaded on a per-map basis?  If I were to switch to JOSN model for mkgmap input, could I get around all the device limitations I am running into with the mp file format?  Can someone recommend a good tutorial on getting up to speed on generating JOSN for simple map input to mkgmap?</span></p></li>
        <li dir="ltr"
style="list-style-type:disc;font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;"
        aria-level="1"><p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"
        role="presentation"><span
style="font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">OSM uses the JOSM model to feed mkgmap.  Does that model allow for more flexibility and control than the "mp" input file model?  I presume the MP file format is obsolete.</span></p></li>
        <li dir="ltr"
style="list-style-type:disc;font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;"
        aria-level="1"><p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"
        role="presentation"><span
style="font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">Is there any better documentation for the MPO format than the CGPSMAPPER pdf file floating around on the internet?</span></p></li>
        <li dir="ltr"
style="list-style-type:disc;font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;"
        aria-level="1"><p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"
        role="presentation"><span
style="font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">Can anyone recommend either a different website or people whom I may contact for further help with any of this?</span></p></li>
      </ul>
      <br>
      <p dir="ltr"
        style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">Any and all help is appreciated.</span></p>
    </b><br class="Apple-interchange-newline">
  </body>
</html>