Ask Your Question

Is there any point in using image_transport republish instead of using CompressedImage in Python?

asked 2014-10-25 23:51:53 -0600

basheersubei gravatar image

I have a Python ROS node that subscribes to a topic of message type CompressedImage. So far it works fine (I play a rosbag with compressed images, run my node, and it correctly reads them [I checked using cv2.imshow()].

I'm probably misunderstanding what the point of compressed_image_transport is. If I have a ROS node (say usb_cam) publishing compressed image messages, and my Python node subscribes to those compressed images (specifying sensor_msgs.msg.CompressedImage as the message type), why would I ever need image_transport or republish for my node (I know it's being used in the publishing node, i.e. usb_cam).

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2016-09-08 01:35:35 -0600

Tommi gravatar image

The answer is a bit late, but in my case it was more convenient to migrate from input data type Images to CompressedImages using republish. This way, I did not have to modify code which stated in multiple occasions the incoming message type as sensor_msgs::Image.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2014-10-25 23:51:53 -0600

Seen: 607 times

Last updated: Sep 08 '16