MapSource & BaseCamp

Have you updated maps? The routing differences could be tied map versions rather than versions of Mapsource/Basecamp. If you still have your older maps installed, you could try the routes with that mapset.

Getting a different route when you reverse is nothing new. You can find several threads on this and other forums about that.

Set Edit>Preferences>Routing>Road Selection in the middle in MapSource, Tools>Options>Activity Profile>Road Selection in BaseCamp with BC. That will calculate similar to how the GPS calculates. Then add waypoints to shape your routes.

Don't get Waypoint crazy when planning a route. Start with just your Start and Destination. Add motels if a multi-day ride, split the route into single day rides. Add waypoint attractions. Then add shaping to each route to your road selections.

I don't understand your comments about MapSource having a cache of waypoints, routes or track logs. It opens up with nothing. BC opens up with however you last left it. Track Logs are not used in routing at all.

I had trouble creating a route for the Blue Ridge Parkway. The problem areas are around Roanoke and Ashville. MapSource refused to stay on the BRP regardless of how many waypoints I put on the route. BaseCamp would stay on the BRP with very few waypoints. On a suggestion from a moderator at GPS Passion, I tried S&T. It might have been a little better than MapSource but was still an issue in the same two places. I don't love the way BaseCamp works (getting points in order is particularly messy) but it did a very good job with this route. I loaded the BaseCamp route for the Ashville area into my 885t and it worked without changes.

I still need to split it up into daily segments and add some POIs for daily start/end points and favorites for the places I will stay.

I think it is worthwhile to learn to use BaseCamp.

Jim

Playing with the options and the average speeds always works for me. I discovered this trick about a year ago and I have little problems in getting routes to stay on the desired path.

One big helper - the speeds for roads are always lower than suggested. Garmin suggests an average speed of 68 for Interstates. The only way you could AVERAGE 68 would be to travel at 75 or better whenever possible.

I have always had issues with the avg. speed because it works at what was stated, 7 to 8 mph less than posted speed limits.

I could be wrong but I think that average speed does not have anything to do with routing, only the time calculations of when you will arrive.

With respect to making MapSource do what it should, I would love for you to make a route in MapSource starting about where the Blue Ridge Parkway crosses I-26 on the southeast side of Ashville and ending on the other side of Ashville. Two administrators at GPS Passion and I tried this and none of us got it to work. None of the preferences we tried made it work. I did not try varying the average speed but I am pretty sure it is not going to work. Average speed limit on the BRP is 45 mph.

BaseCamp will do this with 3 or 4 waypoints, maybe less. I made no adjustments to preferences.

Jim

As a Mac user I've been using Base Camp for awhile. When I switched to Mac's from PC's several years ago there was a learning curve after using MapSource for so long. However after figuring it out I've been pretty happy with it. Can't say I use it often though, I really don't have much need.

Both MapSource and BaseCamp have been updated to the latest version. Also City Nav has been updated to 2012.2.

I will so some searching on the reverse route and see what those posts have to say.

Thanks.

Last year on the return trip from Lady Lake I drove up to Ocala and then made a right on RT-40 to go over to I-95. This was not the most direct route nor was it the fastest. When I was playing around and tried to create a return route from Lady lake it would take me back up to Ocala and then to RT -40 again. Okay be that way so I set up a way point on RT-25 in hopes MapSource would route me that way. Well it did not. It again went all the way up to Ocala then directed me to take a U-turn and drive all the way back to RT-25 and 441. Same thing happened in the Ocala National Forrest. More way points needed to be added.

I figured that since last years track was present MapSource was using that and NOT truly recalculating things. I deleted last years return track and without the added way points it still wanted to take me to Ocala. A system reboot you would think would clear out things but it did not. I started again trying to create a fresh route and again up to Ocala and out of the way. Add again the way point at Rt-25 and the U-turn happens again.

Now the odd this that really has me stumped is that in earlier versions of MapSource I did not have this issue. I only needed one way point at Rt-40 and I-95 and MapSource took the route I wanted to take all along. Upgraded the programs and now the problems.

I hope that explains it more.

Huh? I've got 1 viapoint in that section of the BRP. Here's are full NB & SB BRP MapSource routes: http://www.zumoforums.com/index.php?action=downloads;sa=view...

Your link takes you to a login screen:

"Only registered members are allowed to access this section.
Please login below or register an account with THE ZumoForums. "

I forgot you have to join zumoforums to download. We've got some good MS & BC discussions over there. You can get the BRP routes here: http://garmin-mapsource.wikispaces.com/RT-66

I made a route from Lady Lake to Jacksonville. With one waypoint at I-95 N and Ramp, N29.26058 W81.11712, Hwy 25-CR 19-Hwy 40-I95.

That's with Edit>Preferences>Routing>Road Selection in the middle, just like the Zumo recalculates for me and with map data 2012.20.

It does work best to zoom in to 80ft. before setting a via point or waypoint so that you accurately get the point on the proper side of the road, as a divided highway can tell MapSource to make some unusual detours to reach your waypoint.