This object is in archive! 

Duration and duration in movement

matteo shared this question 7 years ago
Answered

the duration in motion is not exactexample: real time in motion 4 hours, duration indicated 2 hours

Replies (11)

photo
1

Hi Mateo,


do you have screenshot of the situation? GPX of the track for test?

This comment is in trash! Restore
photo
1

the trkking was done with a few breaks (maximum 30 minutes) the duration in motion should be 9 hours but indicates 5 hours and 12 minutes.

Hi I'm waiting for directions to solve the problem!

Thank you!!

This comment is in trash! Restore
photo
1

Hi Matteo,

seeing the track statistics it is clear you were hiking in a demanding mountainous terrain. You were moving very, very slowly - your average speed was 1.5 km per hour (!). Such a slow speed is often evaluated by your mobile device sensors as non-movement a that's why there is so small value in the "movement" section.

This comment is in trash! Restore
photo
1

Hi thanks for the reply!But the duration is not calculated with the movement of the gps?Is not there a chance to detect such a low speed by changing the settings? Is the problem with the smartphone?

This comment is in trash! Restore
photo
1

Locus Map detects speed under 1,8 km/h as non-movement and this limit can't be changed in settngs.

This comment is in trash! Restore
photo
1

Well, I think the developers of the app should intervene since the problem exists !!
If it is only a problem of setting the solution is simple and could be proposed in the next updates by lowering the speed limit to 0.5Km / h
No??</span>

This comment is in trash! Restore
photo
1

Matteo, what are your track recording profile settings? time and distance interval and "AND/OR"parameter, GPS accuracy etc.?

This comment is in trash! Restore
photo
1

do I have to change setting to some parameter?

This comment is in trash! Restore
photo
1

No, you don't have to change your settings, they're okay. I needed to see them just to be sure. Your requirement of detected speed limit of 0.5 km/h is unrealistic - it's way under sensor capabilities of mobile phones in general. What's more, we must take into account GPS deviations originating from weather and terrain conditions. When there is a better movement detection available, we'll change this parameter. Now it would be meaningless. Thanks for understanding.

This comment is in trash! Restore
photo
1

Uphill I can do 300 meters in one hour (vertical reckoning). Linear that could be anything between 1500 meters and 10000 meters. Matteo's example/screenshot indicates about the same gain/loss per hour. 1,8 km/h is quite critical in serious hiking. I understand that GPS is not more precise. But phones do have other sensors to detect motion. Maybe in the future of Locus?

This comment is in trash! Restore
photo
1

I agree with Henk.. My last hiking had an average speed 1,2-1,5 km/hour ..the pack was heavy and steep terrain .These can be very normal speeds for hiking. The 1,8 km/hour limit is not good for this

Maybe using the fused location ( taking into account acceleration sensor and other sensors) would help in lowering this limit speed. This should be improved

This comment is in trash! Restore
photo
1

You can use Google Services assisted location (Locus settings > GPS&sensors) - it utilizes the fused location provider. But, unfortunately, the system is not fully functional in all devices so , therefore, unreliable.

This comment is in trash! Restore
photo
1

I'm using Google Services assisted location on my Galaxy S8 and it is reliable

Am i to understand that if I use assisted location, then I'm not suffering from this 1,8 km/h limit for detecting movement? This way the limit is much lower?

This comment is in trash! Restore
photo
1

With fused location provider the limit is 0,25m/s which is 0,9 km/h. But we don't generally recommend it because it's unreliable, despite it's Google-backed solution.

This comment is in trash! Restore

Replies have been locked on this page!

You can't vote. Please authorize!
You can't vote. Please authorize!
You can't vote. Please authorize!
You can't vote. Please authorize!