Issue with PLY Conversion Using ouster-sdk on Windows 11

Software
1

I’m encountering an issue with point cloud conversion using the ouster-sdk and would appreciate your assistance.

I’m currently using Windows 11 Home and attempting to convert an older .pcap file into .ply format. The file I’m working with was recorded using image version v2.5.0 on an OS2-128 sensor.

Here are the commands I tested:

ouster-cli source 1.pcap slam save 1.osf
ouster-cli source 1.osf slam save 1_1.ply
ouster-cli source 1.pcap slam save 1.ply

I was able to generate both .osf and .ply files on Windows, but the resulting .ply files could not be opened properly in CloudCompare.
However, when I tried exporting the same data to .pcd, it opened successfully. I also found that when performing the same .ply conversion on Linux, the output worked fine in CloudCompare.

Since I primarily use Windows, switching to Linux just for file conversion is quite inconvenient. Could you please advise on how to properly generate .ply files from .pcap or .osf on Windows so that they are compatible with tools like CloudCompare?

I also attempted to record a video to demonstrate the issue, but it seems video uploads are not supported here.

Thank you in advance for your support. I look forward to your guidance.

Best regards,

2

This might be a bug .. and we need to look into it .. Can you share a corrupt ply file.

In the meantime, you can use pcd format with CloudCompare on Windows platform, or if you specifically need ply then you can use CloudCompare to export the generated pcd files as consider exporting the file as pcd then use CloudCompare to save as ply (ascii or binary).

We did update the code export in the coming release so it might be already resolved with the next version.

3

ply_zip

Hi Samahu,
I’ve attached the .ply file you requested via a link, as direct file attachment wasn’t possible here.

I also tried converting a .pcd file to .ply, as you suggested, but unfortunately that didn’t work either.

For your reference, I ran all tests using version 0.14 of the SDK. I hope this issue has been addressed in version 0.15.

Thank you again for your support.

4

Hi @victo, I have checked the file and found what looks like to be the issue.

It seems that on Windows platform our ply file writer weirdly enough is generating very large values for the REFLECTIVITY values (something on the order of 7.135744979033809e+182). There is no world where this is a valid value for REFLECTIVITY. We need to look further into and find what what is causing it.

Does this happen with all sequences or specific ones. Are you willing to share a short sequence (pcap or osf) where this problem exhibits itself on Windows? I will have one of our team members take a look at it.

I have just looked at the code and this has not been updated it .. so if we don’t fix it before the release it is likely to persist. If you can share a short sequence that exhibit the problem it may help us find the issue faster and maybe amend the code before public release.

5

Hi @Samahu ,
This issue occurs consistently across all the pcap files I currently have.

I installed the Ouster SDK via Python and have not made any modifications to the source code. I simply encountered this behavior while testing the save command.

6

Hi @Samahu ,
After updating to ouster-sdk version 0.15, the PLY file was successfully generated.

1 Like
7

Hi @victo, we have made a patch release 0.15.1 to address this issue and other problems we found in the regarding save of pointclouds. Please considering upgrading to the latest.

1 Like