Squeezed point cloud

[step90]

Hi all,
I am importing a txt file with X, Y, Z and Scalar field values. The coordinates are projected (so in meters) and I correctly apply the shift to have a similar scale. Unfortunately the point cloud still remains like a line of points (the typical error when you import geographic coordinates). By clicking the info of a random point I can say that the Z coordinate is not read but it's associated to the scalar field (that has big numbers). I wonder how it is possible to specify the right column for the Z coordinates or if there are other solutions to import this cloud.
Here an example:

XCoord,YCoord,ZCoord,GRID_COD_1
620374.55108052,5148453.86907267,3893.699951,1659190.000000
620374.85108052,5148453.86907267,3894.169922,1715560.000000
620375.15108052,5148453.86907267,3894.649902,1840670.000000
620375.45108052,5148453.86907267,3895.129883,1875600.000000
620375.75108052,5148453.86907267,3895.600098,1880090.000000
620376.05108052,5148453.86907267,3896.080078,2029570.000000
620376.35108052,5148453.86907267,3896.550049,2155520.000000

Thank you very much,
Stefano

[daniel]

In the 'ASCII file' loading dialog, you can check and change the role of each column.

But on my side the roles are properly assigned (with the 2.13.alpha version at least):

load_ascii.JPG (72.39 KiB) Viewed 887 times

[stefano.ponti]

Hi Daniel,
thank you for your interest. I gave a try also on the 2.13 but the result is the same: a correct importation (like the screenshot you showed) but a wrong cloud generation. If you pick the information of a single point the weird thing is that the scalar value is duplicated both on the scalar field and Z (see attachment)...
I can send you the cloud if you need to try as well.
Thank you again,
Stefano

[daniel]

Yes, it will be probably easier. You can send it to admin[at]cloudcompare.org

[stefano.ponti]

Dear all,
i thank Daniel for the suggestion: at mid cloud (4 million line on 9 millions) of the txt file he noticed that the Z was switched with the scalar field value, probably an error due to ArcGIS exportation. I solved the problem by re-exporting the cloud with SAGA gis.
Have a nice day everyone!
Stefano