Cloud Point showing up as a straight line

[LiDoom]

Hello,

For some reason when loading this point cloud file it shows up as a straight line, I can zoom in and out, but I don't see the full extent of the cloud.

[PierreGEOSCAN3D]

Hello, I'm not exactly sure what type of files you are using, but to give you a hint, I have encountered this type of issue before with files where the X, Y, and Z columns were not properly aligned. Make sure that the XYZ coordinates are correctly pointing to the appropriate columns in the table.

[DA523]

check xyz order during import

[daniel]

Also, a classical issue is if the points are expressed in a 'geographical' coordinate system with X and Y being angles, and Z being in meters (i.e. with a totally different scale). CC expects all 3 dimensions to be the same.

[LiDoom]

Also, a classical issue is if the points are expressed in a 'geographical' coordinate system with X and Y being angles, and Z being in meters (i.e. with a totally different scale). CC expects all 3 dimensions to be the same.

Thank you. How can I check or edit this upon import?

[LiDoom]

Hello, I'm not exactly sure what type of files you are using, but to give you a hint, I have encountered this type of issue before with files where the X, Y, and Z columns were not properly aligned. Make sure that the XYZ coordinates are correctly pointing to the appropriate columns in the table.

This is a Mavik drone scan processed in MetaShape and extracted as a point cloud file.

[HeadLess]

Make sure that you are using global shift during opening, if cc revommends it. It might be caused by large coordinate precision loss.

[daniel]

Also, a classical issue is if the points are expressed in a 'geographical' coordinate system with X and Y being angles, and Z being in meters (i.e. with a totally different scale). CC expects all 3 dimensions to be the same.

Thank you. How can I check or edit this upon import?

You'll see that right away by considering the scale/values in the X, Y and Z columns (angular values will be much smaller, and almost all the same)

[LiDoom]

Make sure that you are using global shift during opening, if cc revommends it. It might be caused by large coordinate precision loss.

here's what I see when importing. For some reason I don't have an issue when opening up this point cloud in Quick Terrain Modeler.

[daniel]

And what the bounding-box looks like once you've loaded the cloud?

There's good chances that Quick Terrain Modeler does manage properly geographic coordinate systems...