-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[run v0.17] Distance is wrong #3116
Comments
I like the sound of your proposed fixes, specifically:
Does that all sound good to you? If so, we have a plan |
a) Yes, that should do the trick. Waiting for altitude to stop changing may be easiest (we have barometer, so we can tell the altitude is not changing). |
Great, sounds like a plan. About c) (in fact, this applies to all points, but specifically about where the change should be made), I don't believe So I believe the fix would be to change exstat's distance calculation, which would then be picked up by For exporting runs, we'd need to apply similar logic to the |
gipy's latest update has some logic around this too |
Affected hardware version
Bangle 2
Your firmware version
2v19
The bug
Distance in kilometers is pretty much wrong.
a) On startup, very frequently large distance is added when acquiring GPS fix. It may be distance to previous GPS fix or something like that.
b) When stationary, random position noise from GPS means that distance is growing quite rapidly. [Possible solution might be to test distance from last point; if it is less then 10m, ignore GPS measurement. if it is more, save current position as last point and add the distance].
c) When user returns to the clock, track recording seems to continue but distance is not accounted properly. Straight-line distance is taken from last point when Run was running, or something like that. [Possible solution might be for "Recorder" to do the distance calculation, and make "Run" ask "Recorder" for distance.]
Installed apps
No response
The text was updated successfully, but these errors were encountered: