BaseCamp 4.2.0.4 Beta is available

btw, the above ability to do computer/large screen route planning and research is THE defining feature that makes one want to use a premium standalone GPS. . .

This is most certainly true.

The great unwashed who use 99.5% of the Garmin products (Nuvis, primarily) have no idea what you're talking about, and that's the market Garmin is chasing.

The relatively few really well-informed folks who inhabit these boards give me faith that working out routes well in advance on a large-format screen will not become a lost art. . . in spite of Garmin's best efforts (present company excepted) to hide that capability and make it difficult for those who know it exists. It's clear that the hardware people and the software people exist in silos separated by, well, a long, long ways.

I continue to be amazed by the depth of understanding exhibited by the regular posters here. Thanks to all.

This is most certainly true.

Agreed.

I happen to live in a relatively remote region--that is "the country". Now in "the country", as many know, directions can be pretty vague. Case in point. "Next month we'll meet at The Woodshed in ABC". So I ask "Exactly where's The Woodshed?". The answer I get "You know The Woodshed just beyond the black stump on Hwy 1234". Great!

So I open up MapSource. No POI for "The Woodshed". Next step is Google. Ahh! The Woodshed is at 456 Hwy 1234. I search that in MapSource and get coordinates (no sign of The Woodshed). I then open Google Earth and plug in the coordinates. Oh look that looks like a woodshed right there (not at the exact coordinates). I go to Street View. There's a big sign--"The Woodshed". Gotcha! I adjust the coordinates in MapSource to the exact location of The Woodshed. I then create a route, in MapSource, to The Woodshed and transfer that to my nuvi.

Now next month I don't have to worry. I get in my car, select The Woodshed from my list of routes, press Go and follow the Yellow Brick Road.

But I'm sure that's too much trouble for "the great unwashed". They'd rather drive up and down Hwy 1234 for 30 minutes looking for The Woodshed.

This is most certainly true.

The great unwashed who use 99.5% of the Garmin products (Nuvis, primarily) have no idea what you're talking about, and that's the market Garmin is chasing.

I know.. I've felt quite alone in the way I like to do routes on a computer system first. For a long time the later model Garmin GPSs were not capable having computer planned routes downloaded into them...

I waited and waited for a newer GPS to replace my aging Garmin 2610... and several years ago thought I had found the replacement Garmin unit, then discovered the then current high end model would not support downloaded routes.. I sent a few notes to Garmin marketing asking why their premium flagship GPSs lost this capability. Glad they finally regained that capability.

One of the more extreme "back roads" we've done in our 4x4 ... http://home.4x4wire.com/deddleman/photos/BLM-shafenty.jpg
This is the entrance down into the Shafer Trail in Dead Horse Canyon area out from Moab, UT.. https://maps.google.com/maps?hl=en&ll=38.451589,-109.812212&spn=0.013662,0.025814&t=h&z=16

One caveat, there's one turn you must make on this trail to stay on the Shafer trail, which is driveable in a day, otherwise you are continuing on a loop that takes a minimum 3 days to drive and must carry extra fuel and of course prep.. At the time using a GPSIII+ (no GPS maps in those days for off road areas, but did have the lat/long for each turn I had to make, plus paper topos...

great unwashed who use 99.5%

There's been more than one instance in remote country where this attitude has cost someone their life..

Some years back a CNET reporter and his family on the way back down I-5 in Oregon decided to take a short cut across to Highway 1 on the coast, missed his turn and decided to try cut across the mountains on the National Forest Road-23 shown below in the winter time. It cost him his life and almost his family when he inadvertently turned into a maze of BLM logging trails and got stuck in freezing snow fall conditions.. Very sad story... I pieced the route he inadvertently got into from various newspaper accounts for a discussion on an off road forum I moderate...

http://home.4x4wire.com/deddleman/photos/BLM%20Road%20in%20Error.jpg

Apologies to the forum if this is too much off topic, BUT I think it is important to keep making the case for programs like BaseCamp and full function GPS units, in spite of the 99.5%

Some years back a CNET reporter and his family on the way back down I-5 in Oregon decided to take a short cut...

Yep. I've read many similar stories.

A few years ago two guys showed up in (this remote mountain) town early Sat night looking for someone to repair two flat tires from their Jeep. Seems their GPS was set to "shortest distance" so they came over the mountains. The "road" they took was in fact an old mining trail used by mules 100+ years ago. It was widened to a "road" back in the 50's. While people do drive that "road" they do so prepared and for recreation not as the shortest distance between two points.

These idiots lived. They left their disabled Jeep and walked down the "road" to town (some distance). They then wanted someone to fix their flats and drive them back to their Jeep. I wished them the "best of luck" and left them to it.

One of the more extreme "back roads" we've done in our 4x4 ... http://home.4x4wire.com/deddleman/photos/BLM-shafenty.jpg
This is the entrance down into the Shafer Trail in Dead Horse Canyon area out from Moab, UT.. https://maps.google.com/maps?hl=en&ll=38.451589,-109.812212&spn=0.013662,0.025814&t=h&z=16

Thanks for the links... Since I can not be there right now, I will have to settle for some 'Motorstorm' on my PS3 :)

Just ran into an issue with displaying waypoints using the BC Beta. I have a Montana 600 connected and one waypoint name doesn't appear in the BC list of the devices internal storage. It can be seen on the units own waypoint display and can also be seen in BC if I launch the released non-beta BC. With the beta version it just isn't in the list. If I try to create a new waypoint using the same name I do get the invalid name error so it must know it is in the data on the device. The same waypoint is seen in the All Data list. If I drag or use Send To the waypoint from All Data to Internal Storage I see the Interla Storage momentarily go yellow ahen green but the waypoint name never appears.

Using BC I can open a route on the device that uses the waypoint and recalculate with no error so the waypoint must still exist.

Any ideas?

Just ran into an issue with displaying waypoints using the BC Beta. I have a Montana 600 connected and one waypoint name doesn't appear in the BC list of the devices internal storage. It can be seen on the units own waypoint display and can also be seen in BC if I launch the released non-beta BC. With the beta version it just isn't in the list. If I try to create a new waypoint using the same name I do get the invalid name error so it must know it is in the data on the device. The same waypoint is seen in the All Data list. If I drag or use Send To the waypoint from All Data to Internal Storage I see the Interla Storage momentarily go yellow ahen green but the waypoint name never appears.

Using BC I can open a route on the device that uses the waypoint and recalculate with no error so the waypoint must still exist.

Any ideas?

Could you zip up the gpx directory on your Montana and attach it here or send it to me via PM?

Thanks.

Where's the Help File!!??

Where's the Help File!!??

The help isn't hooked in yet. This should be ready come release time.

With BaseCamp 4.2.04 Beta when I insert additional waypoints into a route, I click on the route so I know I'm at the correct point along the route, then click on the insert point icon, then rubberband over to the new waypoint to be inserted and click on it.. Works fine on the first inserted waypoint, in that it goes into the proper place (order) in the route with respect to other waypoints already in the route.

However if I pull the rubber band over to a 2nd nearby waypoint to be inserted, instead of placing that waypoint following the 1st one inserted, it inserts the 2nd waypoint down the route (skipping forward) over several existing waypoints in the route. In last case I tested, it inserted the 2nd waypoint down past two existing route waypoints. And of course when the route is recalculated, with the second inserted waypoint out of order, it creates a route backtrack.

I haven't had this happen using the same procedure with BaseCamp 4.1.2

btw with the maps loaded on the computer instead of accessing them in the attached 3597, I don't get the crash I reported earlier when using the insert point icon..

thanks