CloudCompare forum

Hi community,

i have a problem when saving a point cloud in CC.

I open my point cloud (*.laz 1.2 with scalar fields "scan angle rank, number of returns, return number, TIME, intensity and classification) and I segment it using a polygon (shp). Then i save the new point cloud (segment). Apparently everything works fine, but when I add again the segment into CC, the scalar field TIME is gone.

Why the scalar field "TIME" is not available anymore?

Thanks

Nico

Hi,

What version are you using? I remember there was a similar bug a while ago but I thought it was fixed in the latest versions. Otherwise I'll have to check again.

Hi,

I also though about the same thing. First I was using CC 2.7 so then upgrade to 2.8stereo but the problem persists.

I also though that the file may be damaged. I did some tests and it is not the case.

After creating the segment, the scalar field is there. A soon as i save it, the scalar field is gone

Thanks for your help :)

Can you try the 2.9.alpha? I see that the bug I thought about was fixed in the 2.8.1 (only available for Mac now, it will be uploaded soon for Windows - anyway it's the same as the 2.9.alpha with a little less features).

2.9 alpha works perfect. Apparantly there is a hidden bug in the version 2.8 ;)

Thanks Daniel

While is not exact issue I think fits here.

I would like to request to save SF of iluminance as SF because baking it to RGB destroyes colours and having the light baked in SF is really handy in case you whant to merge it later on use it later on or simply export iluminance as rgb later on from CC

I'm not sure to understand: which 'luminance' information are you referring to? The PCV luminance? If yes, and if you are speaking about LAS export, then it's not possible to export it 'as is' because the LAS format has very specific fields in its specifications.

Yes Daniel . AAA I see, I thought there could be like custom fields :\

Can you suggest a format that would hold the data? the Cloud compares own?

I see, you're stuck with the fields you are shown when improting. May be iluminance field could be sotred in the user data field.

Indeed, the custom LAS fields could be used, but the previous library we were using was not handling them correctly. Now that we are using PDAL, it may be easier... but anyway it's not implemented in the current version.