[mkgmap-dev] Update on missing POI Labels on some devices and some questions...

Mon Dec 9 16:42:55 GMT 2024

M,

Thanks for you input.  I will dig deeper into mkgmap source code.

For what it's worth, I'd love to see some feedback from anyone in the 
OSM/mkgmap community regarding the XT2 and Tread devices and whether 
OSM->mkgmap generated maps are working properly (specifically text 
labels).  I'm curious if there will have to be some re-working  of 
mkgmap to accommodate these devices.

Scott

On 12/8/2024 6:24 PM, muralito at montevideo.com.uy wrote:
>
>     *De: *"scott taggart" <taggart at taggarts.org>
>     *Para: *"mkgmap-dev" <mkgmap-dev at lists.mkgmap.org.uk>
>     *Enviados: *Sábado, 7 de Diciembre 2024 17:10:19
>     *Asunto: *Re: [mkgmap-dev] Update on missing POI Labels on some
>     devices and some questions...
>
>     On 12/7/2024 11:59 AM, osm wrote:
>
>         You're a bit 'confused'
>
>         It's not OSM that determines the visibility of types but the
>         Garmin  device itself .
>
>         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
>
>
>     Confused and ignorant at this point, for sure!
>
>     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?
>
>     Scott
>
>
> 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.
>
> 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 https://www.cferrero.net/maps/maps_index.html and a list 
> of providers here 
> https://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/Download
>
> 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.
>
> Regards.
> M.
> 2.15.1.0
>
> Documento sin título
>
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> <https://crm2.montevideo.com.uy/trazabilidad/servlet/aredirect1?LPhdB6L%2FWNhVZs6SLZxphQ%3D%3D> 
> 	
> 	
>
> Factura Electrónica de Montevideo COMM
> La instalación más rápida de todo Uruguay
> Informate aquí. 
> <https://crm2.montevideo.com.uy/trazabilidad/servlet/aredirect1?LPhdB6L%2FWNhVZs6SLZxphQ%3D%3D> 
>
>
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>
>
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20241209/bea08525/attachment.html>