This object is in archive!
Track poor - why?
Answered
When I record a track, although the GPS follows my walk accurately, the track has gaps and only roughly corresponds to my actual route with long straight lines between points that are sometimes several hundred metes apart.
I am a new user, so have probably misunderstood something! Settings are generally at defaults.
If I could work out how, I could upload the GPX file.
The same question
Here is the GPX file in a ZIP.
Comparison with the UK OS map will make it pretty obvious where we walked and that the tack is a poor match.
Here is the GPX file in a ZIP.
Comparison with the UK OS map will make it pretty obvious where we walked and that the tack is a poor match.
For a Test(!) plz...
uncheck your GPS settings
"Disable when hiden" and "GPS auto-off"
Activate in "Track recording" "Parameters" "Recording profiles" the "Cycle profile"
and uncheck "Record only whilst moving"
...and try it again.
Write us your experience...
For a Test(!) plz...
uncheck your GPS settings
"Disable when hiden" and "GPS auto-off"
Activate in "Track recording" "Parameters" "Recording profiles" the "Cycle profile"
and uncheck "Record only whilst moving"
...and try it again.
Write us your experience...
Thanks
I actually tried some of ths before seeing your comments.
I had ''
Thanks
I actually tried some of ths before seeing your comments.
I had ''
I had 'disable when hidden' unchecked, but 'record only whilst moving' was checked.
I don't know where to ginf yhose track recording parameters - unless they ore PRO profiles.
Anyhow, I thought I was still having problems with the GPS switching off when the tablet is sleeping
and so leaving gaps in the track until I choose to look at the map, so part wayround my walk I actually unchecked 'GPS auto-off'.
I had also set Locus-as-a-service until later in my walk.
Now I have re-loaded the track and, despite previously looking patcy before I unchecked auto-off the whole track now looks good.
Sadly this is inconclusive.
Also, unchecking auto-off is likely to drainthe battery quickly.
I will be gratefull for other ideas and will have to try changing just one thing par walk!
Thanks.
I had 'disable when hidden' unchecked, but 'record only whilst moving' was checked.
I don't know where to ginf yhose track recording parameters - unless they ore PRO profiles.
Anyhow, I thought I was still having problems with the GPS switching off when the tablet is sleeping
and so leaving gaps in the track until I choose to look at the map, so part wayround my walk I actually unchecked 'GPS auto-off'.
I had also set Locus-as-a-service until later in my walk.
Now I have re-loaded the track and, despite previously looking patcy before I unchecked auto-off the whole track now looks good.
Sadly this is inconclusive.
Also, unchecking auto-off is likely to drainthe battery quickly.
I will be gratefull for other ideas and will have to try changing just one thing par walk!
Thanks.
this was not the solution.
this should be a test whether the GPS is working correctly
this was not the solution.
this should be a test whether the GPS is working correctly
And btw,
if "unchecking auto-off is likely to drainthe battery quickly",
you never should go in the wild with this poor mobile toy :)
The "saving energy effect" is really small..
And btw,
if "unchecking auto-off is likely to drainthe battery quickly",
you never should go in the wild with this poor mobile toy :)
The "saving energy effect" is really small..
OK - I just imagined the battery life would be reduced significantly - I may simply be wrong.
I have now done 2 tests on local walks - in both cases I seem to have a reasonable tracks. In both cases I left the tablet alone for the whole walk - just saved the track at the end.
Is there any potential explanation for the discontinuous tracks I had previously experienced?
If the GPS failed to get a good location I assumed I would simply get a 'straight line' between 2 points where it worked - and assume that is the reason for problems when amongst trees.
Recently, I realised that I was probably moving too fast for a 60sec track update, so I reduced that to 45secs and 20m point separation - which is not achieved, because I move further than that in 45sec.! I think the 45sec is dominating the point density.
Today's track has several points that are about 100metres off my route (I was on paths I know very well).
I have the GPS set to achieve 10m accuracy before switching off (and 60 sec to achieve this).
Under these settings, would you expect to see points recorded that are 100m off-route?
I'm grateful for your comments and help getting a 'newbie' to the position where he can work out what is happening. Thanks.
OK - I just imagined the battery life would be reduced significantly - I may simply be wrong.
I have now done 2 tests on local walks - in both cases I seem to have a reasonable tracks. In both cases I left the tablet alone for the whole walk - just saved the track at the end.
Is there any potential explanation for the discontinuous tracks I had previously experienced?
If the GPS failed to get a good location I assumed I would simply get a 'straight line' between 2 points where it worked - and assume that is the reason for problems when amongst trees.
Recently, I realised that I was probably moving too fast for a 60sec track update, so I reduced that to 45secs and 20m point separation - which is not achieved, because I move further than that in 45sec.! I think the 45sec is dominating the point density.
Today's track has several points that are about 100metres off my route (I was on paths I know very well).
I have the GPS set to achieve 10m accuracy before switching off (and 60 sec to achieve this).
Under these settings, would you expect to see points recorded that are 100m off-route?
I'm grateful for your comments and help getting a 'newbie' to the position where he can work out what is happening. Thanks.
You set "...60sec track update" ???
You set "..10m accuracy before switching off" ???
"..reduced that to 45secs and 20m" ???
why?
Plesae read my comment here again:
http://help.locusmap.eu/responses/track-poor-why#comment-9926
...and set nothing else.
And after that(!) test we will see...
btw.
What hardware are you using?
You set "...60sec track update" ???
You set "..10m accuracy before switching off" ???
"..reduced that to 45secs and 20m" ???
why?
Plesae read my comment here again:
http://help.locusmap.eu/responses/track-poor-why#comment-9926
...and set nothing else.
And after that(!) test we will see...
btw.
What hardware are you using?
The answer to your 'why' was explained in my last post - I can't expect an accurate track if I'm moving >100m between GPS updates. I have only slightly modified the default settings!
That said, I have now UNCHECKED 'GPS auto-off' and 'Record only whilst moving'.
'Disabled when hidden' has never been checked. I will run a test in the next day or so.
As I said before: "I don't know where to find those track recording parameters - unless they are PRO profiles" So unless you enlighten me I simply can't follow that advice.
At present I have the free version - pending understanding the whole thing and getting a reasonably successful result.
Do I assume the 'cycle profile' is merely a short-cut to setting parameters that I could set manually? (I guess to get a higher recording rate commensurate with a higher travel speed - yes?)
I have tried to explain my thinking, even if it may be wrong and brings unexplained derision. I will find it much easier to advance if you give me a little explanation of your suggested changes. Thanks.
I strongly suspect that I'm simply fighting default settings that were not designed to give the track precision that I had expected. (eg GPS auto-off and a recommendation for an interval >60 sec to conserve the battery. I didn't choose those, and that is where my apparently daft comment about battery life originated). Surely starting with the 'defaults' is reasonable.
My hardware is merely a budget Prestigio tablet, albeit their best 4-core version. I'm not expecting to use it as a survival aid on an arctic expedition!
The answer to your 'why' was explained in my last post - I can't expect an accurate track if I'm moving >100m between GPS updates. I have only slightly modified the default settings!
That said, I have now UNCHECKED 'GPS auto-off' and 'Record only whilst moving'.
'Disabled when hidden' has never been checked. I will run a test in the next day or so.
As I said before: "I don't know where to find those track recording parameters - unless they are PRO profiles" So unless you enlighten me I simply can't follow that advice.
At present I have the free version - pending understanding the whole thing and getting a reasonably successful result.
Do I assume the 'cycle profile' is merely a short-cut to setting parameters that I could set manually? (I guess to get a higher recording rate commensurate with a higher travel speed - yes?)
I have tried to explain my thinking, even if it may be wrong and brings unexplained derision. I will find it much easier to advance if you give me a little explanation of your suggested changes. Thanks.
I strongly suspect that I'm simply fighting default settings that were not designed to give the track precision that I had expected. (eg GPS auto-off and a recommendation for an interval >60 sec to conserve the battery. I didn't choose those, and that is where my apparently daft comment about battery life originated). Surely starting with the 'defaults' is reasonable.
My hardware is merely a budget Prestigio tablet, albeit their best 4-core version. I'm not expecting to use it as a survival aid on an arctic expedition!
wow, u are an Locus FREE user ??
nice. sorry my fault.
very rare these species :)
Anyway - set and try:
set
wow, u are an Locus FREE user ??
nice. sorry my fault.
very rare these species :)
Anyway - set and try:
set
OK Thanks. Have done and will test and let you know.
I think the 8 sec interval will over-ride the 3m as I certainly walk more than 22m a minute!
OK Thanks. Have done and will test and let you know.
I think the 8 sec interval will over-ride the 3m as I certainly walk more than 22m a minute!
Hello guys,
quite a lot was wrote and I'm not sure what to wrote first, so just few my suggestions.
1. Accuracy information that you see in Locus do not mean, that point is really that precise, but it's just computed value from received data. So it's possible (mainly on cheeper devices with support for only USA GPS), that Locus show you location 50-100m of your real location, but still show accuracy 10 m. There is anyway nothing, app developers can do with it.
2. GPS Auto-off may reduce battery usage a lot! Amount depend on time intervals. If you set less then 30 sec, then this feature do not have a big sense. For areas with clear sky (where GPS receive location fast) are values more then minute very usable. But if you walk only in deep forest, where your device has a problems with getting precise location (FIX), this feature may cause more troubles then usage.
Anyway GPS auto-off is quite advanced feature that should deserve long blog post to explain all details. I mostly suggest to find optimal settings for track recording withouth this feature and after that start playing with GPS auto-off
Hello guys,
quite a lot was wrote and I'm not sure what to wrote first, so just few my suggestions.
1. Accuracy information that you see in Locus do not mean, that point is really that precise, but it's just computed value from received data. So it's possible (mainly on cheeper devices with support for only USA GPS), that Locus show you location 50-100m of your real location, but still show accuracy 10 m. There is anyway nothing, app developers can do with it.
2. GPS Auto-off may reduce battery usage a lot! Amount depend on time intervals. If you set less then 30 sec, then this feature do not have a big sense. For areas with clear sky (where GPS receive location fast) are values more then minute very usable. But if you walk only in deep forest, where your device has a problems with getting precise location (FIX), this feature may cause more troubles then usage.
Anyway GPS auto-off is quite advanced feature that should deserve long blog post to explain all details. I mostly suggest to find optimal settings for track recording withouth this feature and after that start playing with GPS auto-off
Having followed Gnta's suggested setting, and done much the same walk as a few days ago .... I can report that the track obtained is much better - pretty well perfect in fact.
I think I now understand what is happening rather better - and there is perhaps some scope to start using the more complex features.
If you wish to suggest something, that will be fine.
Having followed Gnta's suggested setting, and done much the same walk as a few days ago .... I can report that the track obtained is much better - pretty well perfect in fact.
I think I now understand what is happening rather better - and there is perhaps some scope to start using the more complex features.
If you wish to suggest something, that will be fine.
Good to hear
There is not really much things to "tune up" - you will see...
maybe this defaults help:
and now: hf with Locus
btw
hope you are a PRO user in the meanwhile :)
Good to hear
There is not really much things to "tune up" - you will see...
maybe this defaults help:
and now: hf with Locus
btw
hope you are a PRO user in the meanwhile :)
Replies have been locked on this page!