Question/Request about "Time Of Arrival" involving paused time

Follow

Fernando

• August 30, 2024 20:52
• Edited

Hi Support Team! I want to share an example of one of my latest rides...

In this ride (as many others) I usually stop for a while for resting several times along the route. I want to focus the last stop and the "Time of arrival" field...

20:41. I stopped for the last time in this route. At his moment, according to ride data recorded and uploaded on the HH dashboard, the average speed was about 20 km/h (selecting interval from the beginning to this moment). I can't remember if I left the karoo powered on or turned off this time, sometimes I power off the karoo in order to save battery. Maybe this is important for this question.

21:13. I restarted the ride. I had 35 km left to my home. I would expect that if the average speed until that moment was 20 km/h, a simple calculation show that ideally maintaining the speed, I would have 1h45m more to arrive home, so I would expect the arrival time on 22:58 (21:13+1h45m). BUT, the Time of arrival field showed 0:03 or so (I can't remember exactly, but about 2h50m more).

I think this estimated arrival is soo long 😮. The question: How is it calculated?

Of course, I know that estimated time don't have into account complex variables like slope, etc., this is only a simple calculation, and also it is adjusting the value basing on the current speeds, the more speed you have, the short the estimated time is.

If the current behaviour is as you expect, this is... the request: Can your devs implement (maybe optional) the behaviour that I expected for this restart moment after a pause?

Thanks for your attention.

Regards.

0

• 

  Ali

  • September 02, 2024 12:21

  Hi Fernando, thanks for sharing your experience with us. The ETA is based on hard value of 18km/h and not based on your current average speed. I will be happy to share with the Product team as this is something we have expected to improve over the years.

  1

  Comment actions Permalink
• 

  Jakub Foglar

  • September 02, 2024 20:42

  Wait, what? This a a hardcoded 18 km/h average? I was wondering how this works, too, and why it’s never accurate.

  0

  Comment actions Permalink
• 

  Gerry Stephenson

  • September 02, 2024 21:05

  So the “ETA” is rather useless as it does not reflect “actual ETA” ride data .. what a useless feature .. do better Hammerhead!!

  0

  Comment actions Permalink
• 

  Fernando

  • September 03, 2024 00:00

  Hi Ali, thanks for your answer. So.. fixed 18 km/h... mmm, don't know how, but it doesn't fit with the experience that I shared, in that case I should expect 1h56m for 35 km, shouldn't I? And the Time of arrival shown when I restarted the ride at 21:13 should have been 23:09... about almost 1 hour less than shown in my case 🤔

  I appreciate so much that you share this thing with Product Team, let's hope that they hear us, maybe this is an easy improve in this field and everybody will be thankful.

  Regards.

  0

  Comment actions Permalink

Please sign in to leave a comment.