<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div data-marker="__HEADERS__"><blockquote style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;" data-mce-style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>De: </b>"scott taggart" <taggart@taggarts.org><br><b>Para: </b>"mkgmap-dev" <mkgmap-dev@lists.mkgmap.org.uk><br><b>Enviados: </b>Sábado, 7 de Diciembre 2024 17:10:19<br><b>Asunto: </b>Re: [mkgmap-dev] Update on missing POI Labels on some devices and some questions...<br></blockquote></div><div data-marker="__QUOTED_TEXT__"><blockquote style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;" data-mce-style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><div class="moz-cite-prefix">On 12/7/2024 11:59 AM, osm wrote:<br></div><blockquote cite="mid:342282d1-3107-4982-8719-dde0eeab1ecd@pinns.co.uk"><p>You're a bit 'confused'</p><p>It's not OSM that determines the visibility of types but the Garmin device itself . </p><p>mkgmap creates maps based on osm data and 'feeds' devices with maps. It's up the each device to accept part or all of the map. So in your case , much of the data gets ignored and falls on death ears, ie it's eclectic <br></p></blockquote><br> Confused and ignorant at this point, for sure!<br><br> Now nderstood that OSM just outputs its contents (in .osm format, correct) to be rendered by mkgmap into a .img file. My central question is still: "do OSM maps largely work across all garmin devices, including the newer XT2 and tread, including having basic text labels"? Assuming "yes" for the moment, where is the secret sauce in mkgmap that generate universally displayable text labels? Does the .osm format pass enough "style" info to mkgmap for it to construct TYP files and POI references that work across most garmin units?<br><br> Scott<br></blockquote><div><br></div><div>OSM "only" provides geographic data and does not have nor pass nothing with respect to the style to mkgmap or to any other map generator.</div><div><br data-mce-bogus="1"></div><div>The "secret sauce" in mkgmap is hidden in the styles and typ files, which most of them are created after hours and hours of trial and error, and checking which device show which types and how they show them. Most authors of mkgmap compiled maps distributes their maps for free, and got feedback from their users and (with some luck and mostly effort) maps get improved in every release, not only because the OSM data gets updated, but also because mkgmap has been improved, and also some maps get more and more specialized. Maybe you can learn more digging in the svn of mkgmap for changes in the default styles, or in the code from some authors that have their tool chain in github. Some old docs here <a href="https://www.cferrero.net/maps/maps_index.html">https://www.cferrero.net/maps/maps_index.html</a> and a list of providers here <a href="https://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/Download">https://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/Download</a><br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>Most of the time the investigation is done using synthetic osm files (not real data, but data specially crafted to be able to see how a map work in a device), which POIs are shown, which categories, etc. etc.<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>Regards.<br data-mce-bogus="1"></div><div>M.<br data-mce-bogus="1"></div></div><div id="sconnect-is-installed" style="display: none;">2.15.1.0</div></div>
<br><!doctype html>
<html>
<head>
<meta charset="utf-8">
<title>Documento sin título</title>
</head>
<body>
<p class=MsoNormal>---------------------------------------------------------------------------------------------------------------------------------------</p>
<table border="0" cellspacing="0" cellpadding="0">
<tr>
<td><a href="https://crm2.montevideo.com.uy/trazabilidad/servlet/aredirect1?LPhdB6L%2FWNhVZs6SLZxphQ%3D%3D"><img src="https://imagenes.montevideo.com.uy/imgnoticias/202105/760489.jpg" width="245" height="100" alt=""/></a></td>
<td width="20"></td>
<td><p class=MsoNormal>Factura Electrónica de Montevideo COMM
<br>
La instalación más rápida de todo Uruguay
<br>
<a href="https://crm2.montevideo.com.uy/trazabilidad/servlet/aredirect1?LPhdB6L%2FWNhVZs6SLZxphQ%3D%3D">Informate aquí.</a>
</p></td>
</tr>
</table>
<p class=MsoNormal>---------------------------------------------------------------------------------------------------------------------------------------</p>
</body>
</html>
<br></body></html>