<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix"><b style="font-weight:normal;"
id="docs-internal-guid-7b10aa9d-7fff-2137-105b-2a9e519ffa6d">
<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;">Thanks everyone for the input. If I understand correctly, there seems to be no universal POI types across all devices (when I look at some of the referenced lists, there seems to be a small bit of consistency with the 0x01...0x11?) types. However, as I have seen in practice, some of the newer devices such as XT2/Tread seem to not even follow these "standards" (the XT2 and Tread definitely do not display text for the well-known 0x1400 type). In my particular case, I need (only) one POI type that will always display a big text label and ideally, no icon (I'm settled for now on 0x1E00 which seems to work across all devices I care about (until garmin releases some new device)). At the risk of repeating what I have previously asked, can anyone explain to me:</span></p>
<br>
<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;">Assuming there's no consistency across devices, how do the OSM generated maps work across devices? Do they not? (I'm not an OSM expert by any means). How the heck does OSM always know a text label will be displayed on every device for a given POI type? When OSM maps are generated does the creator specify a device type so that internal OSM type maps can be used (sorry for my ignorance of how OSM works). In thinking more about this, does OSM generate a TYP file that defines custom point types for all needed icons so they work across all devices? Seems like that is the only way any of this could work.</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;">Even more perplexing, does this mean that garmin must release different versions of maps for each device class (say a US topo)? I never buy garmin maps so maybe I have missed this. When I look </span><a
href="https://www.garmin.com/en-US/p/127633#requirements"
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;">online to buy the garmin 100k topo</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;">, it seems it works for all devices.</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;">Finally, and I asked this before, is there any mkgmap capabilities I can get to using the .osm input as opposed to the mp file format (assuming I generate TYP files)? I ask this because I want to potentially save myself from trying to dive very deep into the non-mp file stuff if there's nothing to be gained.</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;">And finally, just to vent here, why in God's name would a manufacturer ever create such a mess??? Seems like a real headache even for them, let alone us reverse-engineers ;)</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;">Thanks again for your patience. As you can tell, I am a blind man stumbling around in a dark room here.</span></p>
</b><br class="Apple-interchange-newline">
On 12/7/2024 8:07 AM, osm wrote:<br>
</div>
<blockquote type="cite"
cite="mid:c5483407-f3e0-4b5b-8960-9160f53da7c7@pinns.co.uk">I
agree with Ticker; there is also something else which MAY help:
<br>
<br>
If your Garmin came with maps its worth checking which points do
show up.
<br>
<br>
A TYP file may be included into the gmapsupp which will should
reveal
<br>
some of the types used - Gmaptool can export this supfile
<br>
<br>
Regards
<br>
<br>
Nick
<br>
<br>
On 07/12/2024 15:52, Ticker Berkin wrote:
<br>
<blockquote type="cite">Hi Scott
<br>
<br>
There is some consistency across Garmin models I've come across
for a set of
<br>
standard POIs that have a (semi-)defined meaning; but I don't
know if Garmin are
<br>
breaking this with devices like XT, Tread...
<br>
<br>
By semi-defined I mean they respond to appropriate 'FIND'
searches and some
<br>
devices actually show what considers the POI to be. There are
various lists of
<br>
these around the internet and, from a mkgmap distribution,
<br>
./examples/styles/default/points shows usage.
<br>
<br>
Sticking to these can make a reasonably well-featured map that
works on many
<br>
devices.
<br>
<br>
Many POI types don't show at low resolution!
<br>
<br>
For the POI you've mentioned, I've noted from experimentation:
<br>
0x14 No icon. Country. Big font. no subtypes {major
country}
<br>
0x1e No icon. has name. State {province/region}. no subtypes
<br>
<br>
I don't think you get any difference in the final map and
behaviour whether the
<br>
input is MP or from OSM (osm.pbf, o5m, etc format)
<br>
<br>
<a class="moz-txt-link-freetext" href="https://www.mkgmap.org.uk">https://www.mkgmap.org.uk</a> > Documentation is a starting point
for help.
<br>
<br>
Ticker
<br>
<br>
<br>
On Fri, 2024-12-06 at 10:47 -0800, scott taggart wrote:
<br>
<blockquote type="cite"> As I posted here on 2024.12.01, I was
having issues with POIs not displaying
<br>
labels for some garmin devices (specifically the XT2 and
Tread) when
<br>
generating /img files using mp file input to mkgmap. I did
some exploration
<br>
and discovered this (maybe well known but not by me):
<br>
* Each device model displays POIs differently (i.e., type
0x100 does not
<br>
show the same thing). There seems to be no consistency across
models (Felix
<br>
echoed this in a follow-up post).
<br>
* Each model displays labels for each POI type differently
(some show no
<br>
label, others show small vs big text). There seems to be no
consistency
<br>
across models.
<br>
* I attempted to use the custom "[_point]" feature of the mp
files and mkgmap
<br>
but the custom point bitmaps only work for some garmins. Even
then, it didn't
<br>
help with my missing [poi] labels.
<br>
* Prior to the labels not working on the XT2 and Tread
units, I always used
<br>
the 0x1400 POI code type for my labels. With a lot of
cross-model
<br>
experimentation I discovered a single POI code (0x1E00) will
display large
<br>
text on all garmin models I was able to test with (Montana 6XX
and 7XX, XT,
<br>
XT2, Tread). I have no idea if this POI code will work with
all garmins that
<br>
support custom maps.
<br>
<br>
Questions:
<br>
* Are these issues with each model behaving differently
with respect to POI
<br>
types well-known? If so, how are they gotten around by (OSM)
map builders?
<br>
How can a single map be built that has POIs and labels that
are consistent
<br>
across more than one device. What am I missing?
<br>
* How does OSM handle this? I presume that an OSM map
generated for an area
<br>
works on all garmin devices? I will admit that I don't know
what the OSM map
<br>
limitations are across garmin models. Does the JOSN model
allow the devices
<br>
POI maps to be loaded on a per-map basis? If I were to switch
to JOSN model
<br>
for mkgmap input, could I get around all the device
limitations I am running
<br>
into with the mp file format? Can someone recommend a good
tutorial on
<br>
getting up to speed on generating JOSN for simple map input to
mkgmap?
<br>
* OSM uses the JOSM model to feed mkgmap. Does that model
allow for more
<br>
flexibility and control than the "mp" input file model? I
presume the MP file
<br>
format is obsolete.
<br>
* Is there any better documentation for the MPO format than
the CGPSMAPPER
<br>
pdf file floating around on the internet?
<br>
* Can anyone recommend either a different website or people
whom I may
<br>
contact for further help with any of this?
<br>
<br>
Any and all help is appreciated.
<br>
<br>
<br>
_______________________________________________
<br>
mkgmap-dev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a>
<br>
<a class="moz-txt-link-freetext" href="https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a>
<br>
</blockquote>
_______________________________________________
<br>
mkgmap-dev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a>
<br>
<a class="moz-txt-link-freetext" href="https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a>
<br>
</blockquote>
_______________________________________________
<br>
mkgmap-dev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a>
<br>
<a class="moz-txt-link-freetext" href="https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
</blockquote>
<br>
</body>
</html>