chore(submodules): bump polaris and pointperfect GPS clients#103
Merged
Conversation
Pin both clients to require a stable >=2D fix before reporting position, and populate PointPerfect GGA quality/sats/HDOP from GPS_RAW_INT.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Bump polaris-client-mavlink and pointperfect-client-mavlink to pick up the stable GPS fix gate (and PointPerfect GGA metadata fixes).
Problem
Both clients accepted GPS positions with only a non-zero lat/lon check, so flapping/no-fix coordinates could be reported to correction services. PointPerfect also hard-coded GGA quality/sats/HDOP.
Solution
Update submodule pointers to: