Time to Destination issue
As far as I have tried Karoo 2, Time to Destination data field is only calculated based on the Average Speed and distance to the destination. It does NOT include ascents and descents up ahead on the predefined route. It should, because it could make a lot of difference.
-
Hi Mitja, how you upload a route on your device?
Because I import them from Komoot and it looks like the Karoo 2 keep track of the "fitness level" (it's basically a fixed average speed) you selected on Komoot instead of using the average speed.
It's tricky because there are lots of factors that are playing here (wind strength & direction, weight of bike+rider system, fitness level, sustained pace), but I think it could be simplified by using just gradients and the average speed on "flat" (with gradient within -1% and +1%) terrain.
So I'll estimate the speed on gradient on a climb with a formula like this one:- AvgSpeedClimb = AvgSpeedFlat*(1-Gradient*5)
So if my average speed on "flat" is 18 km/h on a 10% gradient (so 0.1) it will be = 18*(1-0.1*5)= 9 km/h
5 here is a factor I just approximate but should be verified, it could be different for different gradient (e.g for from 1% to 3% 2, from 3% to 6%, from 6% to 8% 4, from 9% to 10% 5 and so on).
Similarly, I'll estimate the speed on a descent:- AvgSpeedDescent = AvgSpeedFlat*(1+Gradient*20)
On a 10% descent I'll estimate a 54 km/h of average speed in this example.
It could be also allow for user input to select a "level of fitness" that will affect the multiplier factor I used in both formula.
Personally, I would also recalculate the Time to Destination every 5, 10 or 15 minutes so it doesn't affect much the processor and the battery life as it's not a data needed to be up-to-date as often as power, speed, position and others. -
Hi there Davide, thanks so much for answering. Are you a part of the team who work on this project?
I create routes on Komoot as well, and then simply sync them in Karoo 2 to download them.
I have to say this is an amazing idea that you came up with. We don't need to complicate things too much (since there won't be much of a difference at the end), but to incorporate the basic stuff/data. I agree on each point you stated, formulas, time to refresh the data (each 5min would be good enough), some variables and fitness level of an individual - which could also be gererarated automatically based on previous already driven (cycled actually) routes.
For the beginning it will be good enough, then we can test it, and see if there are still some areas for improvements.
Please sign in to leave a comment.
Comments
3 comments