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
I'm using Overland on iPhone to send location to a locally running instance of Dawarich. I'm noticing a number of incorrect points, where it seems to jump back to a previous location, then back on track again.
Images below indicate this.
Looking at the data recorded in Dawarich for the points, the incorrect ones never had an altitude or velocity value attahced to them (see images below first of a 'correct' point, then an 'incorrect one'. Is it possible for Overland to reject these erroneous points?
The text was updated successfully, but these errors were encountered:
I generally like to avoid dropping data in the app in favor of doing that kind of filtering on the server, but I realize that workflow doesn't work for everyone. It's a reasonable request to add an option to discard these kinds of points. These are usually locations that were obtained not through GPS but through wifi or cell tower positioning, there just isn't an actual indication in the iOS API of this other than noticing some fields are empty.
aaronpk
changed the title
Incorrect points recorded
Add option to discard points with no altitude and/or velocity value
Nov 29, 2024
I'm using Overland on iPhone to send location to a locally running instance of Dawarich. I'm noticing a number of incorrect points, where it seems to jump back to a previous location, then back on track again.
Images below indicate this.
Looking at the data recorded in Dawarich for the points, the incorrect ones never had an altitude or velocity value attahced to them (see images below first of a 'correct' point, then an 'incorrect one'. Is it possible for Overland to reject these erroneous points?
The text was updated successfully, but these errors were encountered: