Back-Up Strips out Speed and Elevation Information from Tracks

Hi All,

I am not sure, if this has been already discussed. I tried to search on this section, but did not find anything related and hence opening up a new thread. (Please close this one and point me to an already existing thread on this topic, if there exists one).

For some time now, I have been noticing that none of my old tracks seem to have speed and elevation profiles. I was not sure what was taking it out.

I just returned today after a 600km road trip. And by chance it struck me and I tried the following experiment:

1. I imported the new tracks from the device.
2. I checked and confirmed they had speed and elevation data in them. I looked at elevation profiles and they looked fine.
3. I created a back-up of the entire basecamp data base including the recently imported tracks.
4. Now when I restore from this backed-up data based and tried see speed/elevation profile its gone!

Have any of you noticed some thing similar ? Or am I missing something very basic?

Thanks
  • Former Member
    0 Former Member over 7 years ago
    Hello Galoi,
    Just for some background info....I use a PC and have done several restore operations using the backup files and have never lost speed or elevation so it might be a MAC only problem?? That does not help your situation but it tells you and any tech people you talk to that the PC version does work properly.
  • Former Member
    0 Former Member over 7 years ago
    If you are using a Mac there are several, possibly more efficient, methods of backing up basecamp. Firstly, you should likely be using Time machine as this backs up every hour, I use 2 time machine backup drives, one on my network and another portable hard drive for when I am travelling and away from home more than a few days.

    Secondly I use an app called "Sync folders Pro" (it's on the Mac app store) to create an automated backup (Real Time Sync) to a designated folder on my local dropbox folder, so as long as I am connected to the internet (extremely likely), I know I have the most up to date backup of my entire basecamp database in an alternate location on my mac and also up in the cloud on dropboxes servers. I also include the "preference" file, so I can restore everything exactly how it is in 2 clicks.

    With all due respect to Garmin, basecamp is a fairly average app (that unfortunately we must use), and it's not exactly updated frequently enough for me to trust that someone at Garmin has this at the top of their list. Bearing in mind it is also STILL 32bit should suggest it is somewhat off the radar for Garmin. I definitely trust well developed, dedicated backup apps to take care of my stuff.
  • Hello Galoi,
    Just for some background info....I use a PC and have done several restore operations using the backup files and have never lost speed or elevation so it might be a MAC only problem?? That does not help your situation but it tells you and any tech people you talk to that the PC version does work properly.


    Thank you for your note. So looks like a MAC only issue.


    If you are using a Mac there are several, possibly more efficient, methods of backing up basecamp. Firstly, you should likely be using Time machine as this backs up every hour, I use 2 time machine backup drives, one on my network and another portable hard drive for when I am travelling and away from home more than a few days.


    Hi, I do use Time machine backups. I create a basecamp backup file on my MAC. It then gets backed-up on Time Machine. I was able to salvage at least 60-70% of my logs by re-extracting them out from the device's Archives folder (present on the device) as GPX files and re-building my tracks library on basecamp. I exported them as GDB and backed-up it up on Time Machine. But yes I did lose quite some road trip details.

    None-the-less this looks like a bug to me on the MAC version. I will let other comment on the same. Till then using a simpler alternative (as explained) to resolve the issue.

    Thanks
  • Former Member
    0 Former Member over 7 years ago

    But why create a backup (that has an issue) on your mac if Time Machine is backing up your original Basecamp database anyway in the user Library folder? Just use the original database backup from Time Machine.

    If perhaps you don't realise that Time Machine backs up the User Library, it's because it is hidden by default. You can unhide it to show the original files on your TM backup drive giving you full access to the original (and therefore accurate) time machine backed up database. Hope this helps

    Back to your original post though, I did set up a test account and used Backup basecamp and restored in my test user account on my Mac (macOS 10.13.3 / Basecamp 4.6.3) and I confirm I get the same issue. All speed and elevation information is lost in my recorded tracks. I'd be pretty pissed if I was using this as a backup!
  • But why create a backup (that has an issue) on your mac if Time Machine is backing up your original Basecamp database anyway in the user Library folder? Just use the original database backup from Time Machine.

    If perhaps you don't realise that Time Machine backs up the User Library, it's because it is hidden by default. You can unhide it to show the original files on your TM backup drive giving you full access to the original (and therefore accurate) time machine backed up database. Hope this helps

    Yes that was how even I was managing. Initially I was unaware. But during course of time some where in between (dont know how) the library got reset. That is when I started looking at alternative means to store my date.


    Back to your original post though, I did set up a test account and used Backup basecamp and restored in my test user account on my Mac (macOS 10.13.3 / Basecamp 4.6.3) and I confirm I get the same issue. All speed and elevation information is lost in my recorded tracks. I'd be pretty pissed if I was using this as a backup!


    Thanks for confirming! So it indeed is an issue. I lost some of the good data points. That cant be undone now. So will just be careful going forward and I hope, it gets fixed by Garmin. I also hope they release a 64 bit version soon.