After field testing this, user chosen precision acts as a minimum not by match in geonav and gnss.
I found two ui related bugs that this PR fixes including:
switching from float rtk to rtk in gnss, user could quickly press collect to save an observations and bypass the precision requirement (when precision is GPS)
minor repeated measures visual bug
Type of change
What type of changes does your code introduce? Put an x in boxes that apply.
[ ] CHANGE (fix or feature that would cause existing functionality to not work as expected)
[ ] FEATURE (non-breaking change which adds functionality)
[x] BUGFIX (non-breaking change which fixes an issue)
[ ] ENHANCEMENT (non-breaking change which improves existing functionality)
[ ] NONE (if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)
Checklist:
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have updated relevant documentation
Changelog entry
Please add a one-line changelog entry below. This will be copied to the changelog file during the release process.
Description
fixes #854
After field testing this, user chosen precision acts as a minimum not by match in geonav and gnss.
I found two ui related bugs that this PR fixes including:
Type of change
What type of changes does your code introduce? Put an
xin boxes that apply.CHANGE(fix or feature that would cause existing functionality to not work as expected)FEATURE(non-breaking change which adds functionality)BUGFIX(non-breaking change which fixes an issue)ENHANCEMENT(non-breaking change which improves existing functionality)NONE(if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)Checklist:
Changelog entry
Please add a one-line changelog entry below. This will be copied to the changelog file during the release process.