Thread: Zumo mapping naming

Thank you all. I have made some more experiments and can confirm what Neil said: the original post and wiki entry are correct (except gmapprom1.img doesn't work with the 660) and no additional img files can be used on my Zumo 660.

@ lolypop000: I have tried both *1.img files and they don't work for me.

@ Neill: gmapprom1 is 9 characters and all other Garmin file names are max. 8, so that is already unlikely to work. I tried it anyway...

@ Roger:
1) No, I'm one version behind, as the new version doesn't have any fixes applicable to my unit (language).
2) Initially not. I have found that this base map interferes with the display of OSM maps when zoomed out. Since you suggested it I tried it anyway.

So, thanks to all for your hints. I went the Mapsource way and this would have worked, had we been able to get to Malaysia. A funeral got in the way.

Kind regards,
Peter.

@Beddhist
Sure, 'gmapprom1' is 9 characters. But it works in the closely related nuvis, and so does the 7 character 'gmapoem' file name [as it does in your zumo]. 8 characters is not a strict requirement either as a mimimum or a maximum in Garmin devices. My [limited] experience with zumos confirms gmapprom1 to be a naming convention for at least some zumos also.

Your reported results with your 660 are different to aeon_flux's results with that of his 550 which he has confirmed against the unit's Inventory page map description names. However, expectedly this is the detail map image file naming which is common to both units:

On unit:
gmapoem.img [not selectable/de-selectable]
gmapsupp.img
gmapprom.img

On SD:
gmapsupp.img only (with no 2nd image available as with older nuvis such as 2xx/W, 465 & 7xx which with latest fw can use both gmapsupp.img and gmapsup1.img in the SD Garmin folder).

Additionally as reported by aeon_flux, gmapprom1 works on 550 in unit memory. Your practical experience is that it doesn't work in your 660, however have you checked the map descriptions in the Inventory page? It's a bit confusing because the map description in that page often doesn't actually intuitively line up with the file name [i.e. Suppmap=gmapsup2.img , Suppmap1=gmapsup.img , PROM2=gmapprom1.img] but here's a likely summary, variable by unit as to naming and location of file, of what might work:

Description in Inventory page = File name

Basemap = gmapbmap.img [Inventory description & File name is common to all Garmin units]

Suppmap1 or Suppmap = gmapsupp.img [File name is common to all Garmin units]
Suppmap or Suppmap1 = gmapsup2.img internally in some units
Suppmap = gmapsup1.img in Map folder of some units [e.g. nuvi 1xxx>], = gmapsupp.img in media card of others

PROM = gmapprom.img [some units], or
PROM 1 = gmapprom.img [some units]
PROM 2 = gmapprom1.img [present only if PROM 1 is present as gmapprom.img]

Dir DB = gmapoem.img [not selectable/deselectable and sometimes doesn't appear in Map Info]

TZMap = gmaptz.img [time zone map, not in all units]

I've compiled the above from memory so it may be incorrect or incomplete, constructive criticism correcting my uncertain recollections is welcome please everyone

Additionally, although not shown in Inventory, described in GarminDevice.xml as '<name>NMaps<name>, anyname.img [e.g. 'CNNTAUNZ2014.10.img'] will work in a Map folder either in root of unit or microSD with modern nuvis from 1xxx onwards [but not in your zumo].

This is aeon_flux's experience with his zumo 550:
SD:
Suppmap = gmapsupp.img [ditto for you]

ZUMO device:
Suppmap1 = gmapsupp.img
Suppmap = gmapsup2.img
PROM = gmapprom.img
Dir DB = gmapoem.img (not selectable...)


Your 660's working internal files [so far, based on your info]:

gmapsupp.img
gmapprom.img
gmapoem.img (not selectable/de-selectable as you've found, [and it may not be even visible in Map Info depending on the actual map])

Additionally, you're stated that none of the file names gmapsup1.img , gmapsup2.img or gmapprom1.img works for you in the unit's Garmin folder which if correct indicates that your 660 supports only 3 detail maps in the unit memory. You also haven't said if you have checked the Inventory page yet. It is unlikely in my experience that your unit is actually limited to 3 detail maps as you've found. I think it should also support a 4th map, file named as either gmapsup2 or gmapprom1.

So can you [or anybody else with a zumo 660] check the Inventory Page and report what it shows?: Press and hold the battery symbol for ~6 seconds>Next>Start Test>More and look what map descriptions you have there.

Additionally, as a cross-check you could load up your unit's Garmin folder with images using all the possible map names using maps previously proven as working images. If need be, download a few little detail maps from here such as Raratonga. Use all five possible files names [gmapoem, gmapprom, gmapsupp, gmapprom1, gmapsup1 and gmapsup2 [only one of the last 3 can possibly work, very unlikely gmapsup1 or 2 will imo, but likely that gmapprom1 will]. Carefully note which map is named what. Put a sixth known map in the SD as well. Next look what's showing in the Map Info screen and check that against what's showing in the Inventory page. That's the definitive and ultimately undeniable test provided you are sure the map images are proven to work. You could check any new downloads named as gmapsupp.img in the SD first to prove they work.

Please post the results.

Well, I'm a bit stunned. I've known for a while that they would do incomplete or meaningless changelogs when it suited them of course [only got to look a GarminExpress for a recent example of that for 'weasel-words' instead of a proper Change History]. But to not crow in the changelog about adding support for a second sd map is very surprising to me which is why i didn't go looking for it.

It's not that I didn't believe you, but i had to check for myself. Searching for 67 2E 6D 2E 61 2E 70 2E 73 2E 75 2E 70 2E 31 [2E as Joker] in Hex Editor XVl32 with 6x0 fw V4.50 yields naught. In V4.70, 4.80 & 4.90 there are about 5 hits for gmapsup1.

Can't find it in the latest 4x0/5x0 fw V5.00 though.

PS: If your customers/clients are so feral, it's no wonder you are always such a cheery soul !!

I've done it. Here is the inventory:



Double surprise for me, these are the file names:

Code:

Please Login or Register to see the links

I don't know why the gmapprom1 didn't work for me during the first testing, but it does now.

The big surprise is the gmapsup1, which works only in the SD card.

Hint for others doing this kind of research: you can see at a glance in the folder which files have been recognised and which haven't. The unit creates .sum files for each recognised file.

Thank you all for your help. I guess I better go and update the wiki now.

Regards,
Peter.

I copied your post here
[Only registered and activated users can see links. ]

Do you have any errors starting zumo?
Do you have other routable maps covering the same area in zumo?
Install

Code:

Please Login or Register to see the links

and see if it gives good suggestions too.

There is a maps tiles limit, I looked with Google and found 2025 maps tiles limit for zumo 550,
that's why you should look at what jdm suggests.
Edit:
Limits are 4GB for the map file size and 1000 mp3 songs