BaseCamp 3.2.0.10 Beta posted

Observations and Nit Picks.

Good progress here. The biggest positive I see is the potential of some of the fledgling features. More on that in another thread. :) I just discovered that the "Hide Map Feature" selections are activity specific and saved with the route profile!!!!! Thank You Sir.

Nit Picks:

The time displayed for navigating a route is a different format between the route properties info window and the map display. I find it confusing to see days/hours displayed instead of total hours as per the info window. A preference where the user could set the duration of a travel day in hours would be ideal, then the day/hour format would be more useful.

Having a choice of Activity in the routing preferences window would be more intuitive than having to go to the menu bar to change Activities.

Wish List:

Make the activities user configurable/nameable. I have no need for cycling, pedestrian or trucking but would love to have 2 or even 3 different Motorcycle profiles, named appropriately.

The time to navigate a route appears to be a bit arbitrary. What is it based on? The ability to set an average speed in Preferences for each of the 5 main road types would make this a more accurate estimate.

And I'm sorry, but I can't stop myself. :D Waypoint categories and true track filtering...... I have given up on custom avoidance settings though. ;)

I generally agree with KILLTIMER - with one exception;).

I like having the "Activity" selector button on the Tool Bar. But, it needs to have relevance to what is going to happen to the route - and I only know that when the routing preference is set to Direct Routing. We need well defined options in the Routing Preferences window such as, but not limited to, the ones KILLTIMER described; i.e, Speed assigned to road type by user, clear definition of shaping algorithm's use for different Transportation Methods, etc. Currently no one knows what effects these preferences "should" have on a route.

If the Activity profiles were better defined as to their effects on routing, then it would be very useful to have "user definable" Activity names as KILLTIMER described.

Oops, forgot; another for KILLTIMER's request for Waypoint Categories. The On Trail products and the On Road zumo 66x products support Categories.

I generally agree with KILLTIMER - with one exception;).

I like having the "Activity" selector button on the Tool Bar.

I wasn't very clear on this. I agree, the selector needs to be in the tool bar but a way to choose an Activity to configure in the preferences window as well would be more intuitive IMO. Having to go up to the tool bar to select a different activity when the preferences window is open seems a bit strange (to me).

crash or recalculate route

I opened BC and double clicked a route. Before .10 I got a different route with an auto symbol. This time nothing changed. I selected recalculate route and crashed. Tried the same thing again.

When I report a crash (BC crash report) do you get the cash report? If not how do you want to receive the crash report.

Thanks

Still seeing issues with routing

If I ask Basecamp to create a route from Dahlonega, GA to Cave City, Ky BC takes me 50 miles south down 400 and back up I 75. Prior to the beta base camp was taking 50 miles off the route going through Ellijay and hitting I75 above Dalton, GA

Thanks

Just a note to say that this beta appears to resolve all my gripes about previous betas -- and the map drawing looks great. Thanks to the team for your hard work!

Routing fix

BC 3.2.0.10 now adds an Automative icon to most of my routes. If the route does not get an icon added and you recalculate, BC crashes 100% of the time. Before 3.2.0.10, no route had an icon until you doubled clickte the route. The route was recalculated and an icon assigned when you double clicked a route. The crash is not a big deal for me, I will just delete any route that did not get an icon.

The problem is the routing algorithm. If you Search for Dahlonega, GA and Chattanooga, TN creating a waypoint from each find and create a route, BC takes you south almost to atlanta for a route of 167 miles. If you drag the route up to ellijay it gets worse. BC goes south again for 199 miles. If I drag it closer to Dalton BC goes south and back tracks for 201 miles. If I leave the Dalton in an redo the Ellijay drag I get the route BaseCamp was creating before Bets a route of only 107 miles.

The trucking route gives me the route I was getting before beta, or very close 108 miles. It appears to me that the preference panel needs help. If I go to the preference panel and select shortest, go back to the route and recalculate I get the same route. Does not the routing preference panel need to be killed? If BC has a shortest and fastest route, should in not be added to the routing window?

Thanks

It appears to me that the preference panel needs help. If I go to the preference panel and select shortest, go back to the route and recalculate I get the same route.

The route preferences section of the preference panel has a banner saying which activity's route preferences you're editing. So long as that matches the route you're recalculating, the route should change if the shortest/fastest route are different for that route. It is also entirely possible that the shortest/fastest route are the same for that route, though.

Good progress here. The biggest positive I see is the potential of some of the fledgling features. More on that in another thread. :) I just discovered that the "Hide Map Feature" selections are activity specific and saved with the route profile!!!!! Thank You Sir.

Nit Picks:

The time displayed for navigating a route is a different format between the route properties info window and the map display. I find it confusing to see days/hours displayed instead of total hours as per the info window. A preference where the user could set the duration of a travel day in hours would be ideal, then the day/hour format would be more useful.

Good catch. We'll get that fixed. True multi-day trip planning is on our roadmap.

Having a choice of Activity in the routing preferences window would be more intuitive than having to go to the menu bar to change Activities.

It seems more confusing to have the main app and the preferences to have different profiles. If you want the preferences picker to change the apps profile, that could be unexpected as well.

Wish List:

Make the activities user configurable/nameable. I have no need for cycling, pedestrian or trucking but would love to have 2 or even 3 different Motorcycle profiles, named appropriately.

That's our plan. We just didn't have time in this release to add that feature. For now, people are using the other profiles, e.g. "Trucking is my second motorcycling profile."

The time to navigate a route appears to be a bit arbitrary. What is it based on? The ability to set an average speed in Preferences for each of the 5 main road types would make this a more accurate estimate.

It is based on average speeds for each type of road. Being able to override the default is a MapSource feature that has never made it over because of the complexity for the user. I can't say we have plans to resurrect it, but we will keep it in mind.

And I'm sorry, but I can't stop myself. :D Waypoint categories and true track filtering...... I have given up on custom avoidance settings though. ;)

What exactly do you mean by "true track filtering"? The tracks are filtered when sent to the device if the points exceed your specified number of points. What is the use case for filtering them while still in BaseCamp?

As always thanks for your feedback.

What exactly do you mean by "true track filtering"? The tracks are filtered when sent to the device if the points exceed your specified number of points. What is the use case for filtering them while still in BaseCamp?

I track all of my motorcycle trips by day at a fairly high resolution. A typical touring day will have 2500 to 4000 track points, many of them redundant. For example, using MapSource, I usually filter out any track segments less than 20 seconds in duration and less than 50 feet in length. This cleans up most of the clutter of fuel stops, rest stops and such without the need for a manual edit. I use tracks as a ride archive, and then convert them to a route if I decide to re-use that segment in planning another tour.

As always thanks for your feedback.

You're welcome.