Cross-country skiing
-
@pavel-samokha And for the summer we have rollerski and skating rollerski. So in Cross-country skiing makes sense to have it.
-
@pavlas I think we experienced this a bit at some point few years ago, but it was too inaccurate due poles giving the bigger hits, not actually legs. Pole hits were detected fine, but the actual steps were sometimes so ‘soft’ that they did not count in our algorithm, also technique one has is giving great impact, not to state the style of one’s choice. Not sure if the algorithm could be taught to do the trick now, but this is not having too big of priority since there are so many other things ongoing.
-
@jouko-from-suunto Ok, I understand. It makes sense. But I can choose Ski touring mode. It counts the steps. And I think it’s a very similar exercise to cross-country skiing (classic style)
-
@jouko-from-suunto I experience that the step count is more precise on Garmin than on suunto. When doing housework or showering the watch counts… but that’s another thing
-
@jouko-from-suunto I get that. But what about some mainstream approximation? If it detects pole hits (it probably detects only those from the hand on which you wear your watch), then why not multiply them by 2 and get at least something. Now, when I check my daily steps history, I see values like 3k for the days when I cross-country skied 30 km… I mean, 25% error is better than having nothing
-
@inkognito
I bet we’ll find users who want it either to the spot or not at all
-
@jouko-from-suunto said in Cross-country skiing:
since there are so many other things ongoing.
but I’m very curious about this one
-
@freeheeler said in Cross-country skiing:
@jouko-from-suunto said in Cross-country skiing:
since there are so many other things ongoing.
but I’m very curious about this one
Off topic regarding cross-country-skiing, but we will have totally new photo upload management
(at least I understand that) -
@mff73
me too… from another post recently. very nice! -
@stefan-kersting that is true, there is actually more accurate (IMHO) algorithm already developed and published in S3, but since we got a lot user feedback that it gives too little steps (when users got used to get plenty, the more accurate was not appreciated, may be target group issue too) there has not been a decision to push it to other watches. (offtopic, I’ve been moved to other tasks quite a while ago so I’m not too active in this forum, sry)
