I'd be interested in that feature too. Especially if when one My Collection is selected, the other does not display on the map. Would be good when planning a trip or activity...it could be isolated from your regular stuff. The subject of "sub-folders" has been discused on this forum and might accomplish similar results.
I've got 4 different My Collections. Backup BaseCamp with your choice of names. Clear everything out of My Collection and build another one. Backup that one. To use one of them, Restore it.
Don't forget to Backup a collection anew when you make changes before you restore another collection.
Currently this is not directly supported. As Dave mentioned, the backup and restore feature can be used to achieve a similar behavior.
We have this on our list of possible future features.
Falagar,
Possible future update?
In my opinion, this feature is the number one critical item in making BaseCamp usable.
That single database just makes no sense to me. What would happen if Microsoft decided that all Excel or Word files should be combined into a single file? The same applies to all jpg or mp3 files being merged into a single file. What were you people thinking?
The way Basecamp is structured it is just too easy to lose important data while experimenting with different routes. Backup/Restore is a clumsy alternative.
I notice that newer GPS units can not communicate with Mapsource, making a usable version of Basecamp even more important.
If there isn't going to be the ability for multiple collections in the near term, then the short term fix seems to be to provide a proper File > Open function that will open a .GDB file as a new collection. And it needs to be accompanied by a proper File > Save As function that will save the current collection to a .GDB file exactly as it is.
As near as I can tell, Backup/Restore is only an approximation of those functions.
Export/Import doesn't do it because Export only allows you to export a list or a selection and not the total collection. And Import insists on importing into a list rather than importing into the collection. Yes, I KNOW anything imported to the list ends up in the collection but it's not the same as simply opening a .GDB file AS the new collection.
The way Basecamp is structured it is just too easy to lose important data while experimenting with different routes. Backup/Restore is a clumsy alternative.
I don't use BC-Win that much ( mostly BC-Mac). How do you easily lose data while "experimenting" with routes?
When deleting an experimental route, if you're not careful, waypoints used to create the route also get deleted.
I don't use Routing that much any more and have not run across that condition. Could you explain the workflow for creating a route whereby you would potentially delete the Waypoints used to create a Route by deleting the Route?
I've got 4 different My Collections. Backup BaseCamp with your choice of names. Clear everything out of My Collection and build another one. Backup that one. To use one of them, Restore it.
Don't forget to Backup a collection anew when you make changes before you restore another collection.
I would love to have other my collections, meanwhile Dave this is a worthy work around for now!
On a side note, I started this thread and almost forgot to check back until tonight working with BC and again realizing it would be great to have multiple My Collections!
