Ascent, doesn’t work?

6 watchers
fetcheveryone
fetcheveryone
Feb 2022
10:03am, 11 Feb 2022
27,175 posts
  •  
  • 0
fetcheveryone
I've had one feedback, from FDNB - and in that case, I think the watch *WAS* recording elevation data. But FDNB's settings had "Use Watch Elevation" unticked. When this is unticked, Fetch sends a sample of the route to a third party elevation lookup, which returns a set of values approximating an elevation profile.

The hill finder was working with the raw data (which had 2754 data points), and found about 14 significant hills. It was then trying to map these onto the elevation chart, which (because it came from the third party) had only 512 points.

The first hill began at point 73 (of 2754), which seems to match up nicely with the raw data. But it shows on the elevation trace as 73/512 - which is obviously much further along.

I've suggested that FDNB reverts to using watch data for elevation - I think that should ensure that the hills appear in the right place on the elevation graph.

If anyone else wants me to investigate bad data, please send me a feedback with a link to the specific piece of training, and a little note to say what's wrong (unless it's obvious).
Fragile Do Not Bend
Fragile Do Not Bend
Feb 2022
11:12am, 11 Feb 2022
9,246 posts
  •  
  • 0
Fragile Do Not Bend
I’ve had a quick look and it’s looking a lot more sensible now, thanks!
Fragile Do Not Bend
Fragile Do Not Bend
Feb 2022
1:13pm, 11 Feb 2022
9,247 posts
  •  
  • 0
Fragile Do Not Bend
A question Fetch, now that I’ve ticked that box, will all my training have been adjusted now so that my list of hills is correct? Or does it just adjust the activity when I view it?
fetcheveryone
fetcheveryone
Feb 2022
3:56pm, 11 Feb 2022
27,178 posts
  •  
  • 0
fetcheveryone
FDNB - the hill finder will be ignoring the sampled data anyway, if the raw data is present. So any run/ride/walk you now look at should be using the raw data, and the hill finder will not have changed. Probably :-)

Got something to say?

To join the discussion, sign in or join us.

About This Thread

Maintained by Bowman 🇸🇪
It has been a little wonky for sure, but fetch made som changes a while a go and now nothing seems to be right?

Today I went for a trail run with some hills, I got 1m here, Garmin says 354m.
Same last few runs.
I have changed watch though, don’t know if it’s something to do with that.

I know that the ascent on GC is not the truth either, but it’s always consistent though. With my new watch to.

Anyone else having problems?

And, it would be nice to be able to let the ascent use...

Related Threads

  • ascent
  • website








Back To Top

Tag A User

To tag a user, start typing their name here:
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 113,371 Fetchies!
Already a Fetchie? Sign in here