![]() ![]() Maybe you're trying to tell me that when I map out a Route on BaseCamp, when it gets sent to the Zumo it ensures that all the relevant maps are pulled into the device.Learning how to change countries on Garmin GPS units is a crucial step to do before going on your trip to Europe. Beneath this I see is the stuff I picked when I loaded map portions from BaseCamp onto the Zumo SD card (as I said, I selected pretty much Florida and most of the East Coast below Virginia.Īgain, why do I need to garbage my device up with the map of Canada? I have no use for this. I now see on the Zumo device itself, when accessing Map Info, a check mark next to CN North America NT 2020.10, and beneath it is Raleigh, NC, Atlanta, Georg (and the rest is off the screen). Is it not possible to clean this up and put a region of the US on the internal storage of Zumo, and if needed, add in other areas to the SD card? This is very confusing. Let's start over, partially, with the question of "Why does the Zumo only seem to see or accept the Canada map when I'm trying to update the Lower 49?" Here's a screenshot of the Maps installed. I seems I used to be able to just load a section of the U.S. Just FYI.Īm I going to have to live with maps on the Zumo that appear to cover the entire North American continent? Is there some way to cut these down to size. I build virtually all my Routes using BaseCamp and do not bother to construct anything on the Zumo itself. I'll be doing that with the same version map installed on the computer and just sent the Route to the Garmin? Using BaseCamp, when I click on the City Navigator North America NT 2020.1, now installed in internal storage on the Zumo, I don't see any local roads or streets, even though I have the detail level set to "highest." Are the details still loading perhaps? I assume I won't need to click on the Zumo map when building a Route. For example, I live in Florida so I'm moving over Florida and a good deal of the East Coast up to the Carolinas. I'm currently installing some maps from the PC to the Garmin's memory card. I can see the V2018 file in the root of the Garmin, chewing up 1.2 GB of space. I'm afraid that if I start brute-force deleting I'm going to break something. ![]() I feel like there must be a way to remove the old outdated map file off the device graciously. This may affect the performance of BaseCamp." Obviously, this is trying to read the map file off the Zumo. ![]() I says, "The device containing City Navigator NA NT 2018.3 is connected with limited speed. I also suppose it's natural for BaseCamp to complain when trying to look at stuff on the Zumo. I'm also pulling an error: Error while communicating with Zumo reading file garmin/gpx/current.gpx. Funny how MapInstall doesn't show any options for pointing at the memory card. I read on BaseCamp that it is resident in Internal Storage on the Zumo - and it isn't resident on the memory card. Question: Is there some way it first delete V2018.3. It says that I'm already 6K over the limit, and any clicking on the map sections just overloads it more. But I'm unsuccessful in using MapInstall to update the Zumo. I managed to pull down City Navigator North America NT 2020.1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |