jonasoreland / runnerup

A open source run tracker
GNU General Public License v3.0
743 stars 274 forks source link

Inaccurate distance in graph #348

Open jacekn opened 9 years ago

jacekn commented 9 years ago

In history view for my workouts there is a distance mismatch between total distance at the top of the screen and rightmost value on the graph. It is 6617m vs 7.92km so the difference is quite big.

I am pretty sure that it's the graph that is wrong.

On top of that map view shows seven kilometer markers which is wrong (should be just 6).

I am using Nexus5.

The problem can bee seen below: screenshot_20151025-195848

nebmo commented 9 years ago

You are correct, I see the same bug. Don't know when it has been introduced..

renegat commented 8 years ago

This issue seems to be related with Jaggy GPS track? On a 4022m track I have a 5km distance marker in the map and 5,02km in the graph.

SafwatHalaby commented 8 years ago

Note that your average pace is 5:40, however, all points on the graph are below 5:40. This is impossible, isn't it? I am experiencing the same issue. In addition to an excessively long X axis, it seems the Y axis has issues too. I am certain that the total distance and the average pace are accurate. Only the graph representation is not.

It also seems to me that the map view has distance issues. The last distance point on the map shows the wrong distance (in this case, I assume it shows 7.92km).

SafwatHalaby commented 8 years ago

Also, it is possible that the graph is fine, and only the text labels are misplaced.

moobyfr commented 7 years ago

I got the same problem on my moto G4. but I tried the current version from git, in android studio, and the graphs are fine.

gerhardol commented 7 years ago

Incorrect distance in Graph Tagged as bug, but I recall something about corrections here (pauses?)

davidedelvento commented 7 years ago

@jacekn It could also be related with smoothing, can you try disabling smoothing in the settings and see if it changes anything (besides the pace not being smooth anymore, obviously)?

@davidedelvento