spatial: add range-rate to bearing object #270
Merged
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 adds
range_rate
andrange_rate_error
fields (in m/s units) to the bearing object. These indicate the time derivative of the range field and its uncertainty or error.We're planning on using range-rate information for GNSS applications, and adding it to the spatial extension bearing object seems most natural, since it already has a range field. A range-rate field seems applicable in other contexts, specially when range-rate is measured via Doppler. Some examples that come to mind are radar and spacecraft navigation.