Brand new tracker functionality: maximum distance tolerance #4589
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
🎉 Ta-daaa, freshly created APKs are available for 847c805: arm64-android |
|
Great ! I hope it will help to avoid this :
Thanks you ! |
suricactus
approved these changes
Sep 19, 2023
nirvn
force-pushed
the
maximum_distance
branch
from
5d968b2
to
847c805
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements a new functionality to QField's tracker, allowing users to set a maximum distance tolerance in-between tracked points/vertices beyond which a received position will be flagged as erroneous.
UI-wise, it looks like this:
I've taken the opportunity to clean up the documentation a bit, as well as renaming a source file and some variables to (hopefully) increase readability of code.