Why points with low GPS accuracy get recorded anyway?
This week I was recording a track with Locus Pro v3.32.2 and heared some "beeps". After looking at the map on the screen I saw there were points completely off track, probably due to GPS errors. There was a clear sky but a lot of wind, don't know if it was the culprit. Is the beep produced by Locus?
However when I started the recording I chose the "on foot / walking" profile, so I'm asking: why does Locus record those points anyway, even though it's impossible to teleport away from the track?
Please consider the attached GPX file (segment #2 in particular); will it be possible to filter those errors before they get recorded? The errors have an high PDOP so the application should be able to tell them apart according to the chosed profile.
At the moment I deleted the points with the track editor after saving the track, but during the hiking the statistics are misrepresented due to the problem and it's a tedious process anyway.
EDIT: I also would like - if it will be possibile in the future - a feature like THIS; unfortunately it still didn't receive so many votes :-(
The same question
Track snap to street technique.
Only service I know (planning tool !)
See Komoot web. Probably is using GraphHopper tech.
As your example track is badly misaligned I had some quick manual reedit.
Removing the largest track deviations. Than deleted 2 small segments out of the total original 4.
1. See the manual reedit gpx attached. (Fast edit)
2. Komoot web: Import that cleanded gpx and use for planning a (hiking) path.
If you want to see the new design and gpx download you have to register and buy the regional maps !
Komoot = commercial company ! New users obtain one (local region) map for free. ( A Komoot Candy)
However very nice to be used for an experiment. See a result in the link. See the "auto" snap to street action ! (Some manual fine tuning is still possible)
Do not expect "any tech wonder" as imo manual replanning by recorded tracks as template probably is the faster method at least when using such a "dirty" recorded track.
https://www.komoot.com/tour/43167743?ref=wtd
Track snap to street technique.
Only service I know (planning tool !)
See Komoot web. Probably is using GraphHopper tech.
As your example track is badly misaligned I had some quick manual reedit.
Removing the largest track deviations. Than deleted 2 small segments out of the total original 4.
1. See the manual reedit gpx attached. (Fast edit)
2. Komoot web: Import that cleanded gpx and use for planning a (hiking) path.
If you want to see the new design and gpx download you have to register and buy the regional maps !
Komoot = commercial company ! New users obtain one (local region) map for free. ( A Komoot Candy)
However very nice to be used for an experiment. See a result in the link. See the "auto" snap to street action ! (Some manual fine tuning is still possible)
Do not expect "any tech wonder" as imo manual replanning by recorded tracks as template probably is the faster method at least when using such a "dirty" recorded track.
https://www.komoot.com/tour/43167743?ref=wtd
Hi,
unwanted GPS deviations during recording can be filtered out by setting up the "Required GPS accuracy" parameter in track recording profile settings to a lower value, e.g. 10-20 m. "Beeps" - check GPS & sensors settings > Position acquired/lost notification.
Hi,
unwanted GPS deviations during recording can be filtered out by setting up the "Required GPS accuracy" parameter in track recording profile settings to a lower value, e.g. 10-20 m. "Beeps" - check GPS & sensors settings > Position acquired/lost notification.
OKay, so other options of the "beeping" are - notifications of a forthcoming point (via Point alert or during guidance to a point), notification about leaving a navigated/guided route, beep notification of forthcoming direction change during navigation/guidance, switch to guidance from navigation when you are too far from the original navigated route. If nothing of these is your case, then the beeping comes from other source, not from Locus.
OKay, so other options of the "beeping" are - notifications of a forthcoming point (via Point alert or during guidance to a point), notification about leaving a navigated/guided route, beep notification of forthcoming direction change during navigation/guidance, switch to guidance from navigation when you are too far from the original navigated route. If nothing of these is your case, then the beeping comes from other source, not from Locus.
Replies have been locked on this page!