Missing elevation and timestamp from transferred tracklog files - Help!

Do you still have the old computer?  Do you still have the BaseCamp Backup file?  Were you using 4.7.2 on the old computer.?  What folders are you seeing in the C:\Users\username\AppData\Roaming\Garmin\BaseCamp\Database folder.

You have not toggled something that would cause this.  On a few occasions I have lost time stamp data while manipulating tracks and once lost I have not found a way to restore them (even via undo commands).

If you still have the backup file and were using and earlier version of BaseCamp, I would suggest uninstalling BaseCamp and installing the earlier version then restore the backup.  If you want to update to 4.7.2, you can do so after restoring the backup.

Thanks Indeed for the detailed response. Good advice. Thanks particularly for your comments about recovering lost time stamp data.  Suspected as much.  Darn. The short answers to your queries are:  Don’t have old computer, but have multiple full system Acronis backups of the old computer. Yes, have at least the last Basecamp backup from old system, and likely several previous; will have to get into old Acronis .tib backups to verify. No, using older version of Basecamp on old computer; installed 4.7.2 on new computer via download from Garmin. As to the AppData/Roaming file, will have to get to that later today.  Will advise.  Thanks again.  Jim

To followup yesterday's post, following are screenshots of >>C:\Users\username\AppData\Roaming\Garmin\BaseCamp\Database<<  and its subfolders:

Further, in >>Basecamp there is a second folder, >>TrackSegments.  It holds 500+ small, no-extension files totaling ~40 MB. Same folder name as in subfolders 4.4 and 4.7, but apparently different - or maybe, aggregated - data.  What's up with this, do you suppose? Screenshot of >>Basecamp>Tracksegments properties:

The TrackSegments folder was added at some point during the development of BaseCamp.  I don't recall Garmin giving any details on what it contains other than it was done to improve program efficiency.  I believe there will be one file for every track.  You can find the number of tracks you have by opening BaseCamp, selecting My Collection and clicking on the little funnel at the bottom of the list of items.

The folders 4.4 and 4.7 refer to different versions of BaseCamp (updating versions does not remove legacy folders).  I wasn't sure if making a backup would backup legacy folders.  

Back to your issue.  I would check to see if the number of files in the two TrackSegment folders (in 4.4 and 4.7) are the same and correspond to the number of tracks in My Collection.

I recently had to reinstall BaseCamp and restore a Backup file and did not have your issue.  But, the Backup was restored to the same version of BaseCamp.  An unexpected glitch in restoring a backup from one version to a different version is something I can see being missed.

I suspect you weren't using BaseCamp 4.4.x on your old computer (AllData file has 2019 date) and therefore the file sizes of corresponding files will differ.  So, copying and pasting files in the folders 4.4 to 4.7 will result in loss of data and may cause other problems.

Since you have the .backup file, I would uninstall BaseCamp, delete the 4.4 and 4.7 folders if they remain. Restart your computer and install version 4.6.2.  The location where I used to retrieve legacy versions of BaseCamp is gone, but this site seems to have them https://garmin-basecamp.software.informer.com/versions/

If someone knows a more reliable source, please chime in.

Legacy versions of BaseCamp can also be found at: https://www.gpsrchive.com/BaseCamp/index.htm

Bottom line up front:  With your generous assistance I've been able to restore my track files to full functionality, including timestamp and elevation data. Here's a screenshot of the track 'properties' popup box substantially similar as first posted.  Note the timestamp and elevation fields this time:

Achieving this required a few false starts and quite a bit of frustration.  The reason is that the Basecamp uninstall utility does not really uninstall all of it!  

Specifically the folder >C:\Users\username\AppData\Roaming\Garmin\BaseCamp\Database< is not removed by the uninstaller.  So, any subsequent installation - any version - will 'read' the corrupted data. For example, uninstalling Basecamp 4.7.2, then reinstalling the same version (yes, I tried this) or an older version recaptures the corrupted data.  

Basecamp apparently rebuilds the \Database folder if it looks where it ought to be and does not find it.

In any event, deleted the \Database folder.  Then reinstalled using the Basecamp 4.6.2 installer.  Then used the File-->Restore menu item to load an older .backup file from late 2019.  (No problem there, 'cuz with the Covid Crisis and all I've not done any travel worth archiving.)  

That did the trick.  What a relief!

(It's since occurred to me that simply loading the old .backup would *overwrite* the existing corrupted data, maybe would accomplish the same thing.  However, being not the brightest bulb in the chandelier, I did not think of this.  If anyone reading this tries this overwrite method, YMMV and please advise the results.)

Interestingly, the most recent .backup file from the old computer turned out to be corrupted also, and in the last Acronis .tib backup from that system the subfolder \4.7 was present.  So likely I had updated to Basecamp 4.7.0 or 4.7.2 before creating the final .backup file.  Given this, I'd have to say the move from one system to another had little to nothing to do with causing the .backup corruption.  Of course, this begs the question of what actually caused it.  Guess I'll have to leave sleuthing down that one for another time.

So, once again, many thanks for your advice and hand-holding on this.

Jim

PS: On first running the new install of Basecamp, it might pop a dialog box stating that it has found "old" .backup files and asking if we want to delete them.  Seems like a bad idea to do this, particularly if the restore .backup file  is on the C:/ drive... Can always go back and delete them later after all issues resolved.  JLM

I was using Basecamp with an older etrex22x and was also carrying a SPOT device.  I decided to upgrade the PLB and thought it would be good to combine the gps and PLB functions available with the inreach mini2 with explore, only to find out when I went to transfer gpx files that 1) if you try to transfer with one collection containing multiple tracks, you loose the track names and 2) even if you transfer one at a time, you loose elvation and timestamp data which really reduces the value of the track.  After reading this forum today,  I contacted Garmin support and I'm very disappointed.  First, the help person said she'd try to duplicate the problem herself, then after I told her this was a problem that is not new, she admitted that it was known with no resolution date and if I wanted, she could help me file an issue to see if they were still working on it.  I let her know how disappointed I was and that garmin had dropped the ball.  She explained to me that basecamp  isn't being discontinued, it just isn't being maintained.  I'm not sure what the difference is,  sooner or later it will break!  She also told me that if I loaded too many tracks to explore web,  Garmin would contact me to remove some to save space,  so,  explore is not a replacement.  Really disappointed to say the least.  I'm an engineer,  if I offered a solution without backward compatibility,  I would be fired.  Working with software providers before,  if you want an issue fixed, you need to bury the company in complaints.  I think that is what we need to do.