Basecamp track summary details for elevation are inconsistent

Former Member over 9 years ago

Greets, I've found inconsistencies in the 'Summary' information displayed for tracks basecamp version 4.6.2 and wanted to determine if it's user error or a system hiccup. A confirmation of the problem would be appreciated from a fellow basecamp user.

ISSUE
I've noticed the summary data for elevation is wrong on some of my tracks if the last point of the track is selected. Below are 2 images showing the track dialogue with and without the last point selected.

ELEVATION DATA (feet)
with last point selected
Min: 167
Max: 5745

without last point selected:
Min: 906
Max: 1849

Also shown is the CSV file with raw data.

0 SUSSAMB over 9 years ago

I believe it's a bug. It's been reported before and will correct the data if you delete one of the track points. It also affects overall distance.

0 Former Member over 9 years ago

5510

I believe it's a bug.

Thanks. Is there an email or site to report bugs?

0 Dave123M over 9 years ago

Thanks. Is there an email or site to report bugs?

You don't say which GPS you are using or the software version.

Garmin had a bug in most if not all their hand held GPS units that would give bad summary information. If you deleted a point or didn't select one of the points in BaseCamp then BaseCamp would calculate summary information instead of using what was written by the GPS.

This was fixed. It sounds like you have old software with the bug. I would make sure that the software on the GPS is the latest.

0 Former Member over 9 years ago

You don't say which GPS you are using or the software version.

Garmin had a bug in most if not all their hand held GPS units that would give bad summary information. If you deleted a point or didn't select one of the points in BaseCamp then BaseCamp would calculate summary information instead of using what was written by the GPS.

This was fixed. It sounds like you have old software with the bug. I would make sure that the software on the GPS is the latest.

Thanks for the response, sounds exactly like the issue I encountered.
My etrex 20x has software version 2.3 which appears to be the latest.

I exported the track in gpx format and found the min elevation to be 72' which is wrong.
So, it appears I have posted in the wrong form as the problem lies with the etrex 20x software and not basecamp.

<gpxtrkx:TrackStatsExtension xmlns:gpxtrkx="www.garmin.com/.../v1">
<gpxtrkx:Distance>18887</gpxtrkx:Distance>
<gpxtrkx:TotalElapsedTime>22176</gpxtrkx:TotalElapsedTime>
<gpxtrkx:MovingTime>16549</gpxtrkx:MovingTime>
<gpxtrkx:StoppedTime>5617</gpxtrkx:StoppedTime>
<gpxtrkx:MovingSpeed>1</gpxtrkx:MovingSpeed>
<gpxtrkx:MaxSpeed>37</gpxtrkx:MaxSpeed>
<gpxtrkx:MaxElevation>1751</gpxtrkx:MaxElevation>
<gpxtrkx:MinElevation>22</gpxtrkx:MinElevation> = 72feet
<gpxtrkx:Ascent>4255</gpxtrkx:Ascent>
<gpxtrkx:Descent>4470</gpxtrkx:Descent>
<gpxtrkx:AvgAscentRate>0</gpxtrkx:AvgAscentRate>
<gpxtrkx:MaxAscentRate>3</gpxtrkx:MaxAscentRate>
<gpxtrkx:AvgDescentRate>0</gpxtrkx:AvgDescentRate>
<gpxtrkx:MaxDescentRate>-2</gpxtrkx:MaxDescentRate>
</gpxtrkx:TrackStatsExtension>

0 Former Member over 9 years ago

You don't say which GPS you are using or the software version.

Garmin had a bug in most if not all their hand held GPS units that would give bad summary information. If you deleted a point or didn't select one of the points in BaseCamp then BaseCamp would calculate summary information instead of using what was written by the GPS.

This was fixed. It sounds like you have old software with the bug. I would make sure that the software on the GPS is the latest.

Sounds exactly like the issue I've encountered.
My etrex 20x software version is 2.3 (latest)

After some more digging, I found the export gpx file has the incorrect min elevation value, so the problem lies in the etrex unit rather than basecamp.

<gpxtrkx:TrackStatsExtension xmlns:gpxtrkx="www.garmin.com/.../v1">		M	Feet

        <gpxtrkx:Distance>18887</gpxtrkx:Distance>	Distance	18887	11.74

        <gpxtrkx:TotalElapsedTime>22176</gpxtrkx:TotalElapsedTime>	Elapse Time	22176	

        <gpxtrkx:MovingTime>16549</gpxtrkx:MovingTime>	Moving Time	16549	

        <gpxtrkx:StoppedTime>5617</gpxtrkx:StoppedTime>	Stopped Time	5617	

        <gpxtrkx:MovingSpeed>1</gpxtrkx:MovingSpeed>	        Moving Speed	1	

        <gpxtrkx:MaxSpeed>37</gpxtrkx:MaxSpeed>         	Max Speed	37	

        <gpxtrkx:MaxElevation>1751</gpxtrkx:MaxElevation>	Max Elevation	1751	5744.75

        <gpxtrkx:MinElevation>22</gpxtrkx:MinElevation>	      Min Elevation	22	72.18

        <gpxtrkx:Ascent>4255</gpxtrkx:Ascent>	              Ascent	4255	13959.97

        <gpxtrkx:Descent>4470</gpxtrkx:Descent>	              Descent	4470	14665.35

        <gpxtrkx:AvgAscentRate>0</gpxtrkx:AvgAscentRate>	Avg Ascent Rate	0	

        <gpxtrkx:MaxAscentRate>3</gpxtrkx:MaxAscentRate>	Max Ascent Rate	3	

        <gpxtrkx:AvgDescentRate>0</gpxtrkx:AvgDescentRate>	Avg Descent Rate	0	

        <gpxtrkx:MaxDescentRate>-2</gpxtrkx:MaxDescentRate>	Max Descent Rate	2	

      </gpxtrkx:TrackStatsExtension>

0 Dave123M over 9 years ago

I would call Garmin Tech Support at 800 800-1020. This sounds like the same bug that was in other Garmin GPS units. It was fixed in the eTrex 20 and GPSMAP 64s and I think all other hand held units shortly before the 20x came out. I'm thinking it could have been missed in the eTrex 20x/30x series due to timing.

0 Former Member over 9 years ago

Thanks Dave123M, I will give them a call.