Improve built-in support for commonly used messages / Rviz parity

[jtbandes]

Tracking some well-known message types which we could consider adding built-in Studio panels/visualizations for.

• https://docs.ros.org/en/melodic/api/sensor_msgs/html/index-msg.html

• https://github.com/ros-planning/moveit_msgs

• https://github.com/ros-perception/vision_msgs

• https://github.com/luxonis/depthai-ros/tree/noetic-devel/depthai_ros_msgs/msg

• http://wiki.ros.org/shape_msgs

• https://github.com/ANYbotics/grid_map/blob/master/grid_map_msgs/msg/GridMap.msg

• https://github.com/uos/mesh_tools / https://www.researchgate.net/publication/336627583_Tools_for_Visualizing_Annotating_and_Storing_Triangle_Meshes_in_ROS_and_RViz

• foxglove/studio#782

• Display sensor_msgs/Imu messages in the 3D panel #156

• Display nav_msgs/Odometry messages in the 3D panel #146

• foxglove/studio#1630

• foxglove/studio#1972

• foxglove/studio#1325

• Native support for sensor_msgs/JointState joint names in message path input #155

• Support sensor_msgs/MultiEchoLaserScan #113

• foxglove/studio#1049

• foxglove/studio#1615

• foxglove/studio#2812

• foxglove/studio#2895

• foxglove/studio#3156

• foxglove/studio#3213

• foxglove/studio#3215

• foxglove/studio#3088

• https://github.com/foxglove/studio/issues/2359

• https://github.com/foxglove/studio/issues/3396

• Support map_msgs/OccupancyGridUpdate #399

• Render depth images in 3d panel #232

[wkalt]

the tutorial here also allows easy interaction with the robot navigation in rviz, by clicking a location on the map:

https://emanual.robotis.com/docs/en/platform/turtlebot3/quick-start/

[adamconkey]

+1 for moveit_msgs, in particular the DisplayRobotState and DisplayTrajectory are incredibly useful for previewing trajectories and visualizing key waypoints in a the trajectory of a robot arm. Is it recommended to create a separate issue for more specific feature requests?

[jtbandes]

Yes I suppose we could stand to have a separate ticket for the moveit stuff. Is there a reference implementation with screenshots demonstrating how the types are meant to be visualized?

[adamconkey]

It looks like the visualization code is in rviz_plugin_render_tools and in particular there is trajectory_visualization.cpp. There are some examples in the videos/images of the MoveIt tutorials for the trajectory visualization. It looks similar to the URDF visualization in that you're showing the robot with its meshes in the scene, but it's decoupled from a published robot state so that you can e.g. preview a trajectory before executing it, or visualize multiple different plans at once. They also support coloring robot links selectively, which is useful e.g. color links that will collide with an object differently than those that are free of collision.