drivers: gnss: Add geoid separation to navigation_data #84547
+13
−1
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
zephyrbot
requested review from
bjarki-andreasen,
d3zd3z,
fabiobaltieri,
mrfuchs,
Sir-Branch and
tomi-font
Currently altitude is only provided above MSL. Adding geoid seperation allows for ellipsoidal height to be determined. Signed-off-by: Maxmillion McLaughlin <[email protected]>
maxmclau
force-pushed
the
gnss-geoid-sep
branch
from
cafa6e2 to
4d71f1d
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.
Currently altitude is only provided above MSL. Adding geoid separation allows for ellipsoidal height to be determined. This is important for many applications.
Curious whether others think this should live in
navigation_dataorgnss_info