Won't import .gdb files basecamp 4.1.1

Former Member
Former Member
I moved my old map files from my old MBP to the new one running OS 10.8.3. I was able to move 'my collection' via backup and restore, but BC won't import my .gdb files, just displays an error message that the file could not be found. Also fails to open .kmz or .kml files, saying they are invalid.
  • Former Member
    0 Former Member over 12 years ago
    I moved my old map files from my old MBP to the new one running OS 10.8.3. I was able to move 'my collection' via backup and restore, but BC won't import my .gdb files, just displays an error message that the file could not be found. Also fails to open .kmz or .kml files, saying they are invalid.

    I'm having the same problems. Anybody a solution?

    Vincent
  • Former Member
    0 Former Member over 12 years ago
    I moved my old map files from my old MBP to the new one running OS 10.8.3. I was able to move 'my collection' via backup and restore, but BC won't import my .gdb files, just displays an error message that the file could not be found. Also fails to open .kmz or .kml files, saying they are invalid.


    Same problem here, OSX 10.7.5. Have to convert gdb's to gpx using Mapsource on Windows (...), the gpx then loads fine. Did anyone find a more elegant workaround, or beter still - a fix?
  • Former Member
    0 Former Member over 12 years ago
    Same problem here, OSX 10.7.5. Have to convert gdb's to gpx using Mapsource on Windows (...), the gpx then loads fine. Did anyone find a more elegant workaround, or beter still - a fix?


    Running 10.8.3 on iMac with new BC 4.1.2 release, hoping 4.1.2 update would resolve this import issue which was introduced when I updated to 4.1.1. I was running previous BC version (prior to 4.1.1) on this OSX without any issues... now all my GDB files 'could not be found'. :mad:

    Any non-windows based solutions would be appreciated!!!
  • Former Member
    0 Former Member over 12 years ago
    Just as a data point, I am running v4.1.1 and have no problems importing my old GDB files. Have you done a Backup of your data and then removed and reinstalled BaseCamp?

    Cheers,
  • Former Member
    0 Former Member over 12 years ago
    Just as a data point, I am running v4.1.1 and have no problems importing my old GDB files. Have you done a Backup of your data and then removed and reinstalled BaseCamp?

    Cheers,


    Removing and re-installing BaseCamp does not solve the problem, too bad...
  • Former Member
    0 Former Member over 12 years ago
    Bummer. When I have issues like this that are not widespread in the community, I usually backup my files in the user\Library\Application Support\Garmin\BaseCamp\Database\4.1\ folder and then completely uninstall BaseCamp. Including removing all of the BaseCamp folders in the previous path. Then I reinstall what should be a clean empty BaseCamp.

    Normally I'd suggest installing the latest version (v4.1.2) but I'm having issues with that one not loading RESTORE files.

    Cheers,
  • If you want to move your data from one computer to another, you should use backup and restore. The internal files are not intended to be manually importable and you would lose your lists and folders even if it did work. Backup and restore should work for all but a small handful of users and that issue is being fixed in 4.2. The GDB files that are stored internally are not the same as exported GDB files and as such don't work the same.

    If for some reason backup and restore from within BaseCamp isn't working, you can zip the entire username/Library/Application Support/Garmin/BaseCamp folder and unzip it in the same location on a different computer. Note that until 4.2, the paths on the two computers must match, including username. Normally the internal paths are fixed when restoring inside of BaseCamp, but that step obviously won't occur if you are doing this manually. This caveat is removed in 4.2.
  • If you want to move your data from one computer to another, you should use backup and restore. The internal files are not intended to be manually importable and you would lose your lists and folders even if it did work. Backup and restore should work for all but a small handful of users and that issue is being fixed in 4.2. The GDB files that are stored internally are not the same as exported GDB files and as such don't work the same.

    If for some reason backup and restore from within BaseCamp isn't working, you can zip the entire username/Library/Application Support/Garmin/BaseCamp folder and unzip it in the same location on a different computer. Note that until 4.2, the paths on the two computers must match, including username. Normally the internal paths are fixed when restoring inside of BaseCamp, but that step obviously won't occur if you are doing this manually. This caveat is removed in 4.2.


    This still doesn't solve the problem of importing GDB files fails. This is really a show stopper.

    A work around is granting permissions to the folder containing the GDB file, unfortunately Base Camp only queries for permissions if you have more than one ISO mounted.
  • There is an issue with importing GDB files in the current App Store version of BaseCamp. It will be fixed when 4.2 gets posted and eventually accepted to the App Store. If you don't want to wait, you can switch to using the web release version of 4.1.2 (http://www.garmin.com/mac) until 4.2 goes live on the App Store. Sorry for the inconvenience.
  • Former Member
    0 Former Member over 12 years ago
    It's a problem with Basecamp. On my mail to Garmin I got a generic mail about how my gdb file is corrupt and I should ask for a gpx file, which means they at least did not understand my very ppor English. I did some digging around on my Mac, and found a workaround. It's a sandbox permissions problem. Happy to share it with you guys: http://rolfje.wordpress.com/2013/05/03/basecamp-import-problem-fixed/

    If/when Garmin fixes their sandbox profile on the appstore in release 4.2, this may be a thing of the past. Until then, use my workaround.