Has anyone else ran into an issue where when you import a point cloud (as an .e57 or .las file) and transform the points at a certain distance, the points start to clamp and display in a grid like projection? Is there a way to fix this other than centering the point cloud? The work I do requires the pc position to be at a certain location to match other incoming data form other collaborators.

- you can maybe separate them as objects, each geo centered to its object and object itself offset to the off-center location

- you can do similar with packed prims if you can keep the individual poincloud sections packed

- or if you need to have them all unpacked within the same object, you can use Attribute Cast to cast P to 64 bit before moving to desired off-center location

@tamte, thank you for your suggestions. The float values are already set at 64-bit in the Lidar node and using an Attribute Cast change nothing. It seems translating the point cloud from the obj level removes this issue. However, I have a particular pipeline that is contained in the geo context that requires the translation to happen before a couple other actions, most of which has been automated in an HDA. Point is, it would be preferred to have the translation happen within the geometry context, and not the object context.

Is there a reason why moving on obj works where geo does not? Is there a software preference or something I am missing?