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
Hello! I have been using this plugin to process some LiDAR data I am getting from the ICGC and am glad to have some tools right in GH.
I first open the .laz files in Cloud Compare and export them to .e57. I then import into Rhino and use the Cockroach GH tools to crop, merge, mesh, etc. The lidar data includes intensity values assigned to each point. I can use this, for example, to assign a greyscale color to the point cloud which represents this intensity value.
When I use Box Crop of Cloud Normals components the resulting point cloud no longer has these Point Values. With other components, like Cloud Merge, the Point Values are carried over.
Hello @fraguada , thanks for the feedback and suggestion, we will definitely have a look into that. Indeed, what you are mentioning are most probably the radiance values that are not carried over in some methods. We will add this to the revision list.
Hello! I have been using this plugin to process some LiDAR data I am getting from the ICGC and am glad to have some tools right in GH.
I first open the .laz files in Cloud Compare and export them to .e57. I then import into Rhino and use the Cockroach GH tools to crop, merge, mesh, etc. The lidar data includes intensity values assigned to each point. I can use this, for example, to assign a greyscale color to the point cloud which represents this intensity value.
When I use Box Crop of Cloud Normals components the resulting point cloud no longer has these Point Values. With other components, like Cloud Merge, the Point Values are carried over.
For example, the Box Crop component passes location, normal, and color to the cropped cloud, but not the Point Values:
https://github.com/9and3/Cockroach/blob/Cockroach/CockroachGH/Cleaning/CloudBoxCrop.cs#L116
My suggestion is to add these values by using the AddRange overflow which allows the 4th argument:
https://developer.rhino3d.com/api/RhinoCommon/html/M_Rhino_Geometry_PointCloud_AddRange_3.htm
The text was updated successfully, but these errors were encountered: