Like most longtime Mapsource users I have quite a collection of past and future trips stored in separate gdb files. As I use my gps for motorcycle trip navigation, I also have an extensive collection of motorcycle roads I've ridden, or plan to ride in the future. Additionally, I've entered the routes from all three Destination Highways books into Mapsource files which I reference and string together when I'm planning routes.
Over the past weekend I thought I'd give Basecamp another shot for planning an upcoming ride to Northern CA. I started by importing my DH Northern California routes into Basecamp. I created a folder for that particular book, and create a list with a folder for each section of the book and it's associated routes. Worked great!
Next I created a folder for the upcoming trip and within that folder started a new list to stored the daily ride routes. I also copied the associated DH lists in the area I'll be riding into this folder. I REALLY like the ability to click between my route list to see my planed routes, and the being able to click on the trip folder to see a composite view with the DH routes. I can then adjust my daily rides to blend in the great roads in NC.
What concerns me is these DH lists/routes are linked back to the same 'my collection' parents. If I accidentally tweak one of these routes I've altered the source which I want to be a static representation of the books.
I <could> dupe the DH routes one by one to create unique copies, but that takes a while. If I duplicate one of the source DH lists a new unique list is created with a '1' at the end, but the routes contained within it are the original routes and are link to the source. It would be nice if duplicating a list to make a new stand alone list also created new stand along routes. It could at least give you the option.
I realize I could make backups to try and protect myself, but I'd have to know I did something to alter one of the routes. With everything in one big database you don't always notice mistakes like this right away.
I know I can create desperate databases, but when you create new DBs they are empty and there doesn't appear to be any easy way to export the folder/list structure into these new databases. You end up with one big collection of the routes and waypoints with the structure.
I also know I can just copy the DB files to create a nice backup of everything to protect my work, but again, without a way to import just parts of one DB into another, it's the same as just making backups which are subject the same data loss if I don't notice a mistake right away.
So, it would be nice to:
1. Be able to duplicate lists and even folders to create stand alone copies of the contents which are independent from the source.
2. Have a way to copy parts of one database into another.
3. Be able to rick click and 'protect' or toggle a list or folder to read/only, etc...
Anyone know of any neat tricks to accomplish any of these?
Like I said, I've just started to scratch the surface of Basecamp so I may just be missing something here that's obvious to someone else.
Thanks!
Adam
