Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

spatial: add range-rate to bearing object #270

Merged
merged 1 commit into from
Feb 10, 2023

Conversation

daniestevez
Copy link
Contributor

This adds range_rate and range_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.

This adds range_rate and range_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.

Signed-off-by: Daniel Estévez <[email protected]>
@jacobagilbert jacobagilbert merged commit 8fa0416 into sigmf:sigmf-v1.x Feb 10, 2023
@jacobagilbert
Copy link
Member

No objections, is sandboxed to an extension, and is a good idea. Merging.

@daniestevez daniestevez deleted the range_rate branch February 11, 2023 09:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants