Minimal speed for auto pause in track-recording configurable

Understand.

Anyway what is in description (speed > 0) is mainly informative.

Real testing in Locus is not on simple speed == 0 , but it's exactly as you need speed > 0.5 . 0.5 is in metres/s so it's 1.8 km/h .

I'm aware of these problems of GPS, when you stand still, but GPS still show some speed during own inaccuracy, so this value is already included in Locus.

Is there still need for user-configurable value? Let me know.

Ah, I thought it like this.

So as 1.8 kmh is nearly exactly the value I would use myself (2kmh),

for me personally it is then not neccessary, despite I would appreciate this setting to adjust if min Speed is to low (e.g. track-recording in a car could be easily more).

How long do you check if speed is slow till you set paused and how long do you wait to continue?

And how do you check that the user is not moving with maybe 1km/h forward, which is not a stop but only slow motion?

You miss important fact - there is NO PAUSE in Locus. Only what may happen, is that

1. Locus do not store any point that has speed less then mentioned value and you have enabled "Record only whilst moving"

2. Locus insert 'break points'. This happen when you manually pause track, then track is internally split into two (or more) pieces.

This depend on GPS (better on values that Android system provide to other applications, that request Location data), not on Locus.

Usually on older devices with worst GPS, precision of GPS is a lot worst that change in your movement per one second (refresh rate of common GPS hardware), so it's usually problem. Mainly in worst conditions.

Don' t understand the answer.

Example:

I start Locus-recording with Setting don't track points with no speed.

I walk from point A to point B with speed of 1 km/h.

Point A is 10 km distance from Point B

My GPS Module is very exact and has no "jumps".

Will Locus track any point?

In this case, no.

Speed 1 km/h is 'nonsense' for such GPS hardware. GPS precision is in best case around 5 m (better 10 m), so you have to move at least 5 m / 1 s, to be 'sure', GPS recognize your movement correctly.

If you want to record all points even in such slow motion, just disable "record only whilst moving" settings.

Now I understand. I thought you have maybe code to detect if there is still motion but slow. Not only just the plain speed to detect a stop.

I even wonder how it is possible to detect a stop at all. With these unexact GPS modules, you have most of the time a "speed" over 1.8 km/h if you stay at one point.

So its how you said in previous comment, that it is usually a problem.

Amazingly it worked on my device (SGS2) not too bad.

SGS2 is best devices I ever met and I changed it to Sony after three years (few months ago) of very intensive usage. And I'm still not as happy with Sony as I was with SGS2 :).

Anyway yes, it's a problem. Better should be checking of moment from changed coordinates and not just from "some speed value". Coordinates may be also little bit "averaged". But this all needs some work and a lot of testing and I still had not much taste to do it.

But I may only confirm, that it's something what is missing in Locus (soma auto-pause tool).

EDIT

Btw. such topic is already here http://help.locusmap.eu/responses/sport_track_recording_autopause_if_5km_h_adjustable, but by amount of votes, there is not a big interested I see ...

I'd like to revive this topic:

I made a test with "Record only while moving" activated, walked to work and then put the device on my desk. When I pick it up after a while, I wasn't surprised that it recorded quite some points, as it was indoors which screws up GPS.

Still I wondered: Isn't it possible to use the gyroscope or other sensors to recognize when a device is really motionless and then ignore new GPS positions? Was that ever considered?

What if you travel in a train and the phone lays on the table? Nearly no motions there but big jumps in location.

I guess this could give false positives.

Would need a quite sophisticated way to detect motionless GPS-Jumps, maybe possibel though :)

Thanks for your reply.

There are probably better ways than speed to decide between a true or false trackpoint.

However, I thougt it might be not very difficult to extend the parameter "Record only when moving" to "Record only when moving above n.n km/h". Where n.n can be entered in the range of 0.0 to 9.9 km/h. Maybe with a preset default value of 1.0km/h.

I'm rather sure, if I could set this value to say 0.9 km/h - my problems would disappear almost entirely.

I can not think of any other single parameter to control the decision between true or false.

I'm also thinking of a rather complicated but much more reliable system for the trackpoint registration. Instead of making the decision to store a new trackpoint directly after a new GPS position is received the (potential) points could be stored in an array and based on the comparison of several points (speed and direction) the points would retroactively become confirmed as trackpoint or discarded as noise.

Have you thought in this direction?