Basecamp keeps improving, but......

Former Member over 12 years ago

Being able to create new databases helps with my Basecamp frustration to some extent.

However it is rather cumbersome to make the switch: Edit > Options > General > Choose a new database. Then go back and forth to copy key waypoints. Perhaps a new toolbar as a starter?

Personally, I'd prefer to be able to bring up more than one instance of Basecamp and be able to copy items between instances of Basecamp like the way Mapsource works.

I really do not like the database concept. I want each trip to include multiple routes, waypoints, tracks, etc. and be in a separate file. Yes, "My Collection" does do that, but it does strange things with waypoints. I'd like to have only one waypoint called HOME, not HOME1, HOME2, etc. I can't imagine what it would be like if all of my MS Ofice files resided in a single database and interacted with one another.

I use Mapsource to plan trips on my desktop PC. I then transfer that one file to a laptop and don't want to drag along the entire database. At this time, I have 9800 track segments in the database. Thats ok, but I'd prefer to leave them on the desktop and not take the time to copy 9800+ files in the database that I'm not interested in at the time.

At this time, I'm still not a convert from Mapsource, but do see the day when Mapsource just won't work with newer maps and or GPS receivers.

The current Basecamp will allow me to do what I want, but it sure makes the task very unpleasant when compared to using Mapsource.

Keep plugging away and eventually Basecamp will get there. Thanks for the effort.

Also, no big deal, but isn't it time to include Mapinstall features into Basecamp?

0 Former Member over 12 years ago

I really do not like the database concept. I want each trip to include multiple routes, waypoints, tracks, etc. and be in a separate file. Yes, "My Collection" does do that, but it does strange things with waypoints. I'd like to have only one waypoint called HOME, not HOME1, HOME2, etc.

I believe you get these multiple, incremented waypoints from importing the same waypoints into your basecamp database. I experienced the same thing when I imported 10 years of motorcycle trips into a common basecamp DB.

0 C14_Rider over 12 years ago

...might be closer than you think...

I'd like to have only one waypoint called HOME, not HOME1, HOME2, etc.

I found that once I dedicated myself to using BC exclusively, that problem took care of itself. As Adamkski noted, and for me as well, it was mostly a product of importing multiple files with a common waypoint like Home. Once I settled on the one correct Home and made sure all routes used that one, and deleted the others, and stopped importing MS files, there are no more multiples. This became realistic for me when they added the option of NOT duplicating waypoints used in a route when you duplicate that route as a starting point for creating another. Don't remember when that was, but that really helped, I use it EVERY time.

And it can be handy when you realize that a waypoint location isn't quite right, and when you move it to the right place, it is then automatically in that right place in all routes that reference it.

Also I used to wonder what routes used certain waypoints over time, and with separate files that was difficult. Now I can see that at a glance in the Waypoint Properties, References tab. Nice.

I want each trip to include multiple routes, waypoints, tracks, etc. and be in a separate file.

That's exactly what I wanted also. I found that if I create a list for a trip and think of that list as analagous to the MS file, I can set it up the same way, with limited waypoints, only routes for that trip, etc., and send that whole list to the device just like I used to send the entire MS file. Only what's in that list goes. Almost no difference.

Also, no big deal, but isn't it time to include Mapinstall features into Basecamp?

It's there, Maps/Install Maps invokes MapInstall if your device is connected.