What are the factors considered for the "time to destination" calculation?

Comments

10 comments

  • Avatar
    Jiri Trousil

    Hello,

    I would also like to know how the time to destination is calculated and whether it can be influenced or set in some way (it is quite inaccurate). When creating a route, would it not be worthwhile to create the possibility of entering, for example, the average speed, according to which the time data would then be recalculated?

    I often ride a bike around the city, I can estimate my average speed on a certain route quite accurately or adapt it to the travel schedule, however, the "time to finish" field really shows very inconsistently and the differences in travel time compared to the plan are over half an hour on a 20km ride. Manually entering the planned average speed before saving the planned route would greatly help to calculate and refine the range in practically minutes. Thank you and best regards Jiri

    0
    Comment actions Permalink
  • Avatar
    Bijit

    Hi Patrick and Jiri,

    Thank you for reaching out to us.

    I would like to inform you that the "time to destination" is calculated based on the the current speed and distance to the destination left.  The average speed of the ride does not take part in the calculations for the "time to destination".

    However, I do agree that the weighted average speed of the ride for the route take would be more accurate in terms of showing the remaining time value. I have share this with our team internally, for consideration.

    1
    Comment actions Permalink
  • Avatar
    Jiri Trousil

    Thanks Bijit for the explanation

    It would be really great if the defined average speed could be set when creating a route or directly on the computer, or if the conversion was set at least according to the current average driving speed. The current setting of the arrival time calculation algorithm is really very inaccurate Thank you for considering the solution and I wish you a nice day. Jiri

    0
    Comment actions Permalink
  • Avatar
    Patrick Winzenried

    Dear Bijit,

    Thank you for the swift feedback which confirms what I was assuming since I noticed the 'time to destination' varies so heavily that it only can be due to some very volatile factor such as 'current speed'. While I never went into much analysis on how ETA could be best calculated, I am quite sure that taking the current speed is probably not the best input factor indeed. Hence very much looking forward on an update from your team as this must be a feature that most riders would appreciate to be more precise I imagine.

    0
    Comment actions Permalink
  • Avatar
    Simon Lockwood

    Hi folks

    Is the above still how ETA is calculated? I see the thread is 2y old, so maybe it has changed?

    I do not find the ETA field changes frequently, so maybe it's more sophisticated now. I find it fairly accurate. At lest enough to be useful as a rough guide.

    Thanks

    Simon

    0
    Comment actions Permalink
  • Avatar
    Loren Heiman

    Wow it uses current speed and distance to end only? No wonder why it's so inaccurate. My last ride I started at 1pm and the ETA ranged from 3pm to 5pm before I finished at 4:15pm. My descending speed is probably 5x my climbing speed. Current speed is an awful way to estimate total time. Needs to take into account the current grade.

    0
    Comment actions Permalink
  • Avatar
    Simon Lockwood

    Years ago route planners would have a predicted time in the background. IIRC correctly Garmin Connect would allow you to enter an average speed for your route, which would then calculate the time to destination when loaded onto a garmin. I think Strava used an average speed of your library of activities to calculate it in the background. Which I remember being annoying as my library had a lot of slow commutes. But this was 10y+ ago and maybe that’s not the case now. I don’t find the time to dest field to change hugely so there must be more to it than current speed and distance remaining.

    Simon

    0
    Comment actions Permalink
  • Avatar
    Simon Lockwood

    I’ve just checked and Strava, Komoot and Ride with GPS all have estimated times with routes in your library. No idea if this is relevant for the Komoot since the HH explanation above was 3y ago.

    0
    Comment actions Permalink
  • Avatar
    Loren Heiman

    Right. And it's funny because my last ride took almost exactly 3 hours 30 mins which was the estimated time according to Komoot.

    0
    Comment actions Permalink
  • Avatar
    Simon Lockwood

    Dear HH friends- can you let us know the current approach? I don’t thinks it’s based on current speed as that would give a very volatile destination time and that’s not my experience. Also when using 3rd party route planning sites does the unit take their time data (not even sure if that’s in the file) or just use its own calculation?
    Thanks
    Simon

    0
    Comment actions Permalink

Please sign in to leave a comment.