readXYZ

(To be removed) Extract XYZ coordinates from point cloud data

readXYZ will be removed in a future release. Use rosReadXYZ instead. For more information, see ROS Message Structure Functions.

Syntax

xyz = readXYZ(pcloud)

Description

xyz = readXYZ(pcloud) extracts the [x y z] coordinates from all points in the PointCloud2 object, pcloud, and returns them as an n-by-3 matrix of n 3-D point coordinates. If the point cloud does not contain the x, y, and z fields, this function returns an error. Points that contain NaN are preserved in the output. To preserve the structure of the point cloud data, see Preserving Point Cloud Structure.

Examples

Read XYZ Values from ROS Point Cloud Message

Load sample ROS messages including a ROS point cloud message, ptcloud.

exampleHelperROSLoadMessages

Read the XYZ values from the point cloud.

xyz = readXYZ(ptcloud);

Input Arguments

pcloud — Point cloud

PointCloud2 object handle

Point cloud, specified as a PointCloud2 object handle for a 'sensor_msgs/PointCloud2' ROS message.

Output Arguments

xyz — List of XYZ values from point cloud

matrix

List of XYZ values from point cloud, returned as a matrix. By default, this is a n-by-3 matrix. If the point cloud object being read has the PreserveStructureOnRead property set to true, the points are returned as an h-by-w-by-3 matrix. For more information, see Preserving Point Cloud Structure.

Tips

Point cloud data can be organized in either 1-D lists or in 2-D image styles. 2-D image styles usually come from depth sensors or stereo cameras. The input PointCloud2 object contains a PreserveStructureOnRead property that is either true or false (default). Suppose you set the property to true.

pcloud.PreserveStructureOnRead = true;

Now calling any read functions (readXYZ,readRGB, or readField) preserves the organizational structure of the point cloud. When you preserve the structure, the output matrices are of size m-by-n-by-d, where m is the height, n is the width, and d is the number of return values for each point. Otherwise, all points are returned as a x-by-d list. This structure can be preserved only if the point cloud is organized.

Version History

Introduced in R2019b

R2021a: ROS Message Structure Functions

You can now create messages as structures with fields matching the message object properties. Using structures typically improves performance of creating, updating, and using ROS messages, but message fields are no longer validated when set. Message types and corresponding field values from the structures are validated when sent across the network.

To support message structures as inputs, new functions that operate on specialized ROS messages have been provided. These new functions are based on the existing object functions of message objects, but support ROS and ROS 2 message structures as inputs instead of message objects.

The object functions will be removed in a future release.

Message Types	Object Function Name	New Function Name
Image CompressedImage	readImage writeImage	rosReadImage rosWriteImage
LaserScan	readCartesian readScanAngles lidarScan plot	rosReadCartesian rosReadScanAngles rosReadLidarScan rosPlot
PointCloud2	apply readXYZ readRGB readAllFieldNames readField scatter3	rosApplyTransform rosReadXYZ rosReadRGB rosReadAllFieldNames rosReadField rosPlot
Quaternion	readQuaternion	rosReadQuaternion
OccupancyGrid	readBinaryOccupanyGrid readOccupancyGrid writeBinaryOccupanyGrid writeOccupanyGrid	rosReadOccupancyGrid rosReadBinaryOccupancyGrid rosReadOccupancyGrid rosWriteBinaryOccupancyGrid rosWriteOccupancyGrid
Octomap	readOccupancyMap3D	rosReadOccupancyMap3D
PointStamped PoseStamped QuaternionStamped Vector3Stamped TransformStamped	apply	rosApplyTransform
All messages	showdetails	rosShowDetails