-
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
Different result export_to_ply vs np.asanyarray(points.get_vertices()) #9118
Comments
Hi @drapado Do you still require assistance with the problem in this case please? Thanks! |
Hi @MartyG-RealSense yes if possible! I'd like to understand why the pointclouds are inverted when exporting to ply using pyrealsense2. |
Hi @drapado I located another example in the link below of Y and Z being exported when using export_to_ply. In that case, C++ language and a D435i stereo depth model was being used instead of Python and L515 lidar camera. https://programmersought.com/article/80301367145/ It may be related to how RealSense cameras observe a scene by looking outward like a human eye, so the perspective would not be the same as when looking towards the camera from a position in front of it. There is an alternative method of exporting a ply called save_to_ply that you could test. The RealSense SDK has a Python example program called export_ply_example that uses this method. save_to_ply also offers a greater range of options for customizing the ply export by enabling and disabling certain features. |
Hi @drapado Do you require further assistance with this case, please? Thanks! |
@MartyG-RealSense Thanks a lot for your answer, quite clarifying! I don't require further assistance. Closing the issue :) |
That's excellent to hear @drapado - thanks for the update! |
I get different pointclouds when I used
points.export_to_ply
againstnp.asanyarray(points.get_vertices()).view(np.float32).reshape(-1, 3)
. I use the following code:Visualization output:
Why does
points.export_to_ply
kind of invert Y and Z axes?The text was updated successfully, but these errors were encountered: