Skip to content
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

total time vs. moving time #2000

Closed
ironspock opened this issue Oct 14, 2024 · 2 comments
Closed

total time vs. moving time #2000

ironspock opened this issue Oct 14, 2024 · 2 comments
Labels
potential bug A bug that could not (yet) be reproduced

Comments

@ironspock
Copy link

moving time looks not correctly calculated compared to total time even consindering pauses and/or "slow moving activities" as geocaching, OSM mapping.
examples:
total time moving time track distance in "lower mountains"
5:06:51 3:32:18 19,44 km
6:38:09 2:43:03 15,53 km
5:00:34 2:14:34 13,64 km

maybe issue is related to my settings
Settings
recording intervall: 10 m
max. distance new segment: 200m
downtime threshold: 10s

Sensors
GPS
Sample Intervall: 0s
GPS accuracy: 50 m
Generisch
Barometer: Internal Sensor

Technical information

  • Device: Gigaset GX6
  • OS: Android 13
  • OpenTracks version: v.14.0 5889 F-Droid
@ironspock ironspock added the potential bug A bug that could not (yet) be reproduced label Oct 14, 2024
@dennisguse
Copy link
Member

The pauses are visualized in OSMDashboard - this might be helpful for understanding the situation.
Slow moving activities (like hiking) should use higher thresholds.
Profiles for different activities+settings would be helpful see #1954.

@ironspock
Copy link
Author

Hi Dennis,

thanks for your feedback. I have to tune my settings... ;-)

Regards ironspock

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
potential bug A bug that could not (yet) be reproduced
Projects
None yet
Development

No branches or pull requests

2 participants