Closed ahcorde closed 3 months ago
Ey @caguero and @tfoote when you have some time, do you mind to review the PR?
I'm not really sure how to handle the doTransform
API in tf2_geometry_msgs
@ahcorde I took a stab at adding some notation here to get us consistent. https://github.com/ros2/ros2_documentation/tree/tf_velocity
Based on this I think that the header.frame_id should be the observation frame. And the other two datatypes should be capturing the semantic meaning. Where the naive transform method is only doing the reprojection of the observation. And then we can have a separate API for adding/subtracting transforms across moving frames which will be more complicated.
I rebased common_interfaces with the same branch name https://github.com/ros2/common_interfaces/tree/ahcorde/rolling/lookupvelocity
It looks like we have some linter errors and a symbol visibility on Windows issue in the CI
Are there any plans to backport this to Iron/jazzy?
Are there any plans to backport this to Iron/jazzy?
It's already on Jazzy, I can backport this to Humble and Iron, because this is not breaking ABI or API
https://github.com/Mergifyio backport humble iron
backport humble iron
Are there any plans to backport this to Iron/jazzy?
It's already on Jazzy, I can backport this to Humble and Iron, because this is not breaking ABI or API
@ahcorde thanks !
Related with this issue https://github.com/ros2/geometry2/issues/643