I kinda like the new location filter in V5 to help reduce noise of dodgy locations - but would be much more useful if there was also an event to know when locations are rejected by the library.
A specific recent scenario for me is on Android when using medium location accuracy (i.e. no GPS) there was over an hour between calls to my "onLocation" handler. From the logs I can see there were 37 rejected locations during that time. For each location the coordinates didn't change and the accuracy simply got bigger - up to 3500m. The library was correctly rejecting these - but without a callback I couldn't detect/adapt to the situation.
A workaround is to set a very big trackingAccuracyThreshold but then you lose the benefit of the filter.
I kinda like the new location filter in V5 to help reduce noise of dodgy locations - but would be much more useful if there was also an event to know when locations are rejected by the library.
A specific recent scenario for me is on Android when using medium location accuracy (i.e. no GPS) there was over an hour between calls to my "onLocation" handler. From the logs I can see there were 37 rejected locations during that time. For each location the coordinates didn't change and the accuracy simply got bigger - up to 3500m. The library was correctly rejecting these - but without a callback I couldn't detect/adapt to the situation.
A workaround is to set a very big
trackingAccuracyThresholdbut then you lose the benefit of the filter.