Any plans to support doTransform() with non-stamped message types?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 153
- Forks
- 256
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 14
Description
Feature request
In ROS1, we used to have doTransforms for message types without Headers, but they are missing in ROS2.
Are there any reasons why will omitted these functions in ROS2?
Example with geometry_msgs/Point
ROS1
ROS2
Feature description
Transforms geometry messages without timestamps.
Implementation considerations
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
Compare the ROS1 and ROS2 implementations linked in tf2_geometry_msgs/include/tf2_geometry_msgs/tf2_geometry_msgs.h, especially the referenced sections. Start by understanding how the existing ROS2 transform functions handle stamped messages and how geometry_msgs/Point is represented. Done means agreeing on and implementing support for transforming non-stamped geometry messages, with appropriate validation of the public API and behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- robotics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100