With help from @likarnik I made some changes to how moving time is calculated for “slow” activities like trail runs and hikes. If the velocity for a point is missing or less 0.05 meters/second the cadence stream is checked. If cadence for the point is > 0 then it is considered to be moving.
To re-compute moving time for existing runs/hikes etc. you need to do Actions → Reprocess File under the activity timeline chart. You can also do this in bulk on the activity list:
HI @david
I know some new Garmin watches have run/walk/Idle time now. My watch is too old and doesn’t get the feature. Would intervals.icu be able to calculate this? It would be very useful for trail runs.
Your Garmin device uses your cadence (steps per minute) and pace during an activity to determine when you are running, walking or idle.
The tricky bit would be know what speed is walking (potentially different for different people) and distinguishing walking from running up a steep hill. Also the velocity data is often very noisy.
yep, understand the complexity and differences.
I often wonder if I am better off walking vs running on steep sections.
From my observation I know I have a slower than ideal run cadence (less than 180 when running), and my walking up the mountain this morning shows red in the garmin graphs, which equates to less than 151. It seems to reflect when I walk vs run quite well. Here is Garmin info on run cadence:
and here you can see the blue sections in the map I am walking up, and the cadence is showing red, when I start to run at the top all the way back is generally green or orange. Orange being a low cadence for running (150-160)
Also on a long flatter run on Saturday I did some run / walking near the end and the cadence seemed to line up for me. (i.e. the cadence was under 150 when I was walking, speed was around 11min/km)
When I ‘speedwalk’ at around 9min/km, my cadence is about 140.
When I do a slow Z1 run at around 9min/km, my cadence is about… 140
The only meaningfull difference is the HR. About 115 when walking fast and 125 when running slow.
I’m a poor runner, but working on it. I hope to be able to run slow at a similar economy compared to walking fast in about 9 months when I will participate in 100Km/24hr event.
Tx. I hadn’t even thought about looking at cadence. Currently Intervals.icu doesn’t extract ground contact time and other running traces from the fit file but I do have that on the todo list.
I actually use cadence as one of the parameters for determining if I should take into account as stopped time. GPS was a bit hit and miss, due to GPS drift, but Trail Runs also involves Uphill Power Walking and that throws cadence out quite a bit too tho.
I coded this to help track my time at Checkpoint stations during Trail Run Races. (I missed out on top 10 on one race for spending too much time at these water stations)
I was wondering if it would be possible to create a custom cadence field in the run settings for users similar to what you do for the HRRc where it would be used to set the minimum run cadence? This way you could use that values to work out the run/walk time for each athlete custom to there run style ?