Stadtradeln Augsburg Tag 11 - BW 06
Mountain Biking Highlight
Mountain Biking Highlight (Segment)
Anton Rieger went mountain biking.
July 13, 2021
Thanks for the tip with Garmin. I now know why your analysis part is misinterpreted 🤣
I'm curious about that, AntonTwo bikers have recognized how to use the "parking device for MTBs" correctly at a mountain hut 😊
I'll tell you the result of this tour. This time with a different analysis tool (LocusMap pro):Track time 3:32:49Movement 2:22:37Total speed Ø 13.4 km / hSpeed travel Ø 19.9 km / hUphill 1,118 m 18.04 kmDownhill 1,119 m 17.71 kmRoute length 47.53 kmWith these key data everyone can imagine that the Ø speed displayed by komoot cannot be correct ...Now it's your turn Anton
The Komoot app shows the total distance and the time in motion correctly with a small deviation, and "calculates" the average speed from it. At the "current" speed, the app had a deviation of - 2 to - 12.6 kilometers, and because your analysis tool uses this speed 🤭
komoot shows me (when displaying in the browser):Tour duration 3:33 hours, Ø 13.4 km / hMovement time 1:58 hours, Ø 24.2 km / hThe difference in the movement time can be explained by the fact that a "standstill"> 5 seconds is not taken into account in the analysis, speeds of> 0 are also counted as movement time
I suggest we leave it that way and stop discussing it.The high average speed is a good motivation factor for you ... keep it up 👍
then the riddle is solved after all 😂
btw: Even if the analysis is closer to the "truth", an average of 19.9 km / h is a fantastic value for a mountain tour with> 1,100 hm🏆
The average speed is also shown by my Garmin like this.
Since the speed display of the Komoot app is wrong, your analysis tool cannot generate a correct value either.
Anton, the so-called header data (calculation of the Ø values) are NOT evaluated in a subsequent analysis, rather only the individual track points are read in and the Ø values are re-determined. Your original recording of your Garmin would be interesting ... but no, I don't want to deal with it from now on. You are the best and you stay that way for me tooB A S T A ... no offense
Since your extremely "ingenious" analysis app is apparently unable to differentiate between the stand and travel times so precisely, a "correct" result will probably never be possible. No offense