Waypoint I thought I could not delete.

Your observed behavior is "working as intended". The route tool will create a "map point" instead of a user waypoint if you click on map data such as a road or POI. There are several reasons for this, but one of them is so the points used for creating your route, including the "shaping" waypoints automatically are deleted if the route that contains them is deleted.

It is best to create the waypoints you want using the waypoint tool or Find, then use the route tool to connect them.

It is best to create the waypoints you want using the waypoint tool or Find, then use the route tool to connect them.

Yes this is a nice feature but if your Nuvi won't accept routes, or in my case where most of the time I prefer to to just upload waypoints, I usually create the waypoints, select them and create route from the menu. Uploading a route is a 3 step process with basecamp and roadtrips requires another step. With BaseCamp, drag your route to the nuvi, on the nuvi got to MyData, import route from file, where to, Routes, select route and decide where to start.

Most of the time it is easier to just upload one waypoint, where to, favorites and select the waypoint.

Something I think would be pretty easy to code and helpful would be a button to create waypoint in the routing dialog window that became active when you select a shaping map waypoint.

The mapping waypoints are a great feature. They really help to keep your MyCollection folder clean.

Another thought for BaseCamp, What if when you drag a route to a GPS that did not accept route it transferred the waypoints used to create the route, all except the starting waypoint. If you drag a route to a GPS that accepts routes, you get an option to upload routes or waypoints.

What if when you drag a route to a GPS that did not accept route it transferred the waypoints used to create the route, all except the starting waypoint. If you drag a route to a GPS that accepts routes, you get an option to upload routes or waypoints.

I think this is a good idea, and akin to a feature we've discussed before. One difficulty is the fact that the unit does not advertise that it doesn't accept routes, so the software blissfully sends them to the unit. We'll explore ways to give the user a better experience when transferring to a device that doesn't accept routes.

Hmmm, the unit does advertise it's model number doesn't it?

Seems the software should be informed about the capabilities of all Garmin units based on the model number.

As you might have noticed, Garmin puts out a LOT of units per year. The software could never be updated often enough to keep up with them. We will work on a solution that will allow new devices to be optimized as they come out.

As you might have noticed, Garmin puts out a LOT of units per year.

I have noticed, 9 models of the oregon and the firmware varies greatly between the oregon models plus multiple models of Dakota, etrex, Colorado, GPSMap 60xx and 76xx. All these for handhelds for just one of many categories, handheld mapping GPSs. I never requested mounting the GPS and dragging objective because I figured all the different models made it almost impossible but now we have that feature in BaseCamp.

One more thought on and easier way for users to upload mapping waypoints (special waypoints used to avoid clutter in My Collections when creating routes). I have not tried it but I assume if you drag a route to a GPS that does not accept uploaded routes, nothing happens. Could you not just provide a dialog with and option of uploading waypoints or routes. Waypoints would always move and routes would move if the GPS accepted routes.

I think the best option would be to allow users to drag the mapping waypoints from the routing window. It should be pretty easy to code and give the user the most options in that a user may only want one waypoint uploaded from a route constructed from several mapping waypoints.