This object is in archive! 
Duration and duration in movement
Answered
the duration in motion is not exactexample: real time in motion 4 hours, duration indicated 2 hours
the duration in motion is not exactexample: real time in motion 4 hours, duration indicated 2 hours
Hi Mateo,
do you have screenshot of the situation? GPX of the track for test?
Hi Mateo,
do you have screenshot of the situation? GPX of the track for test?
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.
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.
Locus Map detects speed under 1,8 km/h as non-movement and this limit can't be changed in settngs.
Locus Map detects speed under 1,8 km/h as non-movement and this limit can't be changed in settngs.
Matteo, what are your track recording profile settings? time and distance interval and "AND/OR"parameter, GPS accuracy etc.?
Matteo, what are your track recording profile settings? time and distance interval and "AND/OR"parameter, GPS accuracy etc.?
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.
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.
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?
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?
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
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
Replies have been locked on this page!