I can’t use the pointcloudcoercer and then group on ”count” since it still need to be in pointcloud- format when writing to Xyz-fileformat. Do I really need to first write to xyz and then bring it back in to split it up?
Thanks
Solved
Hi, What would be the best solution for splitting a pointcloud into smaller parts based on number of points? Eg. One new output-file for Every 1000 points.
Best answer by jdh
Have you looked at the PointCloudDensityTiler on FME Hub?
https://hub.safe.com/publishers/safe-lab/transformers/pointclouddensitytiler
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+12- Safer
Hi @abbe11
I'd recommend using the PointCloundExpressionEvaluator to create a new component, the expression should be something like @index()/1000. Then, use a PointCloudSplitter to split by that component.
I've attached some images and a workspace as an example. 
+40- Contributor
- Best Answer
Have you looked at the PointCloudDensityTiler on FME Hub?
https://hub.safe.com/publishers/safe-lab/transformers/pointclouddensitytiler
Thanks @jdh , that almost does what I am after. However, Is it also possible to get a "tile-id" to achieve the final split/fanout on?
Hi @abbe11
I'd recommend using the PointCloundExpressionEvaluator to create a new component, the expression should be something like @index()/1000. Then, use a PointCloudSplitter to split by that component.
I've attached some images and a workspace as an example.
Thanks @siennaatsafe, this works well. The newly created component "t" isn't exposed as an component, right? (It is still possible to use it in pointcloudsplitter though, but not as a component in "split by"- drop down.)
+40- Contributor
Thanks @jdh , that almost does what I am after. However, Is it also possible to get a "tile-id" to achieve the final split/fanout on?
You could just add a Counter to get an id for the fanout.
+12- Safer
Thanks @siennaatsafe, this works well. The newly created component "t" isn't exposed as an component, right? (It is still possible to use it in pointcloudsplitter though, but not as a component in "split by"- drop down.)
Hi @abbe11 ,
That's right, it won't count as an exposed component, but can be written in the pointcloudsplitter (however not selected by the dropdown).