Speed / pace filtering

Former Member over 9 years ago

Hi Developers,

I have created a data field and was wondering about the current speed (running app) values, which will be provided by the activity info structure (especially when you are starting an activity).
Which values do you assume as valid values in your data fields and which not? In my data field I am calculating the pace and a average pace for a period of time. Sometimes I am getting very strange values above 100 min/km and a lot more (max was about 1000min/km). I don't take these as serious values, but where the line between valid and not valid should be drawn?

Kind regards

Moritz

Former Member over 9 years ago

It is known issue (thread is somewhere around here) with some watches (like Vivoactive) that they average speed over some time (like one minute), so when you start running for some time speed values are unrealistically low. Firmware fix is promissed.

Tweety955 over 2 years ago in reply to Former Member

Forerunner 955 is doing the same now, device useless for short intervalls ......

FlowState over 2 years ago in reply to Tweety955

Tweety955 said:
Forerunner 955 is doing the same now, device useless for short intervalls ......

If you're seeing crazy-high speed/paces at the beginning of an activity, it could be that your watch didn't get a real GPS lock yet.

Older Garmins used to take a long time to get a lock, but as soon as you got a lock, the pace was immediately stable. What I noticed with newer Garmins (within the past 5 years or so) is that the GPS indicator usually goes green pretty fast, but at that point, my pace/speed may be fluctuating like crazy with super high values (even though I'm standing still), which tells me that I don't really have a GPS lock yet.

What I do is wait for the pace/speed to settle to zero before actually starting the activity. For me this usually takes a few seconds.