Skip to content

Point Cloud Size Mismatch with Expected Dimensions #89

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

Open
Charley23 opened this issue Feb 9, 2025 · 1 comment
Open

Point Cloud Size Mismatch with Expected Dimensions #89

Charley23 opened this issue Feb 9, 2025 · 1 comment

Comments

@Charley23
Copy link

I am trying to use the /camera/registered_depth/points topic to obtain the exact 3D coordinates for specific RGB pixels. I’m using the Orbbec 336L camera with a resolution of 1280x720, and I would expect the point cloud to have the same resolution, with NaN values for depths that weren't measured.

However, I am receiving PointCloud2 messages where the width is reported as 540072 (which seems to vary) and the height is 1.

Is this behavior expected, or is it an error?
If this is not an error, how can I match a specific RGB pixel with its corresponding point in the point cloud?

Thank you for your help!

@jjiszjj
Copy link
Collaborator

jjiszjj commented Feb 20, 2025

@Charley23 Hello,Thank you very much for your feedback.
1.Regarding the received PointCloud2 message, the width is reported as 540072 (seems to be different) and the height is 1, which is as expected, depending on the setting of the ordered_pc parameter

2.We have matched RGB pixels to their corresponding points in the point cloud,You can check whether the program in this part meets your expectations :

void OBCameraNode::publishColoredPointCloud(const std::shared_ptr<ob::FrameSet> &frame_set) {

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants