Welcome to the documentation for std_msgs

README

std_msgs

std_msgs provides many basic message types. Only a few messages are intended for incorporation into higher-level messages. The primitive and primitive array types should generally not be relied upon for long-term use.

For more information about ROS 2 interfaces, see docs.ros.org.

Messages (.msg)

  • ColorRGBA: A single RGBA value for representing colors.

  • Empty: Does not hold any information, useful when the sending of a message would provide sufficient information.

  • Header: Standard metadata for higher-level stamped data types used to communicate timestamped data in a particular coordinate frame.

Primitive Types

std_msgs provides the following wrappers for ROS primitive types, which are documented in the msg specification. It also contains the Empty type, which is useful for sending an empty signal. However, these types do not convey semantic meaning about their contents: every message simply has a field called “data”. Therefore, while the messages in this package can be useful for quick prototyping, they are NOT intended for “long-term” usage. For ease of documentation and collaboration, we recommend that existing messages be used, or new messages created, that provide meaningful field name(s).

Array Types

std_msgs also provides the following “MultiArray” types, which can be useful for storing sensor data. However, the same caveat as above applies: it’s usually “better” (in the sense of making the code easier to understand, etc.) when developers use or create non-generic message types (see discussion in this thread for more detail).

Quality Declaration

This package claims to be in the Quality Level 1 category, see the Quality Declaration for more details.