Hi David,
I have a new Garmin FR 255 and I noticed that the climbing value indicated by intervals.icu after a GPS activity (either run or bike) is much higher than what reported by the watch and also by other platforms even when corrected using various map sources.
For your reference:
activity Intervals.icu reports 190mt climbing. Data come from GC
GC w/o correction and the watch calculate an ascent of 24mt (Garmin Connect)
GC w/ correction says 62mt
SportTracks w/ correction: 0mt
I would say that the right ascent should be between 3 and 20 mt
Does intervals makes some elevation correction based on web map data? can I switch it off?
I unchecked the the elevation correction and reprocessed the activity, but the number didnât change. I also tried to change the setting âunknownâ to âyesâ to state that my watch is accurate, but after saving it remain âunknownâ
I have flagged the Garmin FR 255 as having accurate elevation. I reprocessed your file and now the elevation gain from the fit file (i.e. the watch) has been kept.
I just was looking to ask whenever âClimbingâ is same as âTotal Ascentâ in Garmin - on my Garmin Fenix 7x I see Garming reporting 201m on the run today vs Climbing 363m for Intervals. Yesterday run though is even more concerning - it was pretty flat run by the river and Intervals report 964m while Garmin Connect 46m looks a lot more resonable.
And did you check if the starting altitude was more or less as expected?
I now have a Garmin Edge 830 and this one is quickly adapting after I turn it on. But my former Garmin sometimes needed 15-20 min after a temperature shock to display a ânormalâ elevation. If you start your activity immediately, the barometric sensor slowly adapts to the new environmental temperature and the elevation drifts until it reaches a stable value. That drift causes âabnormalâ climbing numbers.
It is always a good idea to inspect the elevation chart when you see wrong climbing numbers. The drift can easily be spotted.
I donât know if Garmin itself corrects this drift or if it is eventually corrected at the Garmin Connect site. Itâs actually fairly simple to correct for round-trips. Starting and ending height should be the same. If not, a drift occurred. Another way to correct for that is comparing measured height with height available in a topo-map.
Not saying that this is what you are seeing, but the difference is so big that it might have something to do with this.
Hi @david , I stumbled upon this thread while investigating a similar issue.
I changed watch on September 1 (FR935 â FR955), and noticed today that the climbing metric on my latest runs is through the roof! I looked at my settings and my elevation correction is set to auto (on purpose).
See my October 4 run for example.
I see 2 potential issues :
FR955 not being flagged as a reliable device (which it should be). Can you confirm, and confirm when there will be a fix please?
The digital elevation model used for the corrections being flawed. I tried simulating Strava elevation fix and I am getting very similar elevation to my watch barometer, hence pointing to the DEM used by intervals.icu being off. Of course it would not matter in my case when the reliability indicator is fixed, but it could break other peopleâs metrics!
Thanks and let me know if I can help with the resolution in any way.
I set your FR955 to be reliable by clicking âUnknownâ and changing it to yes. I also unticked the âUse elevation correction boxâ. Future runs with that device will not use elevation correction. Climbing is now 49m.
