This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Data field for showing estimate for total course time

7008695
over 2 years ago

Is there a way to add data field for estimated total course time? Lets say I am following a course that is 100km long. Currently I can see how long I have ridden and how long I am estimated to ride until finish so the field I am looking for would essentially be the sum of these to fields. It would help me to figure out if I should ride faster to finish under some specific time.

In example if the field would show (at 50km mark of 100km course) that estimated total time is 5:15:00, at the current speed I would need to ride somewhat faster if I'd have a target under 5 hours.

There is some alternatives to this already, but not as nice:

  • Edit course in Garmin Connect and set goal time. Then I can use "Time ahead" data field which shows if I'm ahead or behind virtual partner. Downside is that I need to manually set the goal time for the course and "Time ahead" is not as clear as "Estimated total time" would be
  • Start a workout with distance and time goals and after this use the "Workout" screen to see the estimated time. Downside with this one is again manual labour: it can't use the distance from the course and even if it could, I would still need to start a workout with goal time. And a single datafield would be preferred instead of whole screen.
  • 0 over 2 years ago

    You could just use the ETA data field and see if it that value is going up or down.

  • 0 over 2 years ago in reply to Maximilian

    That's one way too, sure. But the problem in this solution is that I have to calculate the goal ETA at the beginning and remember that during the ride. Let's say I start 100 km course at 10:15 and I would like to finish under 5:30:00 so goal ETA would be 15:45. All is good if I can remember that time Slight smile

    But then again, separate data field for this would be much better as it would do everything automatically. And the data needed is already available from other fields.

  • 0 over 2 years ago in reply to 7008695

    If you are following a course you can use "time to destionation"
    Just you would need to define an average speed. The only issue is, if any, it calculates it from your current position with the speed defined. So it doesn't take your real average speed in account.

  • 0 over 2 years ago in reply to hulster

    "Time to destination" is remaining time, right? So it does not include elapsed time.

  • 0 over 2 years ago in reply to hulster

    That's not true (according to my observations). I have seen that number go up and down according to my speed. Also, going up a hill very slowly and going down a hill very fast changes that number (which makes it pretty useless riding a hilly route).


    It uses speed data from your current activity to estimate the “time to destination”.
    I could not find out yet how much data is averaged into that estimate, though.

  • 0 over 2 years ago in reply to 7008695

    Sorry - I obviously did not get the point originally.

    I guess the only option is to keep the elapsed time and estimate to destination side by side in small fields and you need to calculate them.

    The usual way is your variant 1. Either with Virtual Partner or you simple calculate the average speed, which is the more usual way of doing it.

  • 0 over 2 years ago
    I thik, you soul look for ETE 
    What is the difference between ETA and ETE?
    ETE is the estimated time en route, meaning how long your flight will take (what IF says). ETA is the estimated time of arrival, which is what Live Flight says (hence why it says 22:00). The first one (IF) is how long until you reach your destination, and the second one (Live Flight) is when you will arrive.19 feb 2021
    One issue is, thet very probably it is calculated with your last minutes average speed. So try it
  • 0 over 1 year ago in reply to AlfredoCasaretto

    ETE is just time remaining, whereas OP wants total time estimated to complete the whole route (not just the remaining route). 

  • 0 over 1 year ago

    I would like a field that provides this as well. I actually thought that is what ETE would be. ETE should really be named Estimated Time Remaining (ETR) and ETE should ideally be the total time for the whole route.