Open kmadsen opened 3 years ago
This might help us resolve the issue that we've seen when collecting metrics as well. We can either introduce an interface that filters raw location updates and plug it into the SDK (proper public API or internal one) or implement it as part of a "custom" LocationEngine
where this filtering is the only change.
cc @RingerJK
with metrics we're getting a bit different flow: we might receive null-island locations from NN if a real location hasn't been set to NN. As an option, we might store raw
locations locally and if a session is started but NN spread null-island location we can replace it with the stored(raw
) location.
How does that happen that status is provided without any raw location being set?
A first status update is tied to receiving the first raw location updated :thinking:
How does that happen that status is provided without any raw location being set?
Easy to do: setRoute
-> startTripSession
-> location update will be set in next uncertain iteration and the very first NavigationStatus is come with null-island
location
When setting up simulation environments, and replay environments. The locations will fight with the current GPS.
Add a configuration to enable mock locations
There is a [Location.isMock](https://developer.android.com/reference/android/location/Location#isFromMockProvider()) available. When the configuration is enabled, do not accept locations that are not mocked.
This configuration can also filter for locations provided by mapbox location providers. Such as ReplayRoute.