What did I do wrong? (GPS recalculated the itinerary)

In BaseCamp add waypoints to your route that take you the way you want to go. Double click and open your route then right click on your shaping waypoints and select don't alert on arrival. This will not alert you but will take you the way you want to go.

I do the shaping points right in my 2797 once I have a route set up by using the edit function !

As far as mpion's GPS not following the route, I wonder if he/she did not have ALL waypoints transferred. Just the starting point and the end point possibly. To me that would explain the not following the route.

If mpion's route is still saved in the GPS by using the edit/add waypoints it should show what waypoints were transferred for that route.

I have the problem of a waypoint not transferring. The waypoint shows in my route in BaseCamp but it never transfers over. There are seven "do not alert" waypoints in this route and it is the only one that will not transfer over. Have tried several times. I think I will delete the waypoint and make a new one then add it to the route and see if it transfers over.
If mpion used waypoints that could be their problem.

I’ve had problems in the past with GPSr’s changing imported routes. I’m not sure if you are already doing this but the problem went away for me once I started building routes using Basecamp’s Trip Planner feature. Once imported via Trip Planner, my newer GPSr’s do not make route changes.

Since you came from a 14x0 device that has Garmin's classic route planner, make sure you are using the trip planner correctly. When you start navigating a route with Trip Planner, you pick the first waypoint from the list, not the final destination. If you pick the final destination, it will recalculate the route ignoring all the via points. This confuses many people when they switch from an older nuvi to one with Trip Planner.

That's the normal error. The other problem you may run into is that provided you follow a BaseCamp route exactly all should be well. The issue comes if you go off route for some reason, at which point the dreaded recalculation occurs.

Way round that is to go back to trip planner and restart the route to the next viapoint.

Heck, I have been doing this all wrong. I usually start with the destination. That is why it is confusing. Didn't know you had to start with the first destination.

Learn something new every day.

I guess because of what alanb suggests, I still prefer to use MapSource over BaseCamp. Maybe because I have used MS for so long it seems more intuitive for me.

If you do not have MapSource anymore or never had it this how and where to get it! All Garmin Maps you have on your computer will be available to use in MapSource.

Now to be honest, I have not installed this particular version since I already have MapSource v.6.16.3 on all of my computers. So I really do not know if this is also ONLY the update file!

You can download Mapsource v.6.16.3 here:
http://en.freedownloadmanager.org/Windows-PC/Garmin-MapSourc...

To download click on the smaller "Download button" near the top LEFT where it says 54.4 Mb.

---------------------------------

You can download a MapSource update from Garmin here, it says 57.05 MB:
http://www8.garmin.com/support/download_details.jsp?id=209

But this is only good if you already have an older version you want to update to 6.16.3 which is the latest and LAST version of MapSource. Surely anyone using MS has the latest version already.

There are many folks like you that prefer Mapsource over BaseCamp, but the issue I described has nothing to do with Basecamp and you would get the same results with Mapsource. It has to do with the way the Trip Planner app works on the newer Garmin automotive devices as compared to the old classic "Custom Routes" feature. The same situation exists even if you create the trip on the device itself rather than importing it ... when navigating the route you have to select the first waypoint, not the final destination.

I'm not sure that MapSource can send shaping points to nuvis etc? Or if it can are they converted to via points?

So if you tend to plan routes with lots of shaping points and want them retained as such when sent to your newer devices that are capable of accepting shaping points you need to use BaseCamp.

Sorry my bad and my misunderstanding.

I deleted the number one "do not alert" waypoint from my route in BaseCamp that wouldn't send to my Nuvi 2450 and re attached it back to my route.
I then went to my Nuvi and deleted the route, I then resent the new route from BaseCamp to my Nuvi.
The waypoint number one was there. But now the waypoint number five was gone. I tried this a couple of times from BaseCamp but never could I get it to send all seven "do not alert" waypoints to my Nuvi.
I then went into my Nuvi and inserted it manually. All is fine with the route not.

But, just don't know why the route sent from BaseCamp would not send all seven "do not alert" waypoints to my Nuvi.

... This crops up time and again. I've never experienced this issue and have no idea why it occurs. I don't expect anyone will be able to explain what is happening, would be great if someone can though.

You seem to forget, that route calculated in comp software (like Map Source) usually will be different than calculated in device. And different GPS's will calculate route differently. We had those discussion before.

For me waypoints missing during transfer may be victims of some optimization algorithm. Computer software can operate with way more waypoints than GPS. So during transfer some "less important" points can be cut out from route so they will not exceed number of waypoints allowed for device. Algorithm probably works regardless of number of points so even with few points they will be "optimized".

That may be a reason that from mgarledge's points always this same one was cut out. It could be a victim of optimization.

I have never experienced this problem with route transfer, but if I ever do, I will open the temp.gpx file and browse through it. It should be relatively easy to figure out whether it is BaseCamp or the nuvi trip import feature that is the culprit in removing the waypoint.

I am new to Basecamp, POI-factory, and the POI thing in general. But trying to learn fast. I have an interest in making sure my routes are specific and stay the same for motorcycle touring and want to avoid distracting unexpected changes to my route.

I would check your basecamp preference settings under routing and transfer. I am willing to bet some settings were different between your old and new devices. In routing, be sure you have the calculation mode and avoidances for routing for each activity(driving, cycling, RV, etc.) that best matches your desired route. Most importantly, there is a transfer setting to match the route to the map on the device when transferring. I think this setting will help you maintain your desired routing during transfer. Be sure to select the right device, as your old device, new device, and SD card can all be set separately. (There is an apply to all devices option as well).

There is an option to strip shaping points from the route. I don't know what the ramification of that option is, but it sounds like something that could potentially change routing in the transfer process.

Hope this helps!

One point about both MapSource and older GPS units. MapSource didn't allow you to mark a point as non-alerting and many of the older (primarily 3 digit) units wouldn't accept a shaping point anyway. I remember MM stating the only units at that time which would accept a non-alerting point were the ZUMO units.

Thanks to everyone for all the helpful replies. Indeed I had perhaps one waypoint in each itinerary. I will follow your suggestions and add multiple waypoints to my itineraries.

Thanks again, this is much appreciated.

This happened because your 2450 does not support shaping points. Only these devices do: https://support.garmin.com/support/searchSupport/case.faces?...

The workaround is to keep your waypoints as real waypoints. Do not check the Basecamp option to "do not alert."

I used to tell my navigator/watcher/other driver to watch for the little orange flag as we're coming upon it.

Agreed that model doesn't accept shaping points but on devices that don't they're converted to normal viapoints. Why some therefore 'disappear' is the mystery

Aha! I did not know this. But yes, you are correct. I just tried it with a 3490 and the shaping points do transfer over as viapoints, even though the 3490 does not support shaping points. Thanks for the tip!