Re: Total ascent figures [Bug 66]
Posted: Thu Jun 13, 2019 9:25 pm
Mine are the same as Pedigree's.
A Premier Garmin GPSr Information Resource
https://gpsrchive.com/Discussion/
The excessive elevation gain recorded is in which file?oldkingog wrote: ↑Thu Jun 13, 2019 7:49 pm I've raised this issue with Garmin support as well and have sent in files from my 66 and my Vivoactive 3 tracking the same flat walk. My watch would give around 11 ft elevation gain on a flat walk around my neighborhood while the 66 would record several hundred feet gain. The support person said that they could not duplicate the results. I'm on my 4th unit (because they keep replacing them for this and other problems) and each unit has had this same issue. I'm baffled why they can't duplicate the results...
So... the gpx file is OK, but the fit file is not, but it matches data displayed on the GPSr? Where on the GPSr?pedigree1 wrote: ↑Wed Jun 12, 2019 10:36 am I record both fit and gpx files and notice that in Garmin Connect these two files give widely different figures; the gpx file being close to expected, the fit being double or greater and matching figures displayed on the unit - with elevation correction disabled in Connect.
The issue is that the data displayed in the trip computer and in recorded activities is too high (by 50 to 100%). I have always assumed that this is related to the fit / gpx files, especially that in recorded activities which matches the fit file data. However, more info to follow...
I think the poster here is referring to the data displayed on the unit either live data in the trip computer or in recorded activities post event.gpsrchive wrote: ↑Fri Jun 14, 2019 5:54 amThe excessive elevation gain recorded is in which file?oldkingog wrote: ↑Thu Jun 13, 2019 7:49 pm I've raised this issue with Garmin support as well and have sent in files from my 66 and my Vivoactive 3 tracking the same flat walk. My watch would give around 11 ft elevation gain on a flat walk around my neighborhood while the 66 would record several hundred feet gain. The support person said that they could not duplicate the results. I'm on my 4th unit (because they keep replacing them for this and other problems) and each unit has had this same issue. I'm baffled why they can't duplicate the results...
Ok, this is complex... In November 2018 there was a difference between the elevation gain displayed in Basecamp and Garmin Connect between the gpx and the fit files. The gpx file would show a gain closest to the expected (given by my route mapping software) and the fit file was way too high. That was with data recorded with GPS software v2.10. Now, with version 3.00 the gpx and fit files in Basecamp show the same elevation but it is too high. In Connect there is still a difference with the gpx being a lower figure closest to expected. Garmin support say that it is inappropriate to look at gpx files in Connect and that since Basecamp is now showing matching data between the two files that issue is solved (their words, not mine). I originally raised the difference between the two file types merely as an indicator / symptom of the exaggerated figures displayed on the unit, however Garmin support lost the thread of this and took the differences to be my only issue and therefore closed the action as solved. They missed the point.gpsrchive wrote: ↑Fri Jun 14, 2019 5:59 amSo... the gpx file is OK, but the fit file is not, but it matches data displayed on the GPSr? Where on the GPSr?pedigree1 wrote: ↑Wed Jun 12, 2019 10:36 am I record both fit and gpx files and notice that in Garmin Connect these two files give widely different figures; the gpx file being close to expected, the fit being double or greater and matching figures displayed on the unit - with elevation correction disabled in Connect.