MapInstall

I don't believe it's that unusual, indeed Garmin sell some models with both installed. If there's space they should both fit and work fine, I have multiple maps on my nuvi.

What is confusing is how the mapset has been named, and I'm not sure what that means. Have you tried the trick I posted of using mapinstall to send the NA mapset to a sd card? Or indeed viewing the map using Basecamp? It may all be there and simply be a naming anomaly in Map Info?

It's possible its a naming issue but on my 1490T I get TWO entries for CN NA NT 2013.40: "Lower 49" and the name I give to Alaska/Canada/Mexico. My bet is that the maps are partial for whatever reason.

I'd run MapInstall again and double check before transferring that the entire map is selected.

I don't believe it's that unusual, indeed Garmin sell some models with both installed. If there's space they should both fit and work fine, I have multiple maps on my nuvi.

Well that's encouraging.

What is confusing is how the mapset has been named, and I'm not sure what that means.

[nods] I agree. That's why I was hoping Falagar would answer as I assume he should know (I'm also assuming he's a he!).

I'm puzzled as to why MapUpdater churns for so long, thinks it's installed the NA map but hasn't. Maybe I'll ask about that in another section.

Have you tried the trick I posted of using mapinstall to send the NA mapset to a sd card? Or indeed viewing the map using Basecamp? It may all be there and simply be a naming anomaly in Map Info?

No but it's on my next-things-to-try list, thanks for the suggestion. I'm really glad I tried to do this now rather than just before our trip. (Edit: To clarify, I'm going to try installing it on another memory stick then transferring it. As per a post up there a bit, Basecamp can't see the NA maps after they've been put on the Zumo's internal memory by MapInstall)

Kevin

I have found the Javawa Device Manager to be an excellent tool to investigate just what has been installed on the device and on the SD card. It provides a lot of information on file names, map set names, map coverage, files sizes, and much more. It also allows for editing map names and moving map sets between device and SD card.

The tool also has a trigger to make maps visible in BaseCamp.

See http://www.javawa.nl/jdm_en.html

Ah OK.
I'm told elsewhere that Map Install can not install 3D or Junction View, is that correct? I'm not so bothered about the 3D NA map but I do really want junction view as I find that very useful.

If all of the NA maps had been installed by Map Install is that how you would expect the Zumo Map Info display to look or should it say [All] for NA as per the EU maps?

[nods] I agree. That's why I was hoping Falagar would answer as I assume he should know (I'm also assuming he's a he!).

No but it's on my next-things-to-try list, thanks for the suggestion. I'm really glad I tried to do this now rather than just before our trip. (Edit: To clarify, I'm going to try installing it on another memory stick then transferring it. As per a post up there a bit, Basecamp can't see the NA maps after they've been put on the Zumo's internal memory by MapInstall)

The map set name seems about right for the CNNA image. MapInstall just lists the tiles in order when naming the map set. Javawa Device Manager should be an easy way to check. Another very simple way would be to check the file size, if it's all of NA it should be fairly big (>1GB). Or you can pan to the eastern US on your device and zoom in and spot-check if you have detailed maps.

The reason the naming of the map set differs is because MapUpdater doesn't build the image, it uses a pre-built image that has a nice name (ALL). MapInstall creates the image itself and always names the map sets by just listing the tile names. Of course not all tile names fit. We could probably be smarter and also name it ALL in case all tiles were selected.

Regarding MapInstall installing junction view files as well, that is something we are looking into. Map Installations theoretically support junction view files, however practically they don't contain it. Once they do, we should be able to update MapInstall to make this work.

BaseCamp cannot see map images that were created by MapInstall by default. I am not going to provide the work-around because someone else already did.

And you are correct, I am a he.

I like the way MapSource allows you to name mapsets.

I like the way MapSource allows you to name mapsets.

Yeah, that's another thing on the to-do list.

Thanks Falagar, that's nice and clear.

BaseCamp cannot see map images that were created by MapInstall by default. I am not going to provide the work-around because someone else already did.

Given that MapInstall is provided as part of a package with Basecamp don't you think that's a little, er, idiosyncratic (regardless of there being a workaround)?

Kevin

Given that MapInstall is provided as part of a package with Basecamp don't you think that's a little, er, idiosyncratic (regardless of there being a workaround)?

I believe the only reason for this was to not confuse users because if they have the map installed on their computer, and have them on the device, it will show up twice in BaseCamp. And if you have the map already on the PC, why would you need to map from the device?

Of course you can come up with all sorts of scenarios where you would still want to view the map from the device, that's why it's good there is a work-around.

I believe the only reason for this was to not confuse users because if they have the map installed on their computer, and have them on the device, it will show up twice in BaseCamp. And if you have the map already on the PC, why would you need to map from the device?

I wouldn't want you to think me argumentative <g> but that's an inconsistent approach as maps loaded with MapUpdater do appear twice in Basecamp if they are on both PC and device.

Kevin