Extend location class with more data for higher-quality positioning advice

[avkonst]

Lack of some of the location data attributes limits development of more advanced location-based apps (including mine).

I would like location class to be extended with the following data available on Android at least and anything what is possible on iOS:

• speedAccuracy - corresponds to https://developer.android.com/reference/android/location/Location#getSpeedAccuracyMetersPerSecond()
• headingAccuracy - corresponds to https://developer.android.com/reference/android/location/Location#getBearingAccuracyDegrees()
• elapsedRealtimeNanos - corresponds to https://developer.android.com/reference/android/location/Location#getElapsedRealtimeNanos()
• elapsedRealtimeUncertaintyNanos - corresponds to https://developer.android.com/reference/android/location/Location#getElapsedRealtimeUncertaintyNanos()
• satelitesCount - corresponds to satelites field from the https://developer.android.com/reference/android/location/Location#getExtras()
• provider - corresponds to https://developer.android.com/reference/android/location/Location#getProvider()
• verticalAccuracy - corresponds to https://developer.android.com/reference/android/location/Location#getVerticalAccuracyMeters()

The motivation for this request is to give applications access to more accuracy data. Since fused location data arrives from GNSS on-chip computation, it has got errors and it is important to know these errors (or degree of accuracy) to advice end-user how much to rely on these computations.

ElapsedNanos is absolutely necessary as the provided time field is in UTC and UTC time drifts due to Android's projection and leap seconds. ElapsedNanos are guaranteed to be monotonically increasing. time field does not guarantee this and time can jump backwards. elapsedRealtimeUncertaintyNanos is necessary to estimate an accuracy of the measured time field and ElapsedNanos.

satelitesCount is another piece of useful information which allows an application to filter out measurements with low count, for example, as these tend to be worse.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.