You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My use case is that I use ActivityTracker to record some path, and PureMaps to collect "bookmarks", noting in this way points of interests or other details to be uploaded to OpenStreetMap later.
But issue is that when I switch from PureMaps back to ActivityTracker, I get "jitters" recorded on the map, like this (screenshot from JOSM editor):
Maybe it' location service issue, as during switch I see that location indicator flashes off/on, so maybe precision is actaully lost, IDK.
Though maybe it would be possible to workaround this issue with (primitive?) heuristics? If application is switched-back, app should get GPS position change event "significantly" (whatever that is) later than expected 5s (if 5000ms is the interval set in app settings) since the last event (before switching applications). Detected as such, this position change event could be ignored, maybe even together with subsequent (and too frequent) ones, as it seems there are "burst" of GPS updates after switching back).
EDIT: this is detected on BQ Aquaris E5.
The text was updated successfully, but these errors were encountered:
Originally reported by @Talkless under ernesst#33.
My use case is that I use ActivityTracker to record some path, and PureMaps to collect "bookmarks", noting in this way points of interests or other details to be uploaded to OpenStreetMap later.
But issue is that when I switch from PureMaps back to ActivityTracker, I get "jitters" recorded on the map, like this (screenshot from JOSM editor):
Maybe it' location service issue, as during switch I see that location indicator flashes off/on, so maybe precision is actaully lost, IDK.
Though maybe it would be possible to workaround this issue with (primitive?) heuristics? If application is switched-back, app should get GPS position change event "significantly" (whatever that is) later than expected 5s (if 5000ms is the interval set in app settings) since the last event (before switching applications). Detected as such, this position change event could be ignored, maybe even together with subsequent (and too frequent) ones, as it seems there are "burst" of GPS updates after switching back).
EDIT: this is detected on BQ Aquaris E5.
The text was updated successfully, but these errors were encountered: