A few years back we experience the issue of iOS devices 'snapping' the GPS track to the nearest road. For our users this is a major deal-breaker as they need a GPS track on the exact place where they were driving.
We then had this issue; #1027 (comment) that seemed to be solved by choosing for otherNavigation, which referes to the CLActivityType otherNavigation ( The value that indicates positioning for activities that don’t or may not adhere to roads such as cycling, scooters, trains, boats and off-road vehicles. )
So far so good. However with the introduction of plugin version v5 and above, we now have snapping roads again on iOS, whilst we still have otherNavigation as our activityType and high as desiredAccuracy...
Were there any changes in the plugin for which we might need to alter our configuration in a way to avoid snapping to road on iOS?
See below two tracks of a Android (below; actual track hitting the waypoint) and iOS (above; snapped track hence missing the waypoint). These two devices were in the exact same car at the same time. So the expected behaviour would be two near-similar tracks...
Also when we look into the 'accuracy' value of the track; we can see for iOS it actually 'sees' the inaccurcy to the actual road itselfs; so it's aware of the snapping behaviour or something...
A few years back we experience the issue of iOS devices 'snapping' the GPS track to the nearest road. For our users this is a major deal-breaker as they need a GPS track on the exact place where they were driving.
We then had this issue; #1027 (comment) that seemed to be solved by choosing for otherNavigation, which referes to the CLActivityType otherNavigation ( The value that indicates positioning for activities that don’t or may not adhere to roads such as cycling, scooters, trains, boats and off-road vehicles. )
So far so good. However with the introduction of plugin version v5 and above, we now have snapping roads again on iOS, whilst we still have otherNavigation as our activityType and high as desiredAccuracy...
Were there any changes in the plugin for which we might need to alter our configuration in a way to avoid snapping to road on iOS?
See below two tracks of a Android (below; actual track hitting the waypoint) and iOS (above; snapped track hence missing the waypoint). These two devices were in the exact same car at the same time. So the expected behaviour would be two near-similar tracks...
Also when we look into the 'accuracy' value of the track; we can see for iOS it actually 'sees' the inaccurcy to the actual road itselfs; so it's aware of the snapping behaviour or something...
