Elevation Gain Errors
-
Hi everyone,
I’ve just noticed that plenty of my old moves (2020 and before) have big errors regarding the ascent and descent values.
The graphic below refers to a mountain bike move that shouldn’t be more than 2000m D+, but the value for the ascent registered on the move is 4213m D+.
On this altitude graphic we can see that there are plenty of errors on the values recorded, and this may be the reason why the ascend and descent values are so high.
I’m not 100% sure, but I think that when I did this move the values were normal, otherwise I would have noticed the errors.
This is happening in a lot of moves recorded with my old Suunto Ambit, and with the Suunto Amibt3 Peak I’m using now.
Is it possible that these errors are a consequence of the data migration from the Movescount to the Suunto App? Or is it a Suunto App problem?
Like I said before, there are plenty of moves with this problem, and I never noticed anything when I was using Movescount.
Thanks and regards
-
@jrxara could be, thanks for pointing this out. Maybe @pavel-samokha has any insights?
Watch: Suunto Vertical 2 Titanium Black
Blog: isazi's home
-
@isazi
I recall it was a general issue during the transition, at least the graph, not the total ascent.
but my ambit graphs that have been migrated still look different…
-
@freeheeler
Well, you have an actual histogram
-
@sartoric
I think it displays the integrals of the curve… I just need to derive and everything should be fine again
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login