-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Trip Recording: Do Not Discard Filtered Points #22567
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Your suggestion to include filtered points as comments in GPX files is interesting. It's true that being able to see which points were filtered out could be very helpful for users trying to recover potentially important data, and for us when diagnosing whether recording gaps are due to filtering or other issues. It would offer more transparency into the recording process. |
Good suggestion, but we can't process it later as comments won't be read and displayed - they will be only stored |
Yes, that's why I call it an 'emergency recovery'. Users would have to process the file in Notepad++ or similar, but in theory could recover their complete recording. |
I don't really like implementation idea as it's too complicated and could be easily lost on resave of the track. However we can definitely save filtered points with flag. Probably we can save them into special table and implement special export in Development for example. We can also keep all points for example for 1-4 weeks and then delete them. |
For example 1 button that will export all complete tracks into for last 30 days rec/bak-rec/ |
Hi,
Pls correct is I've misunderstood anything above |
Note inspired by the discussion in For desktop/PC applications, I normally put such sparsely-used settings in a config file/whatever settings contaoner used (not adding them into GUI). |
It's valid idea. But, IMHO, less intrusive and complex is to simply include all points in the gpx file, but simply place the 'filtered' ones in With the exception of the 'minimum displacement' filter: That one is often used to keep redundant data out of the gpx to keep file size small, and these points with small displacement can always be discarded, this will not result in loosing essential data. |
One last note : if filtering the small displacements separately from time/speed/accuacy - make it configurable, and-or use the accuracy. |
I had first posted here: #22370
Suggestion: With an increasing number of inexperienced users, would we not do everybody a favor by implementing that points affected by filtering are nevertheless included in the gpx files and simply commented out.
In this fashion
(Perhaps with the exception of the displacement filter, which may be used to keep the gpx file size small, and there you do not lose essential topology of your recording.)
The text was updated successfully, but these errors were encountered: