Settings to have maximum intensity

Trying to figure out settings to get maximum intensity of the recorded points. The resulting path is very coarse and points frequency is way too low for the configuration parameters passed.

Your Environment

• Plugin version: 2.2.4
• Platform: iOS and Android
• OS version: iOS 9.3, Android 4.2.2
• Device manufacturer and model: iPhone 5s 64G, THL 5000
• Cordova version (cordova -v): 6.3.1
• Cordova platform version (cordova platform ls): android 5.2.2, ios 4.2.1
• Plugin configuration options: var bgOptions = { stationaryRadius: 1, distanceFilter: 1, desiredAccuracy: 0, debug: true, notificationTitle: ‘Background tracking’, notificationText: ‘enabled’, notificationIconColor: ‘#FEDD1E’, notificationIconLarge: ‘mappointer_large’, notificationIconSmall: ‘mappointer_small’, locationProvider: 0,// 0 or 1 interval: 10, fastestInterval: 5, activitiesInterval: 10, stopOnTerminate: false, startOnBoot: false, startForeground: true, stopOnStillActivity: true, activityType: ‘Fitness’, pauseLocationUpdates: false, saveBatteryOnBackground: false, maxLocations: 100 }
• Link to your project: http://www.globalspeedindex.com/

Context

For Android and ANDROID_DISTANCE_FILTER_PROVIDER selected with stationary radius and distance filter set to 1, expect to get more than 400 points during 8.8 miles ride accomplished in about 1.5 hours. route.zip

Expected Behavior

Ideally get points for each 1 meter (I understand that this is not realistic), but at least more often than 50 points per mile.

Actual Behavior

Got about 400 points per 8.8 miles.

Possible Fix

Steps to Reproduce

1. Set parameters as above.
2. Start tracking.
3. Use some tool to look at the track: http://labs.easyblog.it/maps/gpx-simplify-optimizer/

Context

Very low accuracy of the measurements. The idea of the application is to have maximum information about the track to be able to analyze every detail about the ride.

Debug logs

[anatoly-khomenko]

Posted pull request here. @mauron85, please, consider merging. Thank you!

[anatoly-khomenko]

Figured out for iOS as well. The distanceFilter calculation algorithm here: is not suitable for our purpose. We had to comment out the whole calculation and return _config.distanceFilter instead. Along with using Fitness activity type and stationaryRadius=5 we got the satisfactory frequency of GPS points along the way. Compare before: and after: