Admittedly, we’ve started out with a focus on cycling with power.  We attempted to mix in run pace thresholds using the same time duration concept [1, 5, 20, 60] as we do for heart rate and power.   We learned that one minute pace for runners is difficult to pin down when GPS signals waver.  It was quite common for people to have 2-3 min / mile pace inside of 1 minute due to GPS drift.  For now, we’ve just stopped providing 1 minute pace thresholds.  We’ve also learned that while Stryd’s watts are in the Strava power stream, it’s different enough from cycling power to not have them co-mingled as a single power threshold.

The real solution to best support runners is to establish baselines for set distances instead of set time for running pace.  For example, Strava maintains something they call Best Efforts which provides best 1k, 1 mile, 5K, 10K and 13.1 efforts.  Currently I don’t believe these are available via the API which means we’d have to calculate them.  I’ll poke around today to confirm if that’s the case.

Now that we have the smart recording stuff largely worked out I’m guessing it’s a good weekend of work to calculate these on our own (famous last words).

I’m leaning toward the following pace measures:

  1. 400m [flat], 800m [flat], 1600m, 5K, and 10K efforts in time
  2. Average power from Stryd over these best efforts
  3. Average power form Stryd over 3 and 9 minute durations to help support the testing process they advocate
  4. Estimated FTP based on #3 and Stryd’s formula

The basis for only capturing 400 and 800 when the average grade is 0% is to make sure it only records it when you’re not flying downhill.  Typically, these peaks would occur when you’re on the track.

One big question I’m wrestling with is if we should apply the same 8-week window to running fitness as we do with cycling.  I’m assuming so since Strava already gives you a view into your all-time best efforts.

Once we get these metrics in place we can start to see how the variables (e.g. temp, power from Stryd, cadence, altitude) are impacting your pace and power.  I envision a “Running Factors” analysis feature that lets you explore several angles on running.  One disadvantage of Strava is that it doesn’t appear to pull in the myriad of data Stryd and Garmin Connect do on running mechanics.  In the meantime, we’ll get as much as is available and start dialog with Garmin, Stryd and Strava…

Long story short, we’re going to put in place better support for runners in the next 30 days.  Stay tuned and please comment here if you have any ideas or feedback!

Support for Runners
Tagged on: