Currently they're derived automatically but the filtering needs a little work as the next screenshot shows
Activities are selected for inclusion by having (Max Speed > 0) but clearly this isn't sufficient. The easy way doing this is to do (Max Speed > 0) && (Distance > n) where n is some distance that signifies a real session. In my case this rules out wearing of the foot pod to a circuit class.
So, does that sound like a good idea? n would obviously be configurable and I suppose a manual selection of activities is a good idea but one that would probably have to wait a while.
Secondly, the phrase "I do 8 minute miles" is pretty common, but I'm not sure about km's? Currently the application renders speeds and distances based on your local settings (km's for for me). Do people in metric parts of the world refer to this as "I do 6.5 minute km's" or persist with the imperial measurement?
The axis labels need a bit of work too.
1 comment:
"Do people in metric parts of the world refer to this as "I do 6.5 minute km's" or persist with the imperial measurement?"
The first one - min. per km. At least this is very common among orienteerers if they talk about the leg-times between the controls.
Post a Comment