Add geometry_msgs/msg/VelocityWithCovarianceStamped (backport #323)#334
Merged
Conversation
Contributor
|
Pulls: #334 |
ahcorde
approved these changes
Jun 2, 2026
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
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.
Description
Add the
geometry_msgs/msg/VelocityWithCovarianceStamped.msgmessage to represent a fully-qualified velocity with uncertainty. This fills a gap betweengeometry_msgs/msg/VelocityStamped, which provides fully-qualified velocity without uncertainty, andgeometry_msgs/msg/TwistWithCovarianceStamped, which provides convention-qualified velocity (implicit body and reference frames) with uncertainty. #322 describes this void in greater detail.Fixes #322.
Is this user-facing behavior change?
Yes, this change adds a new message type to
geometry_msgswhich users will have access to. It does not modify any existing message types, so use of the new message type should be entirely "opt-in" with backwards compatibility preserved.Did you use Generative AI?
No.
Additional Information
The new
VelocityWithCovarianceStampedmessage intentionally duplicates the fields inVelocityStampedwhile adding the covariance field. There is no clean way that I see to either composeVelocityStampedwithinVelocityWithCovarianceStampedor break out common fields to a new message type (e.g.,QualifiedVelocity) without either modifying existing message definitions or creating a non-standard message structure.This is an automatic backport of pull request #323 done by [Mergify](https://mergify.com).