This object is in archive!
Distance walked being way over recorded
Answered
Each time I've used the recording route facility while walking (twice), the recorded path and hence distance has been way off.
This applies particularly to steep ascents and descents where short zig zags are undertaken but certainly not limited to those times.
The same question
Hi Paul,
could you please post screenshots of the situation here? I don't understand if the recorded track was off the real path or if the distance measurement was incorrect (or both). Michal from Locus team
Hi Paul,
could you please post screenshots of the situation here? I don't understand if the recorded track was off the real path or if the distance measurement was incorrect (or both). Michal from Locus team
Hi, part of one walk.
Pic # 190855
Coming from left I walked directly along the dotted path indicated.The big mass in the middle i walked from a Col up to a peak towards bottom right, back to Col then down from there with many zig zags. At bottom I crossed the river where the dashed road is indicated (at "Y intersection")and walked up dashed road to the yellow road then to left along that.
Pic # 192048
In this pic I maybe walked up to the 2100m contour more or less as indicated, a little bit around over about 1 hectare area there then along the dotted line near 2200 metre mark to the cross and lake indicated.
From there around the curved path underlying as more or less indicated.
Regards Paul Brush
On 8 Jun 2017 6:00 PM, "Locus Map" wrote:
Hi, part of one walk.
Pic # 190855
Coming from left I walked directly along the dotted path indicated.The big mass in the middle i walked from a Col up to a peak towards bottom right, back to Col then down from there with many zig zags. At bottom I crossed the river where the dashed road is indicated (at "Y intersection")and walked up dashed road to the yellow road then to left along that.
Pic # 192048
In this pic I maybe walked up to the 2100m contour more or less as indicated, a little bit around over about 1 hectare area there then along the dotted line near 2200 metre mark to the cross and lake indicated.
From there around the curved path underlying as more or less indicated.
Regards Paul Brush
On 8 Jun 2017 6:00 PM, "Locus Map" wrote:
Thx, I have been in there and have distance recording set at one metre but time interval at 10 seconds. Would that be a problem? Also Time and Distance set.
As an aside (usage suggestion)
Took me a while to work, then remember the second time how to start recording a track IE. You must first create a track to start. I kept selecting display at Top that showed Not Recording, then on the displayed menu would again and again select track recording.
1. Would it be a possibility to offer functionality there that says no track created, create new? Or something like that.
2. Another possibility: is there a button to display your current position on a map, ie press button and have display centre on your current position.
3. Is there a way to pick a point on displayed map and be directed to that point? This could just be straight line but would be useful to" get bearings" when not sure where on map you are in relation to destination.
Thx Paul
On 8 Jun 2017 7:25 PM, "Locus Map" wrote:
Thx, I have been in there and have distance recording set at one metre but time interval at 10 seconds. Would that be a problem? Also Time and Distance set.
As an aside (usage suggestion)
Took me a while to work, then remember the second time how to start recording a track IE. You must first create a track to start. I kept selecting display at Top that showed Not Recording, then on the displayed menu would again and again select track recording.
1. Would it be a possibility to offer functionality there that says no track created, create new? Or something like that.
2. Another possibility: is there a button to display your current position on a map, ie press button and have display centre on your current position.
3. Is there a way to pick a point on displayed map and be directed to that point? This could just be straight line but would be useful to" get bearings" when not sure where on map you are in relation to destination.
Thx Paul
On 8 Jun 2017 7:25 PM, "Locus Map" wrote:
PS sorry, I know the position centering button
On 8 Jun 2017 7:25 PM, "Locus Map" wrote:
PS sorry, I know the position centering button
On 8 Jun 2017 7:25 PM, "Locus Map" wrote:
Hi Paul,
"required accuracy" is the parameter that can influence smoothness of the recorded line - Locus does not record trackpoints that are out of the selected range. However, keep in mind that GPS generally return poor values in a rugged terrain, on steep slopes and in forests.
When you want to record a track, you don't have to create one before. See basics in our manual: http://docs.locusmap.eu/doku.php?id=manual:basics:trackrecord.
Ad 3 - yes you can be guided by a beeline to a point (http://docs.locusmap.eu/doku.php?id=manual:user_guide:functions:guidance#guidance_to_a_point) or you can be navigated (selected routing service calculates the route for you): http://docs.locusmap.eu/doku.php?id=manual:user_guide:functions:navigation:point-to-point
Hi Paul,
"required accuracy" is the parameter that can influence smoothness of the recorded line - Locus does not record trackpoints that are out of the selected range. However, keep in mind that GPS generally return poor values in a rugged terrain, on steep slopes and in forests.
When you want to record a track, you don't have to create one before. See basics in our manual: http://docs.locusmap.eu/doku.php?id=manual:basics:trackrecord.
Ad 3 - yes you can be guided by a beeline to a point (http://docs.locusmap.eu/doku.php?id=manual:user_guide:functions:guidance#guidance_to_a_point) or you can be navigated (selected routing service calculates the route for you): http://docs.locusmap.eu/doku.php?id=manual:user_guide:functions:navigation:point-to-point
Paul,
My track-recording settings for hiking are "2 meters | 5 seconds | 100 meters". I have recorded tracks for about a dozen hiking trips and none have been as inaccurate as the two examples you provided. The tracks I have recorded as usually within a few meters of the true path and don't have erratic points. The area I hike in is has mountains rising to 1500 meters (not alpine terrain but mountainous and forested with thick conifers).
Here is an example of poorer performance but it is still well within the range of GPS accuracy (~ 5-10m).
I hiked the same route twice (once in November and recently in May) and, over a distance of 25 km, the difference between the two tracks was about 500 meters. Most of that difference (0.02%) was due to traveling a slightly different path
My phone (Moto X Play) sits in a nylon pocket attached to my backpack's shoulder strap.
I think poor GPS reception is the primary cause of your track's inaccuracy. It may be due to the terrain but I suspect it is caused by either the phone's placement (it may be buried in the backpack) or possibly even the phone's GPS hardware (it may be substandard).
You should perform this simple test and compare the results: record a track of several kilometers along an open road. Ensure the phone has a clear view of the sky. If the track does not follow the road within a few meters, there may be something wrong with the phone's GPS hardware.
Paul,
My track-recording settings for hiking are "2 meters | 5 seconds | 100 meters". I have recorded tracks for about a dozen hiking trips and none have been as inaccurate as the two examples you provided. The tracks I have recorded as usually within a few meters of the true path and don't have erratic points. The area I hike in is has mountains rising to 1500 meters (not alpine terrain but mountainous and forested with thick conifers).
Here is an example of poorer performance but it is still well within the range of GPS accuracy (~ 5-10m).
I hiked the same route twice (once in November and recently in May) and, over a distance of 25 km, the difference between the two tracks was about 500 meters. Most of that difference (0.02%) was due to traveling a slightly different path
My phone (Moto X Play) sits in a nylon pocket attached to my backpack's shoulder strap.
I think poor GPS reception is the primary cause of your track's inaccuracy. It may be due to the terrain but I suspect it is caused by either the phone's placement (it may be buried in the backpack) or possibly even the phone's GPS hardware (it may be substandard).
You should perform this simple test and compare the results: record a track of several kilometers along an open road. Ensure the phone has a clear view of the sky. If the track does not follow the road within a few meters, there may be something wrong with the phone's GPS hardware.
Replies have been locked on this page!