[FIXED] RGB Color fields - float or int ?

If you are allergic to bug trackers, you can post here any remarks, issues and potential bugs you encounter
Post Reply
ThomasRisto
Posts: 13
Joined: Tue Mar 11, 2014 9:47 am

[FIXED] RGB Color fields - float or int ?

Post by ThomasRisto »

Hi there !

I seem to be having a problem when loading a point cloud (.las or ascii) when the color fields have been encoded in float32 (range from 0 to 255.0) instead of integers.

Basically, the data are the same, but if they are written as 255.00, I'll get only black points when switching to color mode (I tried floating points RGB colors in [0,1.0] but it doesn't work).

It's not a very important problem, but it took me some time to figure out what was happening...

Maybe it's not hard to fix, maybe this post can also help others understand why they can't color their point clouds ;)

Cheers
Thomas
daniel
Site Admin
Posts: 7709
Joined: Wed Oct 13, 2010 7:34 am
Location: Grenoble, France
Contact:

Re: RGB Color fields - float or int ?

Post by daniel »

For LAS files it's a bit strange (as the job is done by the LASlib library).

But for ASCII files, indeed CC assumes only integers values between 0 and 255 for the moment. It will be easy to accept floating point values between 0.0 and 255.0 indeed (we'll keep only their integer part though).
Daniel, CloudCompare admin
ThomasRisto
Posts: 13
Joined: Tue Mar 11, 2014 9:47 am

Re: RGB Color fields - float or int ?

Post by ThomasRisto »

Thansk for the answer !

About the LAS, maybe it's due to the way I write it myself (with laspy), so don't bother...
Post Reply