Difference between info.currentSpeed and info.currentPace

What's the difference between info.currentSpeed and info.currentPace (Both is meassured in m/s)?
How exact is the messured value in m/s (decimal places)?
Are info.currentSpeed and info.currentPace smoothed values or the real speed measured at the moment by the watch?
Is it a average of the GPS and GLONASS values masuered?
  • Former Member
    Former Member over 10 years ago
    Including currentPace and currentSpeed was an oversight. The currentPace element will be removed in the future.
  • Hi,

    thx 4 fast reply. What about the other questions:
    How exact is the messured value in m/s (decimal places)?
    Is info.currentSpeed a smoothed value or the real speed measured at the moment by the watch?
    Is it a average of the GPS and GLONASS values masuered?
  • Former Member
    Former Member over 10 years ago
    The value is stored as a float on the device, so it has the "exactness" of the 32bit floating point specification. That is however going to be significantly more precise than the speed derived from any of our speed sources.

    It is the devices best computation of real speed at that moment, which depends on the capabilities of the device, and its current environment. This is based on all the sensor sources available to the device, including, but not limited to GPS, Bike wheel sensors, running speed sensors, and on board accelerometers. More simply, this is the value that is displayed if you configure a data field to display current speed on the device.

    GPS and GLONASS are used together to derive a single solution on devices that have GLONASS support, so there wouldn't be a speed value from each system to average.
  • More simply, this is the value that is displayed if you configure a data field to display current speed on the device.

    In other words, the value that you'd display in your super accurate speed/pace data field would display exactly the same thing as the built-in data field because he smoothing/averaging happens before it gets to any user code.
  • Former Member
    Former Member over 10 years ago
    I'm not sure what you are saying here, but the value displayed by our speed fields is generally unfiltered. We have a heavily filtered current pace implementation, but that is not what is being provided here. The system is aggregating speed sources to provide the best value, and not much else with speed.
  • So sounds like it is more like "bike" speed than "running" speed as the bike one is not, as I understand, filtered anywhere near as much the running one.