Started by poutnikl, June 15, 2016, 08:33:25
0 Members and 1 Guest are viewing this topic.
TC = ( remaining_distance / avgspeed ) / 5
TC = min( 1000, max(100, remaining_distance / avgspeed )) / 5
avgspeed(N) = alfa * avgspeed(n-1) + ( 1- alfa) * immediatespeed
avgspeed(N) = ((TC - 1) * avgspeed(n-1) + immediatespeed ) / TC
Quote from: Ulrich Kiermayr on October 15, 2016, 20:29:07A remark on that: during our vacation (cycling) the ETA often was not really usable. Reason: the topography of the route has a huge influence on the speed you are able to ride. Consider a tour where you go uphill the first half and downhill on the second. Just considering the current average speed, would result in unusable results,because it would estimate going up the whole tour. But this is wrong, since the second half will be faster because it is downhill.I think the ETA algorithm (for cycling and probably also for hiking) should work somewhat like the algorithm to estimate the time for a track. The current avg speed could\should be used to set the parameters for that estimate (like piking the best profile in the trip time estimate).
Quote from: poutnikl on October 16, 2016, 20:26:13Sure, I am well aware of that. But it is possible only if elevation profile is available.As I have mentioned before on one of Locus forums,ideal would be if BRouter ( or Locus during the import ) would calculate the route nominal time profile estimation based on elevation profile. Then ratio of nominal and real speed for a particular route section would be used for the correcttion of the nominal remaining time.E.g. if you passed some distance in 9 minutes instead of nominal 10 minutes, based on nominal time profile, than if nominal remaining time was 60 minutes, the corrected prediction would be 54 minutes.