Base Camp waypoints and Track names changed when import from Map Source

BC is a database type file. There can only be ONE waypoint or track or route with the same name. MS allows the waypoints with the same name to be placed in different folders. BC STORES all the waypoints in the same folder. It may list the waypoint in different list or list folders, but there is only ONE waypoint with that name stored on the computer. Search this forum for "list" etc.

Actually, BOTH MapSource and BaseCamp are database programs. MapSource allows you to create many databases. Every file you save in MapSource, regardless of format (e.g. .gdb or .gpx) is an independent database. BaseCamp allows only one database (at least at this time).

In general, databases like every record to have a unique identifier. Both MapSource and BaseCamp appear to use a combination of Type and Name. Examples of types are waypoints, routes and tracks. BaseCamp has types not available in MapSource (e.g. folders and lists). You can have a waypoint named Fred and a track named Fred but you cannot have two waypoints named Fred in the same database (in MapSource this means the same file).

When you import data and see something appended to a name in BaseCamp it means that unique identifier has already been used. For practical purposes, you can think of My Collection as your database – although I am not sure what the programmers intended it to represent - and you can find the pre-existing object there. You may need/want to replace the newly imported object with the pre-existing object and then remove newly imported object from the database or you may want to change the name of the newly imported object.

FALAGAR, if at all possible, Path should be a part of the unique identifier for folders and lists. For example Tracks(folder)/2013(list) and Routes(folder)/2013(list) should be allowed.. This should be a very high priority as it is apparent that some users keep a tremendous amount data and would greatly aid in indexing/cross-indexing objects.

Unique names PER list PLEASE

...if at all possible, Path should be a part of the unique identifier for folders and lists. For example Tracks(folder)/2013(list) and Routes(folder)/2013(list) should be allowed.. This should be a very high priority as it is apparent that some users keep a tremendous amount data and would greatly aid in indexing/cross-indexing objects.

YES!

I create lots of "route files" for dualsport motorcycle groups to follow. With MapSource, we had enjoyed some consistent patterns in route/track/waypoint naming. For example, a 2 day ride event might have routes named like so:

• DAY1-A
  
• DAY1-B
  
• DAY1-C
  
• DAY2-A
  
• DAY2-B
  

Riders understand on day 1 to load DAY1-A and when it runs out, load DAY1-B, and so on.

With Basecamp, we have to come up with unique names every time. Sucks.

I've been using Basecamp a lot, and other than this, I really like Basecamp. Like others, I struggled a bit making the change from MapSource, but Basecamp really is a better product with most of the features I felt MapSource was missing. E.g. THANK YOU for the ability (finally) to convert tracks into routes and routes into tracks. I also really enjoy the simple point erase and track/route cut tools.

This issue is quite annoying. +1 vote for allowing non-unique names. Ok, it's a database, what's the problem storing a unique identifier (e.g. number) with every data point (it doesn't need to be shown anywhere, just use it internally as UID)?
It's annoying and stupid to have to rename stuff.
Practical example - on my trips I mark water crossings with waypoints, and I call all of them "river crossing". Upon import to BC they have numbers. But for me they are all river crossings, I don't care/need/want to see their arbitrarily assigned meaningless numbers.
Please fix/implement this!

I should point out that the change I suggested only applies to organization objects in BaseCamp (folders and lists) and not to gps objects (waypoints, tracks and routes). The suggested change is suppose to be implement in version 4.2.

With respect to gps objects, a unique ID number has its own problems. As a practical example, a user migrating from MapSource to BaseCamp would likely end up with lots of waypoints with the name Home. It is unlikely that deleting all but one would be possible since each will likely appear in one or more routes. The problems are not that much different than what users currently face.

This limitation has been around historically because many device required waypoints to have unique names.

I believe this might not be the case anymore, so this might be changed in a future version. But it's not currently on our to-do list.

I would also agree that working with waypoints, especially when creating a route with numerous waypoints, can be frustrating. Maybe I create routes differently than the average user, but this is the short version….

On the map, I create a waypoint. I name it when I create it. ie the first waypoint on the route would be numbered H 001, then H 002, etc. until I get to the end. So, the waypoints on the route would be H 001 – H 067. Then, I come to find out that a few years ago I had created a route using the letter H. Without any warning, the database uses my new “H” route but sees another “H” route in My Collection and adds another number to my new “H” route. ie on the new route H 001 becomes H 0011.

I would be more than appreciative if the program could be updated to warn me (Waypoint already exists, choose another name). Ironically, while I’m creating the route, if I try to insert the same waypoint number, ie H 022 and try to name the next waypoint H 022, it will tell me that it’s an invalid number and make me rename it. BUT, it won’t tell me that the entire “H” series has already been used.

And secondly, it would be really helpful that, when duplicate waypoint names are identified, that I can rename one entire set of waypoints as a batch (rename all of them at the same time) instead of one at a time. A simple example would be to select H 001 – H 067 by selecting them all, then selecting rename all from “H” to say “HD” without losing the numbering. Simply, a find and replace feature where I could find “H” and replace it with “HD” would be great.

Falagar commented way back in 2013. I think he's now moved from the Basecamp team to Virb. I'm going to close this thread, please re-raise any issue you think now exists in the latest Basecamp version in a new thread. Thanks.