[ros-users] Combine robot_state_publisher with tf::TransformListener?

Kelsey Hawkins kphawkins at gmail.com
Wed Sep 17 12:49:59 UTC 2014

I'd bet that 90-100% of transform requests in typical ros systems run
through a chain delivered through robot_state_publisher. Wouldn't it make
sense to optionally allow tf::TransformListener to parse a URDF and
subscribe to /joint_states in addition to /tf? The advantage is that you
can do proper interpolation between joint configurations and you vastly
reduce the bandwidth of /tf. Plus, you eliminate a processor intensive node
which is mostly relaying redundant information easily read from the URDF.

I'm sure this isn't a novel idea, but are there any plans to integrate this
behavior into ROS core? Any caveats?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-users/attachments/20140917/cb7ae35b/attachment.html>

More information about the ros-users mailing list