consider extending NavSatFix with an optional orientation
Open
Nobody has claimed this yet.
backlog
- Dominant language
- C++
- Stars
- 393
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
This is a follwup to the pre Foxy Message API review
- Comment: Consider replacing NavSatFix with gps_common/GPSFix or add some of the fields from GPSFix (the orientations specifically).
This better supports dual antenna gps setups where an accurate heading can be provided and synced with the position fix. - Suggested Action:
Consider a extending the message with an optional orientation. Or consider a new extended message with orientation added. This message is specifically generic to all GNSS systems versus the GPS one has GPS specific data so is not suitable to be replaced.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked pre-Foxy Message API review and compare NavSatFix with GPSFix, focusing on the dual-antenna heading requirement. Done means the project has a resolved decision on whether and how an orientation is exposed, including the message choice and API shape.
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
- 20/100