Things that I cannot accomplish in Mac BaseCamp

The MapSource (MS) shaping points were discussed in a previous thread, I can understand why Denny wants BaseCamp (BC) to have MS shaping points. BC has BC shaping points that behave differently. They show in the route window and on the GPS but do not show in the GPS BC list. The nuvi 7xx and above (I think) accepts uploaded routes and I think the behave the same as your Zumo.

I would think most users do not have a do not have an issue with the way BC handles shaping points and it would appear to my your dilemma could be solved with and option.

What if the shaping points in the routing window had 3 circules following each shaping point and you could select the default box bulleted upon creation in preferences. The three boxes would be BC for the current behavior and the default until the user changed. MS for the behavior Denny is requesting. Wpt for waypoint behavior which would create waypoint in the BC waypoint list. The Wpt shaping points would allow users with GPS's that do not support uploading of routing to easily to upload waypoints that define the route.

Aaa Haaa..... Semantics.
via points vs WayPoints
Properties pane vs MyCollections Sidebar

I think you want them to show up in the MyCollections sidebar.
Waypoints will show up there. If you want Waypoints you must use the Waypoint tool to create those, then drag the route and drop it on the Waypoint.


They (viapoints) do show up in the route Properties pane:


I think a dropdown list in the Point Properties pane, under the advanced tab would be cool. A way to change the type:



MapSource shows you the type of point, but does not allow you to edit the type.

There is a very good reason for this. (difference between viapoints and Waypoints)
Most Garmin units have a limit. Only X number of waypoints per route.
If you exceed that limit the route will be truncated when imported, or will not import at all. Viapoints do not count, you can generally have as many of those as you want. There is still a limit, but that limit is much larger than the WayPoint limit. The exact value of those limits varies by model. Generally the models with higher limits cost considerably more.

+1 on Denny's post on via points. Keep them simple and innocuous. They should be totally independent, unrelated and different than Waypoints. Waypoints are locations you want a record of, via points are only needed as long as the route is being used. When the route is deleted, they should disappear.

I'm sorry to keep coming back to what's becoming a broken record but the ability to move the via points as you can in MapSource is another missing feature.

I'm sorry to keep coming back to what's becoming a broken record but the ability to move the via points as you can in MapSource is another missing feature.

You move via points the same as you move waypoints. Alt-click with the selector tool and dragging will move the point.

You move via points the same as you move waypoints. Alt-click with the selector tool and dragging will move the point.

My apologies. I've tried (I thought) everything and waited for a visual clue that I was in move mode. It never occurred to me to just move the pointer and see what happened. I do see now that the graphic I've used for a via, being a tiny dot, moves with the pointer. I was expecting an indicator/rubber band line. Again sorry.

May I suggest that Help section be changed to reflect the fact that the process works with both via and way points? I totally ignored the help section returned by search due to the results all being waypoint instructions.

I noticed that also works with the command (pretzel) key.
And it behaves slightly differently than the option (alt) key.

I've tried (I thought) everything and waited for a visual clue that I was in move mode. It never occurred to me to just move the pointer and see what happened. I do see now that the graphic I've used for a via, being a tiny dot, moves with the pointer. I was expecting an indicator/rubber band line.

I agree that it is much too subtle when moving a small icon like the default via point icon. We'll see if we can address that in a future release.

Aaa Haaa..... Semantics.
via points vs WayPoints
Properties pane vs MyCollections Sidebar

I think you want them to show up in the MyCollections sidebar.
Waypoints will show up there. If you want Waypoints you must use the Waypoint tool to create those, then drag the route and drop it on the Waypoint.

Actually I very pleased with the way waypoints and shaping points are currently handled by BaseCamp. I was just trying to help with MapSource addiction. If I understand, even if BaseCamp handled shaping points exactly as MapSource and you could set a preference to create MapSource shaping points, and other users had other options like creating a waypoint form a shaping point which KillTimer states they don't need, the only solution for you guys is MapSource ported to the Mac. Parallels and VMWare run MapSource extremely well.

When you consider the number reading the Mac BaseCamp forum and the number of request for additional features, the developers already have a killer app and it is still in beta.

Garmin is giving you free software and asking how can they make the software meet Mac users needs which vary tremendously. Truth be known, most of use don't know what we need until Job tells us. All you guys can say is MapSource forever. For me MapSource was useless, I only take two or three trips a year that needed route planning. I would spend hours learning MapSource maze of features and by the time the next trip rolled around I had forgotten everything. Currently my iPhone blows my gamin plus III away for navigation but my Nuvi 750 blow the iphone away. Not so much in features but connivence and planning. You can't plan on a five inch screen and the iPhone is smaller. My iPhone goes on my side not the windshield. BaseCamp is a tool to sell Garmin GPS products. As such it must be a product any mac user can be up, running and productive in a matter of minutes. Something that can be used one or twice a year without a refresher course. Most Mac users know how to use iTunes & iPhoto and BaseCamp can build on that knowledge. Yes it helps that it is appealing to the eye with smooth text characters. This does not mean BaseCamp can't be a full featured mapping application that meets the most demanding requirements. However, if Garmin is to maintain it lead in GPS navigation, BaseCamp must default to an intuitive, easy to use application for the average casual user. With proper planning the power user features can be added. If these features follows the iTune, iPhoto model of ease of intuitive ease of use, I think Garmin will maintain their lead but if the port MapSource, the number user that eat, sleep, and live to create routes is not enough to keep Garmin in business.

One more thought, most Mac users don't want to add a 100 shaping points to a route. Most Mac users just want BaseCamp to know the route they prefer. I would think additional routing options and maybe interstate avoidance could create routes that required less shaping. I would think less shaping points would be better for everyone, even you professional routers.

I think you are missing the point.
We paid a premium price for our devices that support "recalculation off" and the behavior of these type of shaping points.

We just want the software to support our devices on any computer platform.

I guess I am but when I google "Gramin recalculation off", google doesn't get the point either. I just think that if you could define the functionally you need in a request that did not require scraping BaseCamp and porting MapSourse, your chances of seeing the feature would be much greater. Just remember for ever user defining routes with 25 shaping points, there is 1000 time more buying GPSs to geocache, hunt, fish, explore the outdoors or navigate the roads via the interstate.