Is there a list somewhere that documents the undocumented rules, pitfalls and hidden traps in making maps for Garmin?
Something I recently tripped over and spent a lot of time trying to figure out was where I had a map built that looked as expected on qmapshack, but some of the roads did not show up as expected on my Garmin Montana. I would change the element type for a way, but it wouldn’t show up as expected on the garmin. The problem was that I had another map on the garmin that I had built that was on the device, and it seems like the TYP data from that one was being used instead of my new one.
The other item I don’t understand is the various names. I don’t use mapsource or sendmap, I use qmapshack and use the OS to copy maps to the device.
The various names don’t show up on the Garmin. The --description shows up as the map name on the Montana. There is a 2nd map name line shown for some maps which I didn’t build which I’d like to use if I could figure out how.
Does family ID have to be unique, ie not conflicting with other maps on the device? This may be related to my issue above?
I don’t think FID is the key. I have 2 maps with different FID that don’t show up in the garmin map list and 2 with the same FID (Openfietsmap) that do show up.
My OS is linux, so many of those tools don’t work, bu from GMapTool there is a cmd line tool,
Here’s the output for the 2 maps, where only 1 shows up.
gmt v0.8.220.853b CC BY-SA (C) 2011-2015 AP www.gmaptool.eu
File: cco.img, length 2247680
Header: 02.12.2018 19:47:31, DSKIMG, XOR 00, V 1.00, Ms 0
Map length s-f CP prio PID FID name
MAKEGMAP MPS 73 1
00030001 IDX 30388 2
00TYP001 TYP 34814 1 1252 1 30001
63240001 MPC 2167991 5 1252 20 1 30001 cco
F: PID 1, FID 30001, famname
V: OSM map set (0)