Custom map-works on 650 and in mapsource but wont show in basecamp

If you created a Garmin "custom map" (.kmz file), then that is not compatible with any Nuvi. These files only work on newer Garmin outdoor/handheld devices like the Oregon, Montana, Dakota, GPSMap 62s, etc.

This kind of map also doesn't show on the dropdown map list in basecamp. It is treated separately and can be displayed in basecamp at the same time as regular Garmin maps (.img files).

I'm afraid you're out of luck. The Nuvi just isn't compatible with this type of map file.

-Boyd

The device i have is a Montana 650. The map works fine on this and i forget how i did it now but was installed on my old pc and showed in mapsource. As it won't show on basecamp by plugging the Montana into the windows 7 pc; can i install on the pc to show? The file extension is the same as my other maps on the sd card. thanks

What is the file extension? Is it .kmz or .img?

If .img it should be read by Basecamp. If not use JaVaWa'a Device manager to make it visible http://www.javawa.nl/jdm_en.html

If .kmz it should show in Basecamp. It can then be dragged into any of the Basecamp folders. If for some reason it can't and you have it saved somewhere on your PC just use Basecamps Import function.

If it's a "custom map" made with a .jpg, I'd wager it's a .KMZ file....

When the unit is connected, you should see the custom map in the "Data View Pane." ~ If you "receive from unit" this converted .jpg map should appear as a "custom map object" in the receive list. (Those custom maps are not .img maps. They are .KMZ files. You should also be able to locate these ".KMZ file maps" in the \Garmin\CustomMaps directory. (If you also have a microSD chip, it might be located on the chip, in the same directory.)

PS: There was (maybe still is in 4.2.5) a bug in Basecamp 4.2.4 where a custom map could stop displaying properly.... Somehow these "received" map .KMZ files could/would stop displaying properly in Basecamp after multiple "receives." (You'd see an "empty square" outlining the maps overlay region, but no image was displayed.) And the properties (right click on the "empty image overlay border" and select properties) of this "corrupted custom .kmz map" indicated the image files were 0 in size.... The way to (temporarily) "deal with this" is/was to delete all shortcuts (and the map object itself) in Basecamp. ~ Then connect the unit & receive it back in...

If this was the issue, Once you get the map into Basecamp, I suggest you: Rename this map object (in Basecamp) & leave it alone so that this "copy" of the map will not be corrupted with subsequent receives.....
(The cause of the corruption may be due to other issues, and not the receive process. That was my assumption. - It could also be due to the auto-backup routine (fixed in 4.2.5), or possibly from relocating/dragging & dropping folder/lists/objects.)

FYI: Much effort went into fixing some "seemingly but not random" data loss/corruption that was occurring in Basecamp 4.2.4. Some type of "auto-save" feature was recently added to Basecamp. And when this routine was "triggered" (based on time lapse)..... If a user was working with the data (at the same time), the "auto-save" routine (a "behind the scenes" process you don't notice) may have been the culprit.

If it's a "custom map" made with a .jpg, I'd wager it's a .KMZ file....

Me too ... but you never know :)