Track Distance Discrepancy between Summary and Graph

I have opened a case for this.

@JM47048, just wondering if there has been any progress on this issue? Would you please notify me when there is any updated information?

Thanks.
Annie

I have the same problem here.

There has not been movement yet specifically on this. We have it in our queue. Thank you for your patience.

GPX file created by the GPS may be the reason, not basecamp.

There has not been movement yet specifically on this. We have it in our queue. Thank you for your patience.

I was testing out my new Garmin GPSMAP 64 and noticed that a 1.06 mile track was displaying in both Basecamp and GPS as 10.6 mile track. I proceeded to look further in the GPX xml file to see
if both GPS and basecamp just display a precalculated total distance. I found the following xml tag:<gpxtrkx:Distance>17028</gpxtrkx:Distance> which is part of a track stats section. The number shown is in meters and it equals 10.6 miles. Somehow, the GPS came up with this calculation and saved it to this overview section which is used when display information about a track.

When the graph is displayed in Basecamp this section is ignored and the total is computer from each one of the track points in the file which is the reason why it displays the correct distance. I also noticed that the speed is way way off:
<gpxtrkx:MovingSpeed>11</gpxtrkx:MovingSpeed>
<gpxtrkx:MaxSpeed>35</gpxtrkx:MaxSpeed>
It is displayed in km/h so that is 11 km/h and 35km/h. I was walking rather slower pace as I was walking my dog so I am pretty sure I did not reach 35km/h or 21.74 miles/h.

I have to add that the signal of the GPS was very accurate. Looking at the trace on a map is spot on. My problem is just with the stats section. I agree with others with regards to having a place in Basecamp to automatically recalculate the stats based on the points, although it would be better to the get GPX right out of the GPS.

I hope this helps.

Thanks,

Iván

GPX files ignore the settings on devices. Time will be in seconds (or UTC date/time for time stamps), distances (elevations) in meters and therefore speeds in m/s regardless of the settings on the device. So a speed of 11 is in m/s, not km/hr (still very fast).

Best practice until things are fixed would be to reset the trip computer and clear the current track log before recording anything of interest. You should then save the track when the destination is reached. Additionally, deleting a single point will force a recalculation using the logged data. Choose a point that looks off or is in a straight section.

To me, it appears that Garmin is trying to get the trip computer to more closely agree with logged track data, but it still needs work on both device and BaseCamp.

GPX files ignore the settings on devices. Time will be in seconds (or UTC date/time for time stamps), distances (elevations) in meters and therefore speeds in m/s regardless of the settings on the device. So a speed of 11 is in m/s, not km/hr (still very fast).

Best practice until things are fixed would be to reset the trip computer and clear the current track log before recording anything of interest. You should then save the track when the destination is reached. Additionally, deleting a single point will force a recalculation using the logged data. Choose a point that looks off or is in a straight section.

To me, it appears that Garmin is trying to get the trip computer to more closely agree with logged track data, but it still needs work on both device and BaseCamp.

Just came back on the forum to see if anything had changed. I went for a hike yesterday and same old story. Hopefully they will fix the problem this year. I had a long hike on Saturday and the unit indicated I had walked 21.4 km (track and trip) but when re-calculated in Basecamp it turned out to be 18.8 - which is more accurate I believe. Like you, the track looks perfect as does the altitude graph. However, the trip and track now indicate the same distance. I reset both at the start of each walk just to make sure it's not human error!

Just came back on the forum to see if anything had changed. I went for a hike yesterday and same old story. Hopefully they will fix the problem this year. I had a long hike on Saturday and the unit indicated I had walked 21.4 km (track and trip) but when re-calculated in Basecamp it turned out to be 18.8 - which is more accurate I believe. Like you, the track looks perfect as does the altitude graph. However, the trip and track now indicate the same distance. I reset both at the start of each walk just to make sure it's not human error!

Garmin has released new firmware for the eTrex, GPSMAP 64 and I assume others that they said fixed this bug. With the new firmware so far the distance on my eTrex 20 and A forced recalculation in BaseCamp has been within + or - .2 miles. I don't use it as much in the winter so not a lot of testing but so far I'm happy with it.

Any news on the update? Im using etrex 30 and yesterday had a 19km hike. Etrex showed distance of 17km and stopped time of 3:59. The real distance was 19km and stopped time of 2:16. Its really annoying bug since I want to know the moving time and distance at the hike. Garmin express is saying I have my device software up to date.

Are you using version 4.20 software? After loading 4.20 on my eTrex 20 in mid February I had 1 hike that was .5 miles different between the summary data and what was calculated by BaseCamp. It was a hike with a lot of switchbacks, elevation changes and was in the mountains so lots of chances for errors and bad signals. All other tracks have been + or - .2 miles or better. I think this is good. Before loading 4.20 I was seeing large errors.