The following APIs include accuracy information.
A 68% confidence level (i.e. 1-sigma) is explicitly mentioned in the Android documentation but is absent in the Apple documentation.
I suspect that Apple are multiplying the 1-sigma value provided by the GNSS chipset (e.g. Broadcom, Qualcomm or Intel) by a constant value to produce an estimate that is more intuitive to end users; e.g. 2-sigma (95% confidence) or 4-sigma (99.99% confidence).
Accuracy information can be found in the Location class.
Returns the estimated horizontal accuracy radius in meters of this location at the 68th percentile confidence level.
Added in Android 1.0 (Sep 2008)
Returns the estimated altitude accuracy in meters of this location at the 68th percentile confidence level.
Added in Android 8.0 (Aug 2017)
Returns the estimated Mean Sea Level altitude accuracy in meters of this location at the 68th percentile confidence level.
This means that there is 68% chance that the true Mean Sea Level altitude of this location falls within getMslAltitudeMeters() +/- this uncertainty.
Added in Android 14.0 (Q3 2023)
Returns the estimated speed accuracy in meters per second of this location at the 68th percentile confidence level.
Added in Android 8.0 (Aug 2017)
Returns the estimated bearing accuracy in degrees of this location at the 68th percentile confidence level.
Note: The word “bearing” is used instead of “course”. It’s incorrect to use the word bearing.
Added in Android 8.0 (Aug 2017)
Accuracy information can be found in the CLLocation class.
The Apple documentation says that locations with an accuracy >=50 meters should filtered out when creating workout routes:
Because raw Core Location data can contain a significant amount of noise, your app needs to filter out any inaccurate locations before adding them to the route builder. Don’t add any locations whose accuracy is greater than 50 meters.
The radius of uncertainty for the location, measured in meters.
Added in iOS 2.0 (Jul 2008) and watchOS 2.0 (Sep 2015)
The validity of the altitude values, and their estimated uncertainty, measured in meters.
A positive verticalAccuracy value represents an uncertainty that’s approximately 68 percent, or one standard deviation, above and below the altitude values.
Added in iOS 2.0 (Jul 2008) and watchOS 2.0 (Sep 2015)
The accuracy of the speed value, measured in meters per second.
Added in iOS 10.0 (Sep 2016) and watchOS 3.0 (Sep 2016)
The accuracy of the course value (compass heading), measured in degrees.
Added in iOS 13.4 (2020) and watchOS 6.2 (Mar 2020)