Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add missing tutorial page #939

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions image_pipeline/doc/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,7 @@ stereo disparity images, and stereo point clouds. Components include:

self
camera_info
tutorials
changelog
camera_calibration <../camera_calibration/index.html#http://>
depth_image_proc <../depth_image_proc/index.html#http://>
Expand Down
26 changes: 26 additions & 0 deletions image_pipeline/doc/tutorials.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
Tutorials
=========

.. _`Remapping camera_info Topics`:

Remapping camera_info Topics
----------------------------
When a ``camera_info`` topic is needed, an image_transport camera subscriber
is typically used. ROS convention for naming ``camera_info`` topics is:

* **camera/image** - an image in namespace ``camera``.
* **camera/camera_info** - the associated camera info.

So if a node subscribes to a topic called ``image``, and the user remaps this
to ``my_camera/image``, then the associated camera info will be automatically
remapped to ``mycamera/camera_info``.

Most ROS 2 camera drivers will follow the convention, but occasionally they do
not. In this case, you will have to manually remap the camera_info - but due
to the way that ROS 2 remapping works you have to use the fully resolved
camera info topic. An example:

* ``image`` is remapped to ``my_camera/image``.
* The fully resolved name for the camera info is now ``my_camera/camera_info``.
* If your camera driver actually publishes ``another_ns/camera_info``, then
you would have to remap ``my_camera/camera_info`` to ``another_ns/camera_info``.
Loading