Separate names with a comma.
Discussion in 'Mapping & Navigation' started by atg, Sep 20, 2013.
Didn't you mention it on the other thread? If it wasn't you, I can't remember who it was.
I completely lost control of my AmEx whilst pinking up the WCGS, and ended up with the Nav-V to fill the empty cradle from the GPS Prep-kit on the bike...
After putting some road miles on it, I really like the GPS unit for road use. Its clear, responsive and accurate. I certainly like the dashboards view that supplements the info/trip data from the bike's computer. So for road use, this thing seems like the bees-knees....
For Offroad use though - Im not so sure... so maybe someone already has worked this out... I've been using a cellphone and Backcountry Explorer to have FS/Topo Maps and loading GPS Tracks on for the BDR... and while that works, I'd rather be able to do the same with the Nav V... So: Does anyone know a good way to get Topo or maps with Forest Service roads loaded on a NAV V?
Additionally, I cant find the specifications for what capacity MicroSD Cards are supported... Does anyone know?
Install your Topo/other maps into BaseCamp and then with your Nav-V connected to your computer use Garmin MapInstall to install the map to your device. I recommend installing to the micro-SD card and I believe that the Nav-V supports up to 32GB cards. Use a high quality card like SanDisk and you will have fewer issues over time.
^^ Thank you, Much appreciated - Now I just have to figure out how to get the Accuterra maps I bought from my Android off, in a format that the Nav V can hopefully accept.
Just bought a 32GB class 10 Sandisk from Amazon.
Unless you get Accuterra to convert their maps to Garmin compatible format you're out of luck.
Ahh, So does garmin sell Topo Maps that are compatible with the Nav/Zumo devices? I dont mind paying for the ability... Im looking at their BirdsEye Topo Series but the Zumo/Nav ist listed as compatible - hence my confusion of how to load Forest Service/Topo Maps. Thanks for the help so far and any other advice you can give.
Edit: Reading the articles on your sig... It appears as though you are running the Birdseye maps (on what looks like to be a zumo or similar)... I'm busy reading your site in case my questions are answered there - Thanks in advance
You do not want the BirdsEye topo's. They are just images of topo maps. What you might want are either the 100K US Topo (not much road detail) or the 24K US Topo's (by region) that have reasonable road detail and are routable. It really depends on what you want the Topo maps for. The latest version's of City Navigator NT 2014.20 have more backcountry roads than most maps - just not so good for trails.
Thanks - Thats super helpful. 24K regional is what I've been looking for but didnt know how to ask the right question. Thank you, for the help and patience.
Meta-4, are you finding that the forest service roads you seek are not in the CN version on your Nav V?
I am running Garmin regional topos on my Montana and although they are nice, they have not been updated in years.
So, I ran into limitation of the Nav V over the weekend. I spent a bunch of time creating a fairly complex one day Route to follow. Part of the route was created from a track where I had stumbled across roads that I wanted to take again sometime. The rest I added in BaseCamp with the insert tool (pencil icon) to make it into a loop.
Apparently, imported track points become Via Points when imported to to a route. It wouldn't matter except the Nav V has an arbitrary Via Point limit of 29! So, my route was split into three routes on the Nav V! How stupid is it to not even be able to have a route in one piece for a day's ride?
Even worse, when in BaseCamp and I look at the Route detail dialog and right-click a Via Point and select "do not alert - shaping point" the software doesn't really change it to a Shaping Point, so I still hit the 29 Via Point limit.
If anyone else finds this limitation silly or frustrating, I urge you to contact both Garmin and BMW about it. Garmin built the Nav V to BMW's specs, but I suspect they never thought about this item.
Well, this is really weird. I just did a test. I pushed the route to the Nav again, and it came out as a single route!
Since my initial post about this, I have exited BaseCamp and re-entered it. Is it possible that the Via Points did not actually change to Shaping Points until the application closed?
Its hit and miss...Some of them are, and some are not... Id say on my limited exploration I had most of what I needed, but occasionally i would come to forks and route options (do I go left or right?) that were not on the Nav V maps...
Its not that bad, but if there are better maps, Id use them and like to have alternative topo maps as a backup.
This may seem obvious to those who have owned this thing for several weeks now, and I have had mine for all of 24 hours, but I have a question- where the devil are my custom routes, in Trip Planner? I was going nuts last night looking for them, and this is one place I have not looked. Initial impressions are good and should get better as I negotiate the learning curve.
Update- that was it. Duh.
Formatted a 64mb sd card FAT32 and it is visible in the Nav V. Anyone else done so?
Played it safe and used a 32GB Class 10 Sandisk. Threw a little over 5,000 ~192kbps mp3 files in the \GARMIN\MUSIC\ Folder with a \%ARTIST%\%ALBUM%\ subfolder structure and the individual tracks in each folder.
Other than a bit of lag on initial views the NAV V can see them all and Ive had no issues with audio playback... Even with the high bitrate, I only used about 25GB total - that still leaves well enough room for a 24K topo NW Map, I believe.
So how does the display on the Nav V compare to the Montana?
I will run them a bit over the next handful of days and pay more attention to the differences. I did not notice any great differences, but then I wasn't really looking with that in mind and was running one with CNNA and the other with 24k Topos. I will come back after looking at them with the same maps side by side.
Expect you meant 64GB. Most of the 64GB SDXC cards also meet SDHC specs so it's not a surprise that the 64GB works even though BMW/Garmin only published 32GB support. Thanks - good to know.
Exactly Dan, just wanted to see how long before someone found this error.
As usual, I took the bait...