ros2 / ros2/common_interfaces

Proposal - support velocity and velocity covariance in NavSatFix

Open
#219 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

backlog help wanted
Dominant language
C++
Stars
393
Forks
157
PR merge metrics
No merged PRs in 30d

Description

Feature request

Feature description

In NavSatStatus, there is a field for position covariance. Some GPS receivers also support velocity with a velocity covariance.
I'd like to request some fields added to report both the velocity and accuracy estimates of that velocity

Implementation considerations

There is some thought in other threads about re-adding the GPSFix message support. I'd like to get the ball rolling on this for ROS2 Iron, if possible, since there are two other tickets regarding the NavSatFix message. Seems like a good opportunity to bundle all the changes in one version bump.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the NavSatFix and NavSatStatus message definitions and reviewing the related tickets about re-adding GPSFix support. Clarify the proposed velocity and covariance fields, their compatibility with ROS2 Iron, and the required version bump; the issue does not define enough detail to establish completion criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.