Infographic no ascent?
5 watchers
Jun 2021
9:51am, 30 Jun 2021
53 posts
|
Bowman
So today my watch (and garmin connect) says 96m This site says 70m. I guess it has to do with not use watch for elevation box? Its fairly accurat though since i have calibrated it and checked over many many runs onm this particular route. |
Jun 2021
12:11pm, 30 Jun 2021
26,269 posts
|
fetcheveryone
I blogged about determining ascent back a few months ago: fetcheveryone.com/blog/3/2021/3#blog421624 (TL;DR = summing the deltas of the raw data from Garmin gives over-exaggerated figures, so our algorithm represents a best attempt at matching the figures that Garmin deduce from that same data) |
|
Jun 2021
5:23pm, 30 Jun 2021
60 posts
|
Bowman
Ok, then I know thanks. I’ll read the blog as well. Still the info graphics is wrong though. But today 600m something. But I have thousands of meters. But I’ll read the blog maybe it’s there as well. |
Jun 2021
6:12pm, 30 Jun 2021
4,546 posts
|
K5 Gus
I'm still very confused by all this. Long hilly run yesterday - Garmin says 1157m, fech (with use watch data unticked ) said 1130m - pretty good ! Saw that you've now said that for watches with "enhanced elevation" which my Fenix6 has, then it should now work from the watch for those, so I ticked the setting for use watch elevation, and edited yesterdy's run, and it went down to 693m. But in the training log list ( and on Terrain option ) it still shows as 1130m - is that because it's cached somewhere and will change to 693, or are there two separate calculations for list view and individual entry view ? With a Fenix6 should I now be able to use the watch data and get the same correct value in all places ( individual entry view, list view, infographics, etc ) ? |
|
Jun 2021
6:12pm, 30 Jun 2021
4,547 posts
|
K5 Gus
*fetch not fech 
|
|
Jul 2021
4:25pm, 16 Jul 2021
113 posts
|
Bowman
I still miss a reasonable ascent on the yearly info graphics. I still have ~600m But I have thousands of meters gathered. No way of fixing this fetch? |
|
Aug 2021
2:06pm, 9 Aug 2021
148 posts
|
Bowman
I still miss a reasonable ascent on the yearly info graphics. I still have ~600m But I have thousands of meters gathered. It doesn't have to be perfect, but at least the data that is stored here? No way of fixing this fetch? |
|
Oct 2021
5:51pm, 1 Oct 2021
296 posts
|
Bowman
Still miss it, also sent in a request about this. That has to be a simple fix? Fetch, you do much by your self, I know that. But this thing I really would like to have when I frame the infographic for 2021
|
|
Jan 2022
3:48pm, 30 Jan 2022
901 posts
|
Bowman 🇸🇪
I really appreciate all you do Ian, and this seems to be a hard one. This is not only about the infographic, but ascent calculation over all. Still the ascent is way off. Garmin gave me 375m for the run. Fetch logs 56m It’s just to big of a difference. You never answered if you can’t just let Garmin user tick a box and use Garmins calculation from the fit-file? Garmin might not be spot on either, but at least it will be consistent? |
Related Threads
-
Ascent, doesn’t work?
Feb 2022
-
Hillscore...what is it?
Aug 2023
-
Most ascent in half an hour. Best way?
Jun 2022
-
Climb *some* miles in 2017
Apr 2017
-
distance, gradient and a little trigonometry
Apr 2016
-
Ascent
Sep 2014
-
Ascent in training log
Aug 2014
-
Fetch meetups
Apr 2024
-
New Features
Apr 2024
-
What is your fetch addiction position?
Apr 2024
