Separate names with a comma.
Discussion in 'Mapping & Navigation' started by AugustFalcon, May 18, 2011.
. . . uh...yes.
Thanks guys !
Using BC, I perfer to 'Export' my routes, tracks and waypoints to the gps. When a list is exported, it takes on the list name with a .gpx file extension. The routes, tracks and waypoints are all in a single file with a descriptive name when viewed through Windows Explorer.
+1. I'd like to see this too..
And that is a good way to manage your data with Windows Explorer. But, if you want the benefits of what the Montana can do for you, that isn't the best option. We discussed this last year when the Montana optimized the way it reads your Track and Route data.
There are two primary benefits of using BaseCamp to Transfer (Send to Device) your data.
When BC transfers the data it breaks the Tracks and Routes in to separate files as I mensioned previously: Track.gpx, Track1.gpx, Track2.gpx…, Route.gpx, Route1.gpx, etc. By doing this the Montana does not have to load ALL of your data into memory at one time. It can optimise performance.
Routes contain waypoints and the Montana will show you those waypoints in the Waypoint Manager. If you transfer your data in a single GPX file the Montana places all of that data where it belongs: Waypoints in the Waypoint Manager, Track in the Track Manager and Routes in the Route Planner. In so doing if you transferred a waypoint that was used in a route you will get duplicate waypoints in the Wayoint Manager. If you used BC, the Montana knows not to duplicate a waypoint that is in a Route if it is already in the Waypoint Manager.
In summary, if you have relatively long Tracks and/or Routes the Montana will preform much better if you transfer the Route/Track/Waypoint data to internal memory via BC. All other data I put on my µSD Card.
BMW Motorrad finally releases the Navigator Adventure GPS: aka the Montana 600.
The BMW unit comes with Lifetime Maps and the AMPS Rugged Mount with RAM Mount. I'm guessing that it also has a BMW Dealers POI database - which most likely can't be accessed by the user if they keep to previous Navigator implementations.
Interesting, if you're a BMW rider, per BMW's press release:
"It can be used as an alternative to the Navigator IV on all BMW motorcycles except the new R 1200 GS, the K 1600 GT and the K 1600 GTL."
If I were BMW Marketing, I might have worded that a bit different. I think what they meant to say was that the Navigator Adventure does not interface with the bikes Trip Computer in the same way as the Navigator IV does on those bikes.
Anyway, maybe us poor stepchildren will get Lifetime Maps included with the next firmware update...
I did the transfer from Basecamp so wherever that sends it too. Is there a difference?
Yes, if the Route is sent to the Garmin internal storage, the route should remain as-was in BaseCamp (not recalculated). If it was sent to the µSD Card it was recalculated.
It would be interesting to look at where the changes are in the Route compared to the Track since you have them both on the Montana and try to figure out why it was recalculated if it actually was transferred to internal storage.
Wow, really? Thank you so much, this is really useful information. It would also explain some of the behaviours I've seen and couldn't explain, even after reading may wikis and threads
If you have a link explaining this kind of differences in more detail I'd be (even more) grateful.
There are a several good sources to keep up with:
Emmbeedee's Wisdom Thread for the Montana
altas cache's Wiki for the Montana (see below screen shot)
Here of course...
Really! We need to capture this in the Routing thread as well then.
I figured this out on the trail, and locked the orientation. Still had crazy, momentary "blurps" where the screen turened 90 degrees, then flipped back.
I have North American City Nav on my MT, got into a smallish town outside Dallas, couldn't get local street names to display. Do I have a "Settings" fail, or is it a limitation of City Nav?
Or have I failed to properly activate City Nav on the unit? The lines for the streets appeared, just no names.
You mus be running a very recent firmware on your Montana.
Garmin has tweaked the firmware recently in favor of map drawing performance at the cost of some map detail, including street names.
Got a 600 recently after months of following this thread. This is such a great resource. But for some of us more tech challenged, it can raise as many questions as it answers. Here's one I'm still wrestling with. The 600 came with 4.6 and works fine so far. Should I just stay with 4.6, or upgrade to 4.9? Thanks.
I'm sticking with 4.7 for the reasons posted above. Garmin has an unfortunate track record of breaking more than they fix with firmware upgrades, so when I get a good one, I keep it until the community here thoroughly vets the newer one. I'm sick of being a Beta tester for Garmin.
You can get earlier versions, (I forget the link, but someone here will have it) and I usually keep the *.exe file on my computer so I can revert to a known good version. I've had no problems with 4.7.
Try out 4.9 and see how it works for you. I had some initial issues but after a master reset everything has worked just fine for a few thousand miles.
You can always rollback to 4.6. I've done it a few times since 4.6 is the last rock solid stable release for me. Although 4.9 is treating me well at this point.
I just purchased a Montana 650t. I have worked with mapsource in the past with a older serial port Garmins. Now I have to learn Basecamp which is new to me. I have a Mac with Mountain Lion and Windows 7 on it. Is there substantial advantages of one system over the other? I have read this forum up to page 374. I get the feeling with Windows I can do more but Apple might be easier to use. Which system would be best to start with. chip
You should plan to spend some time with BaseCamp. It is not a follow-on to MapSource so don't go into it thinking it should just work the same way. The workflow is much more intuitive once you've learned the basics of the application. There are big changes coming to BC on both OS's in v4.2. Oh, and I personally prefer the Mac version of BC over Windows.