Intelligent use of the speed accuracy estimate requires a fair bit of research, development and testing. A brief insight into speed accuracy estimates is provided on other pages, but detailed investigations and insights are yet to be documented.
It should be noted that different generations of Apple watch use different GNSS chipsets. This can result in notable differences in behavior, especially in relation to the so called “accuracy estimates”, how they are calculated, and how they may be interpreted.
More often than not, GNSS accuracy estimates (horizontal accuracy, vertical accuracy, speed accuracy, etc) can be regarded as 1-sigma (or RMS) accuracy estimates. For example, given a speed of 10 m/s (20 knots) and speed accuracy of 2 m/s there is supposed to be a 68% chance that the true speed is between 8 m/s and 12 m/s (16 knots and 24 knots).
The reality of the situation is that different GNSS chipsets calculate their accuracy estimates using their own proprietary methods, and the actual values cannot be taken literally. What the accuracy estimates provide is a means to spot inaccuracies, not quantify or measure them exactly.
Different generations of Apple watch use the following GNSS chipsets:
It should be noted that Apple phones since 2016 (iPhone 7) have been using GNSS chipsets from Intel and Qualcomm. They are likely to differ quite considerably from the Broadcom chipsets in the Apple watches.
Interim filtering may be applied when the speed accuracy estimate exceeds 1.5 m/s, simply outputting a speed of zero.
It isn’t possible to say whether the filter is suitable for several models of Apple watch, due to the absence of any data:
Given the uncertainty around models other than the ones from 2019 (Series 5) and 2022 (Series 8), caution should probably be applied. Without any data for 2020, 2021, and 2023 models it is impossible to assess the suitability of this simple filter.
Apple phones use different GNSS chipsets to the watches and the antennas will also be different. If an app such as Waterspeed can provide data from multiple generations of watches and phones, they should be considered individually. Some watches may prove to be reliable enough to be an approved device, some may not. The same is also true of Apple phones, but without suitable test data it is impossible to determine which are good enough, and which are not good enough.
A possible approach to consider is to go live, then evaluate the data quality before approving specific devices?
The <trk>
element of GPX contains a <src>
element for the device type - e.g. “Apple Watch Series 8”.
This is the obvious way to specify which device was used during the session.