Importing a GDB file wipes out the last one imported every time. WHY?

Former Member over 10 years ago

I am having a problem where each time I import a .gdb file it wipes out the last one I imported. This started recently, I have been importing files for years without this problem. I am currently running Basecamp 4.4.6 on OSX Yosemite 10.10.2. I updated to 4.4.6 BECAUSE I had begun having this problem in the last version, but it has persisted in 4.4.6.

What happens is I import a .gdb file using the import command under the file menu. In the old program you just "imported" and it ended up in "My Collection". Now the import command says it will import to whatever folder or file you have highlighted, but it doesn't. Instead, no matter what I have highlighted, the imported file shows up at the bottom of "My Collection", right above "Unlisted data", just the way it always used to.

The next time I import something that previously imported file disappears, replaced by the new one.

I have tried moving the first file into a folder. The folder empties when I do the second import, even though the second imported file is always placed in "My Collection", not in the folder where the first import was. I have tried re-naming the first import once it's in "my Collection". I have tried importing different files from different sources, and in different orders. It was suggested to me in a Basecamp thread on ADV that I should try duplicating the first import, then re-naming the duplicate to see what would happen, but the "duplicate" command is always grayed out no matter what I select, so I haven't been able to try this.

I have searched around this forum some before posting, but don't see other people reporting this problem. What's going on and how do I fix it?

0 Former Member over 10 years ago

Rename list folder name after import.

Notice the difference in list folder icon after import and after rename.

0 Former Member over 10 years ago

Re-naming imported tracks works to keep them imported

Rename list folder name after import.

Notice the difference in list folder icon after import and after rename.

OK, that's STUPID. It works, and thank you, but why on earth does Basecamp make me do this? Not only is it a counterintuitive extra step that didn't need to be done in the past, but it means that when I am loading tracks to use on a group dirt bike trip, my tracks will no longer be named the same as the tracks given to everyone else. The potential now exists for all Basecamp riders on the trip to have identical tracks with unique names because we've all been forced to re-name, and therefore none of us will be able to communicate clearly which track we are supposed to be using at a given point unless all of us are diligent about re-naming in order to get Basecamp to save & then reverting to the old name, yet another extra step.

(Also, in my own defense, I had tried this before and it did not work for me, but apparently I had tried it in the previous version where I first started having this import problem, and may have lost track & not tried it again in 4.4.6 until now)

0 Former Member over 10 years ago

I know/use this procedure for a long time, and do not know another. I am surprised that it did not happened to you until this version of BaseCamp for Mac.

0 Former Member over 9 years ago

Do I still need to re-name imported files or has 4.4.8 fixed this?

I have recently imported almost 50 custom maps from a friend. Before I slog through re-naming every single one to prevent them from being wiped out by my next import, I thought I'd ask if the new version of Basecamp (4.4.8) has solved this problem?

0 Former Member over 9 years ago

I have recently imported almost 50 custom maps from a friend. Before I slog through re-naming every single one to prevent them from being wiped out by my next import, I thought I'd ask if the new version of Basecamp (4.4.8) has solved this problem?

This issue persists in 4.4.8. The data is being imported into 'My Collection', but is immediately visible by the last imported smart list. This smart list is renamed to the filename of the last imported file. On the next import we rename the 'last imported' smart list again, but your data is still in 'My Collection'. It's just not being filtered by any list.

There is an issue though with us saying we are importing into the currently selected list. We should either add the imported data to this list, or we should just always say we're importing into 'My Collection'. I'll open a case for this.

I agree that it's a pain and counterintuitive, but for now, you'll need to continue doing what mp_gps suggested, renaming the smart list to a regular list.