Rhino Pointcloud Import Not Working as Expected

[Daniel_Innes]

Hi Dale,

The issue is that large point clouds (I tried one 38Gb .e57) fail to import in their entirety. I found the import command finishes but I am getting rectangular holes in the loaded point cloud similar to Terry’s first image, assumingly due to insufficient memory for the size of point cloud.

Based on other threads, the workaround seems to be making the point cloud smaller by either decimating it or cutting it into chunks:

Pointclouds with 30 billion points can be imported and viewed in Rhino but not all works as I like

@dale, @stevebaer, I imported 33 pointclouds created by Lidar scans of a street and combined them into one cloud with 465.8M pts. If I start slowly when rotating the view, then the response gradually picks up speed while still showing the whole cloud but then after very much rotation, the view shifts to showing only the bounding-box which allows for more rapid movement. After Rhino has shifted to bBox view once, then it immediately jumps back to the bBox view for all subsequent rotations no mat…

Point clouds in Rhino - poor performance

Hello, I wrote an email to tech.eu@mcneel.com but I was told to create a forum post with my issue, so here we go: I am evaluating the Rhino 7 now and I have run into one major problem - poor performance with relatively small point cloud. It is especially problematic for me because my company specializes in delivering data from point cloud. I was told that in Rhino there was no software limit for models and point clouds and the only limitation is my computer, which I consider to be quite power…

I would be keen to know about any updates or other approaches.

Thank you,
Daniel.