You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If deskewing is required, the current generic dataloader is not loading (and thus, discarding) the timestamp information. Should be easy to do it. I tried with PlyData but it's really slow!
I regularly use the new open3d Tensor API to read/write extra point data like timestamps from .pcd files.
An example of what that API looks like, tested out of context:
import open3d as o3d
import open3d.core as o3c
pc = o3d.t.io.read_point_cloud(file_path)
points = pc.point.positions.numpy() # Here 'positions' is the special reserved attribute name for xyz data.
timestamps = pc.point.t.numpy() # Here 't' is a user-defined extra attribute name in the .pcd file.
timestamps = timestamps / timestamps.max()
return points, timestamps
The gotcha which is why I'm commenting: From what I can see, the Open3d Tensor API .pcd file writer (and I believe file reader) can not work with point clouds larger than 2**31 bytes (about 2.1 GB). I think this limitation isn't a major pain point in the open3d community and the resolution would require a rethink of their file writer's approach, so I don't expect much traction on the open issue.
If deskewing is required, the current generic dataloader is not loading (and thus, discarding) the timestamp information. Should be easy to do it. I tried with PlyData but it's really slow!
snippet that works (but too slow)
The old API from open3d also does not support this, maybe migrating to the tensor API helps (?)
The text was updated successfully, but these errors were encountered: