BaseCamp 3.2.0.10 Beta posted

Sorry, DENNYHENDERSON I'm just not as smart as you and never owned a Zumo. I totally agree that GPSshould accept routes as upload and the route should not change but I think the problem is with the 100s or even 1000s different GPS models BaseCamp is trying to support. Instead of trying to support legacy GPS products will all features, I think Garmin should be developing a new line of GPS products certified for BaseCamp.
1. Except for traffic related routing and nüRoute; Transportation Modes, Route Preferences, and Routing Algorithm should be the same so people can use the units as stand alone and not require a route upload if you have a standard calculated route.
2. Uploaded (draged from BC to Unite) Routes should not require a multistage process and should be identical routes. If the gpx route file contained enough information, it would be great if Garmin could standardized on the GPX format.

Create Route from Track...Direct Routing?

I think this might not be working as intended.

When I set my Routing Preferences for Direct Routing and then preform a "Create Route from Track..." operation, my expectation is that I will get a Direct Route that uses ALL of the Track Points as via points not just the Start point and End point.

Is this currently working as intended?

Cheers,

Route Info screen: NOTES field. . .

The NOTES field does not Left-Right Justify text well. This is a bit of a nit but it would be nice to have this fixed. I use Notes (Description) fields often.

While I'm on the topic, it seems many of the On Trail devices are using the term "NOTES" term rather than the historic Description or Comments term. Although, I noticed that Waypoints only have a COMMENTS field not a NOTES field in BaseCamp.

What is the reason for BaseCamp having COMMENT field on Waypoints rather than NOTES?

Cheers,

I have created a small route in Lancashire, UK, with just a start point and end point, motorcycling profile. (Small item: the info page for the route says "Transportation Method: Car". Car?)

I'm using older maps (City Navigator Europe 2009) because Garmin has ceased publishing updates for my Quest. Here's the route map:



Two issues: the silly route south turning into direct routing followed by the U-turn, and then direct-routing to the destination straight across the sea.

Here's the route:

http://www.collinacre.plus.com/Basecamp/Lancashire Route.gpx

I just committed a change that should fix this. So 3.2.1 should not display this behavior anymore.

Excellent. Thanks very much for putting effort into supporting old stuff.

Feature/Function Request

The backup function is very handy as it is for syncing between multiple computers. Any chance that the BaseCamp Preferences, including the "Hide Map Features" preference could be included in the backup? This way all BaseCamp installs would have the preferences set so any subsequent planning or editing of routes would have the same outcome.

This beta is really a big step forward, i like it! :)

One little complaint: waypoint sympols read from the edge 800 are wrong, e.g. a mountain get's an anchor...

One little complaint: waypoint sympols read from the edge 800 are wrong, e.g. a mountain get's an anchor...

You're right. That is an issue that we probably will not be able to fix before the release. Thanks goodness for "bulk" waypoint edit :)

Zoom bug

After a long period of no problem, today BC launched with the map zoomed all the way out to all of N. America again.

I also came across a route file created in BC that my new zumo 660 refused to import -- crashes the GPS every time. But this may well be a zumo issue -- the same route imports OK on my nuvi 760.

-dan

I also came across a route file created in BC that my new zumo 660 refused to import -- crashes the GPS every time. But this may well be a zumo issue -- the same route imports OK on my nuvi 760.

-dan

It's a zumo issue but look at the route in question. How many via points does it have in it? Over 250 and it can cause "issues".

Are you at v4.20 of the software? Hope that they deliver a "fix" rather than an "update" soon. v4.20 broke more than it fixed and reverting to an earlier version didn't fix a lot of what is broken (some of which you might not even be aware of unless you use Tracks).

Cheers,