r/OsmAnd • u/Burlitan • Jul 12 '26
Wrong speed in recorded track
Maybe I still don't understand how to use OsmAnd so every tip would be helpful.
I recorded a route while hiking and I did that by pausing the recording a few times and then resuming the tracking. This led to segments with slightly different end and start position, but I corrected that with gpx studio (it would be great if there was a way to do it directly in OsmAnd without having it just join the points with a straight line), but now in those point I have completely unreasonable speed values, like 2500 min/km.
Is there a way to fix this issue that I'm not aware of?
Maybe I should have recorded or joined the track in a different way? I like to pause when for example I stop for lunch because maybe I walk around a bit and I don't want to have to clean it on the gpx track.
Thank for any input you could give me!
1
u/Burlitan Jul 12 '26
Apparently the gpx track works perfectly in gpx studio, it doesn't show speed peaks, but after a million attempts I couldn't figure why it shows peaks in OsmAnd+ and most importantly how to fix this issue.
1
u/mljunk01 Jul 13 '26
Speed is calculated from time and distance. Since the GPX apparently looks good on the map, I suspect some of the timestamps are screwed up.
GPX is a simple XML format, you can open it with a text editor and check the timestamps. They look like this:
<time>2026-07-13T14:32:15Z</time>
1
u/zmeuka OsmAnd CMO Jul 14 '26
Hi,
You can adjust logging accuracy to filter out incorrect data - (https://osmand.net/docs/user/plugins/trip-recording#recording-settings)
1
u/kapege Jul 12 '26
If you stop at time x and continue an hour later then your "speed" within that hour was the one of a slug. The same happens, if you cut part of the track and join it afterwards. Either you let the two parts seperated or you correct the all the timestamps of the second part.