This object is in archive!
Track time all/track time movement
Answered
On a small bike tour i stopped two times ~30 sec. for orientation.
In saved Track statistic "time all" and "time movement" are equal.
My track parameters for bike are 10m/5s/and/100m
The two trackpoints at one stop have a gap from 33 sec., so i expect this is recogniced as pause
My question: from what parameter recognice locus a pause?
The same question
Good day balloni,
well this is very good question. I'm aware of this problem for a long time and it's quite funny, that no-one wrote about it sooner.
Locus detect if certain part of recorded track is "moving" or not, simply by detecting distance and time from previous recorded trackpoint.
So in case of your conditions it means, that when
In this case, you moved 10m / 33s = 0.3 m/s. Locus has internal parameter set to 0.25 m/s. So if you next time wait just a few seconds more, it will be enough :).
If you will have any idea on improvement, my ears are always open ;).
Good day balloni,
well this is very good question. I'm aware of this problem for a long time and it's quite funny, that no-one wrote about it sooner.
Locus detect if certain part of recorded track is "moving" or not, simply by detecting distance and time from previous recorded trackpoint.
So in case of your conditions it means, that when
In this case, you moved 10m / 33s = 0.3 m/s. Locus has internal parameter set to 0.25 m/s. So if you next time wait just a few seconds more, it will be enough :).
If you will have any idea on improvement, my ears are always open ;).
Hello menion
thanks for your answer!
on further tests while track recording i noticed, if i stopp moving "time movement" inside track panel stop also immediately and as you explained "time movement" jump up to "time all" by calculation if distance/time=>0.25m/s
so my idea:
if "time movement" value stop more than e.g. 10 sec. don´t calculate speed for next track point.
So each stop > 10 sec. is recogniced independent distance value
Hello menion
thanks for your answer!
on further tests while track recording i noticed, if i stopp moving "time movement" inside track panel stop also immediately and as you explained "time movement" jump up to "time all" by calculation if distance/time=>0.25m/s
so my idea:
if "time movement" value stop more than e.g. 10 sec. don´t calculate speed for next track point.
So each stop > 10 sec. is recogniced independent distance value
Hmm do you think, it will work? What about lost of signal (GPS) below trees, signal lost in beep street in big city, signal lost in tunnel ... you will be more then 10 seconds without a signal, BUT! you will be moving, so next recorded point will be 100 far away ...
Hmm do you think, it will work? What about lost of signal (GPS) below trees, signal lost in beep street in big city, signal lost in tunnel ... you will be more then 10 seconds without a signal, BUT! you will be moving, so next recorded point will be 100 far away ...
< you will be more then 10 seconds without a signal, BUT! you will be moving, so next recorded point will be 100 far away ...>
exactly that is the current functionality, if i lost sat signal a straight line is drawn inside track from last to first satfix point.
< Hmm do you think, it will work? >
yes ;-) if locus ask additionaly "and satfix"
if you think it didn´t work, add a calculated value for info in settings.
If Distance interval is set to 10m display 40 sec
or if Distance interval is set to 20m display 80 sec
< you will be more then 10 seconds without a signal, BUT! you will be moving, so next recorded point will be 100 far away ...>
exactly that is the current functionality, if i lost sat signal a straight line is drawn inside track from last to first satfix point.
< Hmm do you think, it will work? >
yes ;-) if locus ask additionaly "and satfix"
if you think it didn´t work, add a calculated value for info in settings.
If Distance interval is set to 10m display 40 sec
or if Distance interval is set to 20m display 80 sec
Good afternoon balloni,
let's move with it.
Extra description to settings, as you suggest, only display required time needed to recognize stops, right?
Anyway your first suggestion about 10 seconds ... really, just imagine real situation. Fact that you lost GPS for more then 10 seconds is not something un-usual, it may happen. And in such cases (like deep forest or hilly road with tunnels), there will be unwanted pauses and total movement time will be even worst.
Best should be to detect movement thanks to some device sensor, but it will require quite a lot of battery and also value should be stored somewhere, so I do not see it best solution.
Hmm I'll be thinking about it. For now, you at least know how it works ;). Thanks!
Good afternoon balloni,
let's move with it.
Extra description to settings, as you suggest, only display required time needed to recognize stops, right?
Anyway your first suggestion about 10 seconds ... really, just imagine real situation. Fact that you lost GPS for more then 10 seconds is not something un-usual, it may happen. And in such cases (like deep forest or hilly road with tunnels), there will be unwanted pauses and total movement time will be even worst.
Best should be to detect movement thanks to some device sensor, but it will require quite a lot of battery and also value should be stored somewhere, so I do not see it best solution.
Hmm I'll be thinking about it. For now, you at least know how it works ;). Thanks!
Replies have been locked on this page!