@cfc I enjoyed using the new routes features immensely the last weeks. Worked flawless for me as long as they don’t contain loops.
Actually they are the reason for a feature request that is now making a lot of sense when using routes as distance metric.
What I would love to have is “Time” as target type. Currently it’s only possible to choose between “speed” and “pace”.
Before we could choose routes for distance it didn’t make a big difference as you could just calculate the pace corresponding to a target time and set pace as target type.
Now as we can select a route it makes a difference as it can update the distance on the fly depending on the route and could give a spot on time vs target metric when aiming for a specific time for a specific route.
What is the use case? Races with a fixed official distance when aiming for a specific finish time.
This would have been super useful for me in my New York Marathon.
I was using “time vs target” as my main metric to orient myself how I’m doing. The metric showed me most of the time in front of my target finishing time when in reality I was behind. The reason was, that I was running much more as the official 42.2k.
Using “time” as target type would not have only made it easier, as I would not have needed to calculate my target pace corresponding to the finishing time, but also given correct ”time vs target” values using the route infos. I’m very confident that this would have worked nearly perfect as the “estimated time” metric was spot on.
What do you think? Would it be possible to include time as target type?
Actually they are the reason for a feature request that is now making a lot of sense when using routes as distance metric.
What I would love to have is “Time” as target type. Currently it’s only possible to choose between “speed” and “pace”.
Before we could choose routes for distance it didn’t make a big difference as you could just calculate the pace corresponding to a target time and set pace as target type.
Now as we can select a route it makes a difference as it can update the distance on the fly depending on the route and could give a spot on time vs target metric when aiming for a specific time for a specific route.
What is the use case? Races with a fixed official distance when aiming for a specific finish time.
This would have been super useful for me in my New York Marathon.
I was using “time vs target” as my main metric to orient myself how I’m doing. The metric showed me most of the time in front of my target finishing time when in reality I was behind. The reason was, that I was running much more as the official 42.2k.
Using “time” as target type would not have only made it easier, as I would not have needed to calculate my target pace corresponding to the finishing time, but also given correct ”time vs target” values using the route infos. I’m very confident that this would have worked nearly perfect as the “estimated time” metric was spot on.
What do you think? Would it be possible to include time as target type?
