6 Series map file details

Following an update to V 9.0 and a map update via Garmin Express Ive seen a hike in battery consumption and a long load time for maps on starting the watch. Id like to delete the map and associated files not pertinent to my area (UK/Europe).

1. Could someone kindly let me know which Disc Images relate to which maps? I recognise that gmaptz is the time zone map and gmapski is the ski map but the others Im not sure of.

2. Should you delete the corresponding GMA file when deleting the image file?

3. I seem to have a GMA file with no corresponding image file: 0933045096.GMA any idea why that should be 

  • If I delete some maps, can I reinstall them using garmin express , I won't lose these maps?

  • Yes,  you won't loose these these maps. You can reinstall them with Garmin express.

  • Sorry for my reply, maybe i am stupid. I still dont understand this procedure.

    1. I manualy errase all of .img and .GMA files from windows explorer.

    2. then manualy paste img and GMA files of the first map back. then second map etc ....

    But where I find this files of the new version of maps, if I dont want to use garmin Express to download new maps?

  • If device space saving is not an issue, but rather  "playing" with map files, an option might be not to delete those, but rather moving whatsoever .IMG/GMA files "out of sight" on the device itself.
    For example, create a directory "garmin.hide" on the same level as the "garmin" directory , just under "Primary" or anywhere else *NOT* under Primary\Garmin.
    As experiments showed, the Garmin runtime just looks to what's in or below the "garmin" directory.
    This approach avoids lengthy copying of files to/from the device thru USB. Moving is fast, and moved files are always at hand easily being restored.

  • Do you know if by deleting the maps I can save some battery usage when I run activity? Or better just turn them off in the settings ? When the maps are loading at startup does that means they use more memory on the device and maybe more batter power ?

  • Yes, this I know.

    but I need slowly whole procedure. Sorry for my stupidness.

    1. connect watch via USB

    2. find Garmin and move ALL .img and .gma files to (for example) HIDE file as you wrote.

    3 than I have to reset watch or not?

    4. than again connect cia USB and paste back files img and .gma to Garmin? All files in one step, or one by one and after each reset watch?

    5. is there any file, which to paste back from HIDE as the first file? or no matter which file as first?

    6. can I paste back only one map? or is there any neccessary files, that has to be paste back?

    How can only this mooving of files help?

    Thanks for your time.

  • as of 2.) Move all: I never tried that. Would guess that's OK. My "best practice" is to target special img/gma pairs. Thread here has information on "mapping " (sic!) map file name to (supposed) map content.

    as of 3.) Reset: Probably.  I'm always doing one. A soft reset like How to do a soft reset? will do. Depending on the size and number of the maps in \Primary\Garmin the subsequent restart might take an awful long time (30 min or so). I interprete that as some kind of indexing takes place after map constellation has been changed.

    as of 4.) You could do that, I guess. But again (as 2.) I prefer/recommend to move "well known" gma/img file pairs only.

    as of 6.) yes. but semantics of "one map" is: the xxx.img + xxx.gma files both. I never tried otherwise. And no, just the gma and the img, nothing else. After a restart you might consider reviwing/configuring navication related activities and enable/disable some maps.

    And: All the information here is to my own knowledge and experience, but on own risk.

  • I am not native English, sorry. I can't get idea what exactly to do to solve 'slow map' issue? Could you explain one more time with simplified step-by-step list what to do? Appreciate your help! Thank you!

  • Its all explained in the verified answer from Oliv1381 above, in summary it was concerning the golf course maps and particularly the DEM file which once deleted solved the issues