Bug with the transformation of LAS file to Cesium 3D tiles

Hi @thomaspetit​ if you inspect the LAS data in the Data Inspector and look at the feature information are the x, y, and z components set to Real32? If so you could use a PointCloudComponentTypeCoercer to change them to Real64. I had this issue with an E57 file but it may help with LAS.

Thanks for your answer, I tried a lot of things without any concluant results.

Whatever the way, it leads to the same warning :

@thomaspetit​  Can you provide the workspace?

Here is it

Do you see what's going wrong ?

Hi @thomaspetit​ sorry for the delay, yes I can see the issue, can you provide the LAS file also?

Thanks, Daragh

Hi,

I can't send you the original file but here is a wetransfer to a similar file : https://we.tl/t-kQEiKLSBy5

Thanks, Thomas

Hi Thomas,

So looking at the documentation for Cesium 3D Tiles, FME does not support the writing of point clouds. So a workaround to this is to create a surface of the point cloud and drape the appearance over it. Please also so see these two articles for an explanation on some of the transformers that I used.

https://community.safe.com/s/article/creating-a-raster-from-a-point-cloud

https://community.safe.com/s/article/point-cloud-to-3d-terrain-model-with-buildings-dwg

I have attached the workspace so you can see if it works for you.

Thanks, Daragh

Hi Daragh,

Thanks for all your help !

I have this specific problem and I cant see the attached workspace, nor I find the linked articles helpful enough. Furthermore, I’m wondering that if a simple LAS reader to Cesium 3D tiles writer solution is not working, why does the software even let me run this workflow without any errors? I’m clearly getting some .pnts output with decent file size so what is this then if it’s not readable Cesium output???

Thats the solution - >

What can the Cesium 3D Tiles Writer

support in the output data? →

→

Geometry Support