-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
How to get the corresponging image coordinates (rows and columns) of given 3D points captured by RealSense senor? #5475
Comments
I hope that the discussion in the link below, which looks at Open3D, will have something useful for you. I recommend going back to the start of the discussion after reading the final comment in the link above. |
Given a 3D point, you can find a corresponding 2D pixel using |
Hi, Thanks for your reply! |
Hello, I want to know, is the original point of the 3D points same with that of the color camera coordinate? |
Not entirely sure what you mean, are you asking if you'll get back to the exact same pixel if you project from a 3d point which was originally associated with a certain pixel? I don't know for sure, but I think this wouldn't necessarily be guaranteed due to rounding errors etc. It should be close though. |
Hello, I want to konw, which intrinsics should I use? the intrinsics of depth frame or color frame? |
You should use the intrinsics that your point cloud is aligned to. So if your point cloud is calculated from a normal depth image you should use the depth intrinsics, and if the depth image was aligned to colour you'd use colour intrinsics. |
@JimXu1989 hello, do you need further assistance on this topic ? |
Issue Description
<Describe your issue / question / feature request / etc..>
I have capture some 3D points by my D435i, and I have clustered the 3D points by Open3D.
Now I want to know the corresponding positon of each 3D points cluster in the color image, that will help me to know which 3D points cluster is needed, and which is noise.
Thanks a lot!!!
The text was updated successfully, but these errors were encountered: