Related

joining 2 tracks, but joined track and summary only keep the info from one track

Former Member
Former Member
Looking for an answer to the following dilemma. I recently returned from a 53-mile, 5-day trip in the Sierras, with everything from deep forest cover to alpine summits including a quick tag of Mt. Whitney. I had 5 days of data and on some of the days, due to my own inexperience, I had 2-5 tracks recorded per day. I was able to successfully join all the multiple-track days into 1-track days except for one day, explained below, which I hope someone can help with.

I tried to join these two tracks (with end of first and beginning of second virtually on top of each other), but the Basecamp joined track will only show either one set of data or the other, not both, but the track on the map shows the entire joined track. For example, I have a 1.1 mile and 10.1 mile track, and when I join them the summary shows all the data for the entire 11.2 miles including the number of track points, but the summary only shows a distance total of 1.1 mile?!

Summary: 2 tracks
track 1: distance 1.1 mile 216 track points
track 2: 10.1 mile, 1613 track points

joined track: distance 1.1 mile, 1829 track points?? So you see Basecamp joined the tracks with some info from one and but all info from both tracks.

zipped gpx files attached. If another format is better, let me know please. Thanks.
  • 0
    Your device exports summary data from the trip computer along with the track. When the tracks were joined the summary data for the first track was kept. This is something that BaseCamp probably should not due and should be addressed.

    A recalculation of the summary statistics can be accomplished by deleting a single point and clicking in the summary area. Choose a point with a small leg length or one that occurs during a relatively straight part of your track. If you do not like your choice, the change can be undone with ctrl-z.

    If you feel you must keep all of the data points, export the joined track as a gpx file. Using a text editor like Notepad, highlight and delete everything from and including <gpxtrkx:TrackStatsExtension thru </gpxtrkx:TrackStatsExtension>, save the file (make sure .txt does not get appended) and it should recalculate the summary stats from scratch when imported into BaseCamp. This information is near the top of the file and before <trk>.
  • Former Member
    0 Former Member
    Velopedo, I've ran into the same issue a few times now. It drives me nuts. It'll only show the information from the first track, and that's it. Although if I look at the elevation profile it will show the complete track.

    Today I was mapping a new trail, but my batteries were low; got the low warning partway through, so I saved the track when I started heading back around, then started recording again. That way I'd at least have the most important bit if my batteries died before getting back home, at least. They lasted until I got home to save the 2nd track, then I joined them in BaseCamp: track 1 was 7km and track 2 was 6km. Joined track was 7km. haha Calories, distance, time, etc. was all from the first track. Only the actual mapped route and elevation profile was overall accurate. Weird stuff and certainly not expected behaviour for joining tracks!

    Sorry for the bump, but I just had this come up again today and decided to search around to see if this was a Garmin Basecamp bug or oversight. Looks like an oversight. Should really be addressed, IMHO. Doesn't look like it would be a major bit of code to tweak.
  • 0
    Have you tried the trick mentioned above by BTLAAKE? Deleting a point forces the track to be recalculated.
  • Former Member
    0 Former Member
    Velopedo, I've ran into the same issue a few times now. It drives me nuts. It'll only show the information from the first track, and that's it. Although if I look at the elevation profile it will show the complete track.

    Today I was mapping a new trail, but my batteries were low; got the low warning partway through, so I saved the track when I started heading back around, then started recording again. That way I'd at least have the most important bit if my batteries died before getting back home, at least. They lasted until I got home to save the 2nd track, then I joined them in BaseCamp: track 1 was 7km and track 2 was 6km. Joined track was 7km. haha Calories, distance, time, etc. was all from the first track. Only the actual mapped route and elevation profile was overall accurate. Weird stuff and certainly not expected behaviour for joining tracks!

    Sorry for the bump, but I just had this come up again today and decided to search around to see if this was a Garmin Basecamp bug or oversight. Looks like an oversight. Should really be addressed, IMHO. Doesn't look like it would be a major bit of code to tweak.



    Hello Waldenman,

    The problem with Velopedo's file was there were corrupt timestamps at the end of track1. When those last few timestamps are deleted the files join correctly and all the data shows the correct distance and gain etc.

    Check your tracks for odd dates or otherwise corrupt data and remove it and then join the tracks again.

    There is nothing wrong with the BaseCamp software with respect to joining tracks if the individual track data is okay. :)
  • Former Member
    0 Former Member
    Problem fixed!

    Hi all and thanks to BTLAAKE for the fix. It worked! I was able to join the tracks successfully before I read the remainder of the posts, including the suggestion from DATEZZ.

    I'm now going to try DATEZZ's suggestion, and probably would have done this first had I logged back in before going the BTLAAKE route. Either way, thanks for the help, I'm back on track now.

    The corrupt time stamp is interesting. My thoughts are: due to the rather long days on trail, and my inexperience with the GPS (it was my first trip with it), I was using a combination of auto start/stop, manual stop start/stop and battling with inferior batteries that drained really quickly. Knowing where I was when the corrupt time stamp issue came up and the frequency at which I was stopping and starting the unit while route finding in this particular area, I could see how it got corrupted.

    Thanks again for help.
  • Former Member
    0 Former Member
    DATEZZ time stamp comment was spot on: problem fixed

    As soon as I hit submit on my previous post, I knew I should have taken the 30 seconds to try DATEZZ's suggestion. Well, it actually took me about 15 seconds and the tracks joined successfully. It was immediately clear what the "corrupt" time stamps were that DATEZZ saw in my file that I needed to delete. Until I can time travel, I suppose the track points should follow in chronological order. :)




    Hello Waldenman,

    The problem with Velopedo's file was there were corrupt timestamps at the end of track1. When those last few timestamps are deleted the files join correctly and all the data shows the correct distance and gain etc.

    Check your tracks for odd dates or otherwise corrupt data and remove it and then join the tracks again.

    There is nothing wrong with the BaseCamp software with respect to joining tracks if the individual track data is okay. :)