From 15eb636920806ec95f62b983c2686def2c360650 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Messias=20Ol=C3=ADmpio?= Date: Tue, 26 Jan 2021 10:43:16 -0300 Subject: [PATCH] Update Docs Updated 'locationTimeout' to 'interval', following the plugin docs --- DISTANCE_FILTER_PROVIDER.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/DISTANCE_FILTER_PROVIDER.md b/DISTANCE_FILTER_PROVIDER.md index ff8acc18b..15a34553e 100644 --- a/DISTANCE_FILTER_PROVIDER.md +++ b/DISTANCE_FILTER_PROVIDER.md @@ -2,7 +2,7 @@ This provider has features allowing you to control the behaviour of background-tracking, striking a balance between accuracy and battery-usage. In stationary-mode, the plugin attempts to decrease its power usage and accuracy by setting up a circular stationary-region of configurable `stationaryRadius`. iOS has a nice system [Significant Changes API](https://developer.apple.com/library/ios/documentation/CoreLocation/Reference/CLLocationManager_Class/CLLocationManager/CLLocationManager.html#//apple_ref/occ/instm/CLLocationManager/startMonitoringSignificantLocationChanges), which allows the os to suspend your app until a cell-tower change is detected (typically 2-3 city-block change) Android uses [LocationManager#addProximityAlert](http://developer.android.com/reference/android/location/LocationManager.html). -When the plugin detects your user has moved beyond his stationary-region, it engages the native platform's geolocation system for aggressive monitoring according to the configured `desiredAccuracy`, `distanceFilter` and `locationTimeout`. The plugin attempts to intelligently scale `distanceFilter` based upon the current reported speed. Each time `distanceFilter` is determined to have changed by 5m/s, it recalculates it by squaring the speed rounded-to-nearest-five and adding `distanceFilter` (I arbitrarily came up with that formula. Better ideas?). +When the plugin detects your user has moved beyond his stationary-region, it engages the native platform's geolocation system for aggressive monitoring according to the configured `desiredAccuracy`, `distanceFilter` and `interval`. The plugin attempts to intelligently scale `distanceFilter` based upon the current reported speed. Each time `distanceFilter` is determined to have changed by 5m/s, it recalculates it by squaring the speed rounded-to-nearest-five and adding `distanceFilter` (I arbitrarily came up with that formula. Better ideas?). `(round(speed, 5))^2 + distanceFilter`