This object is in archive! 
distance difference between two devices
Answered
hi, my wife and i both have locus map pro and we use it for outdoor excursions. the question is: why, despite the fact that we do the same route, does my mark always hundreds of meters less than my wife's?
Hello.
Please, you can check if both phones have the same GPS filter settings.
https://docs.locusmap.eu/doku.php?id=manual:user_guide:settings:gps
Best regards.
Adela Voldanova
Hello.
Please, you can check if both phones have the same GPS filter settings.
https://docs.locusmap.eu/doku.php?id=manual:user_guide:settings:gps
Best regards.
Adela Voldanova
Also check the settings of the track recording profile. If too few points are set, the curves are always slightly cut.
Also check the settings of the track recording profile. If too few points are set, the curves are always slightly cut.
what are the optimal settings?
I tried to set it up better following the guide but with poor results.
today on the same route she marked 5 km and to me 4 km!
I probably understood little!
what are the optimal settings?
I tried to set it up better following the guide but with poor results.
today on the same route she marked 5 km and to me 4 km!
I probably understood little!
how many are too many points?
my profile:
distance interval: 25 m
time interval: 5 s
point recording condition: distance and time (both)
GPS accuracy required: 100 meters
how many are too many points?
my profile:
distance interval: 25 m
time interval: 5 s
point recording condition: distance and time (both)
GPS accuracy required: 100 meters
It would help if you could upload both tracks, so that we could analyse the source of the fact that both differs that much.
It would help if you could upload both tracks, so that we could analyse the source of the fact that both differs that much.
unfortunately it is a short lap repeated several times because of this virus!
unfortunately it is a short lap repeated several times because of this virus!
Interesting case Giovanni.
I see a different Locus version. Your wife's is on 3.43.1 and you are on 3.44.3.
For this setting point recording condition: distance and time (both)"" I prefer point recording condition: distance and time (ONE) so distance should be true or time.
At the moment your wife's phone is recording a point about every 10 seconds and your's about every 18 seconds. So your track is cutting more off and thus "shorter".
Interesting case Giovanni.
I see a different Locus version. Your wife's is on 3.43.1 and you are on 3.44.3.
For this setting point recording condition: distance and time (both)"" I prefer point recording condition: distance and time (ONE) so distance should be true or time.
At the moment your wife's phone is recording a point about every 10 seconds and your's about every 18 seconds. So your track is cutting more off and thus "shorter".
ok, now I try to set mine as my wife's and update its version then I do another test.
thanks
ok, now I try to set mine as my wife's and update its version then I do another test.
thanks
I'm using a similar profile like freischneider for hiking and cycling: 3m | 3s | 100m (setting: "distance AND time"!)
This will probably adjust the results of both your tracks.
Additionally you can experiment with Settings > GPS & sensors > Advanced settings > Location filter.
First try to use "No filtration". If your tracks look zigzaged too much (on a straight line in reality), try using "Light filter" or later even "Medium filter"
I'm using a similar profile like freischneider for hiking and cycling: 3m | 3s | 100m (setting: "distance AND time"!)
This will probably adjust the results of both your tracks.
Additionally you can experiment with Settings > GPS & sensors > Advanced settings > Location filter.
First try to use "No filtration". If your tracks look zigzaged too much (on a straight line in reality), try using "Light filter" or later even "Medium filter"
ok, now i set it like my wife's:
1m | 5s | 100m (setting: distance and time (both)
position filter: no filter
thank you all
ok, now i set it like my wife's:
1m | 5s | 100m (setting: distance and time (both)
position filter: no filter
thank you all
I'm afraid that 1m is to less and will make the track zigzag (jitter) around your real path a lot especially if position filter=no filter. For example if even you don't move, the track will still sum up, cause the GPS-recevier receives positions that fluctuate by some meters. Resulting in a artificial too long track. To result this effect it would be better to increase the "distance" setting to 3-5 meters. and/or try to use some kind of position filter. You'll have to experiment to find the optimal values to don't get too short and too long tracks ;-)
I'm afraid that 1m is to less and will make the track zigzag (jitter) around your real path a lot especially if position filter=no filter. For example if even you don't move, the track will still sum up, cause the GPS-recevier receives positions that fluctuate by some meters. Resulting in a artificial too long track. To result this effect it would be better to increase the "distance" setting to 3-5 meters. and/or try to use some kind of position filter. You'll have to experiment to find the optimal values to don't get too short and too long tracks ;-)
Interesting subject, but this is not an exact science.
Just like calorie calculation, you can worry about this for a too very long time.
I don't really care about that precision, but I do strive to be as realistic as possible.
I had previously tested once, after some person complained about the distance accuracy of the Locus track records.
Compared to what the design program indicated as a distance, I thought the record result was quite good. Nothing to worry about.
I also found out that different GPS programs measure the distance value of the track slightly differently.
See design and the recorded track together in the gpx file in attachment.
The measurements with a bicycle computer are also not 100% perfect, as even the tire pressure and thus the wheel circumference are also decisive here.
Comparing is of course a best method, but only with exactly the same settings or very similar equipment. So Giovanni, I wonder what the difference will be now.
Important ! Either way with a recorded track you should always be careful, observe and check it, clean it, and correct if necessary.
It is not intended that a 'toilet' stop somewhere further away in the bushes to be kept in that record.
By the way, ladies usually also travel a little more distance for such task, usually go a little further away ;-)
,
Interesting subject, but this is not an exact science.
Just like calorie calculation, you can worry about this for a too very long time.
I don't really care about that precision, but I do strive to be as realistic as possible.
I had previously tested once, after some person complained about the distance accuracy of the Locus track records.
Compared to what the design program indicated as a distance, I thought the record result was quite good. Nothing to worry about.
I also found out that different GPS programs measure the distance value of the track slightly differently.
See design and the recorded track together in the gpx file in attachment.
The measurements with a bicycle computer are also not 100% perfect, as even the tire pressure and thus the wheel circumference are also decisive here.
Comparing is of course a best method, but only with exactly the same settings or very similar equipment. So Giovanni, I wonder what the difference will be now.
Important ! Either way with a recorded track you should always be careful, observe and check it, clean it, and correct if necessary.
It is not intended that a 'toilet' stop somewhere further away in the bushes to be kept in that record.
By the way, ladies usually also travel a little more distance for such task, usually go a little further away ;-)
,
Hello.
Thank you for your knowledge :-)
Please check the recording profile setting - for walking is 25 m in terrain really too much, shorten eg 2 m, I recommend condition (Distance OR time), allowed GPS accuracy.
Try different GPS position filters.
Check location access settings in Google services.
It also depends on the type of device you are using. But even if you have the same device, the same settings, the record will not be exactly the same.
Best regards.
Adela
Hello.
Thank you for your knowledge :-)
Please check the recording profile setting - for walking is 25 m in terrain really too much, shorten eg 2 m, I recommend condition (Distance OR time), allowed GPS accuracy.
Try different GPS position filters.
Check location access settings in Google services.
It also depends on the type of device you are using. But even if you have the same device, the same settings, the record will not be exactly the same.
Best regards.
Adela
obviously I don't pretend that they are identical but the tracks seemed too different!
now I have set the apps in the same way, as soon as I can try them I will let you know.
thanks
obviously I don't pretend that they are identical but the tracks seemed too different!
now I have set the apps in the same way, as soon as I can try them I will let you know.
thanks
ok, today I managed to hike 4 km.
difference between the two devices 20 m
I would say that the problem is solved!
thank you very much everyone
ok, today I managed to hike 4 km.
difference between the two devices 20 m
I would say that the problem is solved!
thank you very much everyone
Great. Thanks for sharing and #StaySafe
Great. Thanks for sharing and #StaySafe
Replies have been locked on this page!