Point Cloud renderer treats Unsigned8 data as Signed8

hobu commented 10 months ago

What is the bug or the crash?

UserData fields in LAS content is interpreted as Signed8 (int8_t) instead of Unsigned8 (uint8_t), which they should be.

The attached data should be showing data in the following range:

      {
        "average": 150.1949131,
        "count": 69472,
        "maximum": 254,
        "minimum": 127,
        "name": "UserData",
        "position": 10,
        "stddev": 37.30480778,
        "variance": 1391.648683
      },

As shown by the screen shot, it is in the wrong range

Screenshot 2023-11-09 at 8 47 00 AM user-data.copc.laz.zip

Steps to reproduce the issue

See screenshot

Versions

3.32. I haven't checked the latest.

Supported QGIS version

[ ] I'm running a supported QGIS version according to the roadmap.

New profile

[ ] I tried with a new QGIS profile

Additional context

No response

ntw-au commented 10 months ago

Possibly unrelated due to different fields in play, but https://github.com/qgis/QGIS/issues/54365 also relates to field type misinterpretation.

max-mapper commented 9 months ago

I am also experiencing this issue, but it's preventing me from using the Export > Save As dialog. When I try to save a .las file I get this error:

Export failed: A problem occurred while exporting: Unable to set data and convert as requested: UserData:int(-57) -> uint8_t

qgis / QGIS