3D Tile pnts attribute support without draco

[jconnolly-bond]

The workflow I am using to create 3D Tiles does not support draco compression and there does not appear to be any tooling for applying draco compression to pnts files.

Looking at the 3D tile parsing code it appears that there is only support for point attributes / dimensions e.g. Intensity when using draco compression. https://github.com/visgl/loaders.gl/blob/master/modules/3d-tiles/src/lib/parsers/parse-3d-tile-point-cloud.ts#L24

Are there any plans to support accessing attributes in cases where draco compression is not used or am I missing something :)?

Thanks very much.

[Avnerus]

Hi! This was first raised here. Ran a quick check by uploading a LAS to Cesium without using Draco. Intensity is stored in the batch table since it is considered application-specific metadata. However, there is no BATCH_ID feature or BATCH_LENGTH and because of this line the batch table is not parsed. According to the spec these are per-point properties, so I think ideally these properties could be added to tile.attributes as an extra feature? Same as we do in Draco. Thoughts? Also noting that in the next version of 3D Tiles point clouds are in glTFs and I guess Intensity is stored using EXT_meth_features, but is there any tool that produces new 3D Tile point clouds?

[ibgreen]

3d tiles point cloud implementation has not gotten much attention after initial implementation a couple of years ago. The code involved is quite small and should be quite accessible, and PRs are definitely welcome.

Contributing a test file that exhibits the problem is also a good start.

I know @belom88 did some work on 3D Tiles Next for the tile converter project, but likely did not cover point tiles.

[ibgreen]

Closing due to inactivity