-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot read field "R" because "rgbRecord" is null #3
Comments
Hi, @mmiler . First of all, thank you for your concern. We do have plans to solve this issue, but not right away. The reason for this issue is that the points cloud samples we have only have RGB values. We will fix this issue as soon as we acquire samples that have "intensity" values. Thank you. |
Hello, There are different record types in LAS data, and some record types do not contain RGB record. Later, we will release the source and jar file when we release the main version. Thank you. |
Great, thank you. I see the changes you made. If I see the changes correctly, you have added Intensity value for all three (RGB) bands. Why not put it as a Intensity attribute without RGB value? 3Dtiles specifications allow it and you get much smaller tiles becouse you store one value, not three. |
First, thanks for the comment. I'll definitely consider that feature, though not right away. The normalized intensity value will be converted to a float or double. When this value is stored as an attribute, it will be stored as text or float, but whether it will be smaller than the RGB(byte[3]) value is something I need to think about a bit more. Thank you for your active feedback. |
Hi,
I have laz files with no RGB, only Intensity and Classification attribute. When I try to process the files I get this error:
Exception in thread "main" java.lang.NullPointerException: Cannot read field "R" because "rgbRecord" is null
Command that I am using is:
java -jar mago-3d-tiler-1.3.0-natives-linux.jar --input /in/RH_W15_fixed -it laz -c 3765 --output /out/RH_W15_fixed/mago_test
Thank you.
The text was updated successfully, but these errors were encountered: