Bright shiney new Training Infographic question

5 watchers
Jul 2019
12:30pm, 2 Jul 2019
2,901 posts
  •  
  • 0
jabberknit
Great summary, and thank you, but I have a question about it.

I live and do most of my running in Leicestershire, which is not flat and does have a fair bit of hillage though nothing particularly serious compared to other parts of the country. So I can't quite believe I've run up over 17,000 metres of ascent so far this year which is what my inforgraphic seems to be implying. Other available (probably inferior) websites say it's more around 10,000 - 11,000 metres.

Am I misunderstanding or misreading something, which is perfectly possible as I'm not very maths-minded, or could there be an issue?
Jul 2019
12:32pm, 2 Jul 2019
22,207 posts
  •  
  • 0
fetcheveryone
Try clicking 'Show Data Table', and look for the 'Asc.' row. If there's a month with higher numbers than the rest, we may be able to trace it to a specific entry.
Jul 2019
12:55pm, 2 Jul 2019
2,902 posts
  •  
  • 0
jabberknit
All the monthly totals seem much higher than on strava - I optimistically join their monthly Run Climbing Challenge to try and reach 2,000 metres each month, and usually fail to achieve that. The lowest month on here is 2,082, most of the others are well over 3,000.
Jul 2019
12:58pm, 2 Jul 2019
366 posts
  •  
  • 0
Sam Jelfs
Is your elevation data based on GPS or an altimeter? That other site does a lot of "cleaning up" of data that they aren't sure of. I think height changes of less than 5m on GPS data are ignored, and less than 2m on altimeter data are ignored.
Jul 2019
1:11pm, 2 Jul 2019
2,903 posts
  •  
  • 0
jabberknit
It's whatever's on my Garmin watch, which automatically loads up to Garmin Connect and strava. I don't use anything else to log my runs. 7,000 metres difference over 6 months/1000m miles seems a bit excessive for 'cleaning up' data!
Jul 2019
3:37pm, 2 Jul 2019
2,904 posts
  •  
  • 0
jabberknit
Just done today's run, 7.5 miles.
Ascent:
Garmin Connect: 99 metres
Strava: 103 metres
Fetch: 148 metres
Jul 2019
3:53pm, 2 Jul 2019
7,970 posts
  •  
  • 0
larkim
I thought broadly that strava and FE did the same thing - ditch the data from the watch (unless an altimeter is present) and replace with estimated topographic data based on mapping data? So quite surprise they turn out different values. I don't pay any attention to the elevation data anyway, unless it's a particularly hilly effort, so I wouldn't really notice it on moderate elevation datasets like yours jabberknit. I did a similar distance yesterday with similarly small elevation data and the discrepancies between strava FE and garmin are similar in scale.
Jul 2019
4:06pm, 2 Jul 2019
7,971 posts
  •  
  • 0
larkim
Just checked a more lumpy run:-
GC - 787m
Str - 736m
FE - 867m
Jul 2019
4:17pm, 2 Jul 2019
5,939 posts
  •  
  • 0
Pompey Paul
I wear a Garmin Fenix with a built in altimeter and agree the Garmin elevation data is always lower than the Fetch elevation data.

A recent 18 mile run on the SWCP:

GC - 751m
FE - 1,057m

Fetch - Do you ignore our altimeter data and use the topographic data based on mapping data? Can you give us the option to use the Garmin altimeter data?
Jul 2019
4:19pm, 2 Jul 2019
368 posts
  •  
  • 0
Sam Jelfs
Interesting, just had a look at one myself...
GC - 1064m,
Str - 1152m
FE - 1499m

fetcheveryone.com/t-16346646 - Recorded with a Fenix 3 with altimeter.

About This Thread

Maintained by jabberknit
Great summary, and thank you, but I have a question about it.

I live and do most of my running in...

Related Threads

  • training









Back To Top
X

Free training & racing tools for runners, cyclists, swimmers & walkers.

Fetcheveryone lets you analyse your training, find races, plot routes, chat in our forum, get advice, play games - and more! Nothing is behind a paywall, and it'll stay that way thanks to our awesome community!
Get Started
Click here to join 112,275 Fetchies!
Already a Fetchie? Sign in here