This object is in archive! 

TRACK AND SPEED TIME MISCALCULATION

T. shared this problem 12 years ago
Solved

Help please: track/speed time miscalculation


Problem with SPEED and TRACK time


Hello:


The track time (total recording) and speed time (actual moving) are showing up as same values. Accordingly, I cannot get a proper average speed time reading because the stationary recording time is included in the calculation.


I`m running Locus Pro 1.15.3 It was working okay initially, but something`s changed. Can you help?


Thank you.

Replies (10)

photo
0

Hi,


latest version of Locus Pro is 1.16.3...


May you consider updating it and report us, if this problem still exists?


Cheers, berkley

photo
0

Hello again:


I updated to 1.16.3 but unfortunately the problem still exists. Wonder where the bug is? Everything was working fine when I first installed Locus Pro.


I`m attaching a screen shot. Again, the total track time and actual moving time are showing up as same values.


photo
0

question is, if this is issue or not :). May you share exported GPX file of your recorded track?

photo
0

of course it`s an issue :-) When I ride my bike and stop for ten minutes to eat an ice cream cone, the average speed time is lost. Or am I missing something?


I am attaching two gpx files. on suthep.gpx the readings are correct. The file named bosang.gpx both track and speed values are the same (not correct).


But how do you attach files on this forum?? There`s a button to add an image, but where do I upload the gpx files? :-)


.T

photo
0

if you`re on places with wrong GPS signal, your location can still "move". In forest below trees for example, you location can move in radius 100 or more metres. In this case, same values aren`t issue.


Please send me file on locus(@)asamm.com email. I`ll look at it

photo
0

problem located. When I check if last segment was "move" or "stand still" I just took first and second location and checked if speed was above some value. But if you move (point stored), then you stay few hours on one place (no point stored) and then you again start moving (point stored), I took this as "move" segment.


So fixed now, I now compute own speed value for such segment and test this value

photo
0

well..I`m a little embarrassed to say I haven`t clue what this means. What do I need to do at my end to get it working properly? :-)

photo
0

just wait for next version.

photo
0

exactly :) test next release ... will be on "Google Shop" within next few days

photo
0

Great news! I`m looking forward. I subscribe to Androidpit. Can you make the upgrade available there? Thanks. Keep up the brilliant work!


t.

Replies have been locked on this page!