Skip to main content
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.


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

 

Best answer by jdh

Have you looked at the PointCloudDensityTiler on FME Hub?

https://hub.safe.com/publishers/safe-lab/transformers/pointclouddensitytiler

View original
Did this help you find an answer to your question?

6 replies

siennaatsafe
Safer
Forum|alt.badge.img+10

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. 2021-04-01_15-56-302021-04-01_15-57-23 


jdh
Contributor
Forum|alt.badge.img+28
  • Contributor
  • Best Answer
  • April 5, 2021

Have you looked at the PointCloudDensityTiler on FME Hub?

https://hub.safe.com/publishers/safe-lab/transformers/pointclouddensitytiler


  • Author
  • April 6, 2021

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?


  • Author
  • April 6, 2021
siennaatsafe wrote:

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. 2021-04-01_15-56-302021-04-01_15-57-23 

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.)


jdh
Contributor
Forum|alt.badge.img+28
  • Contributor
  • April 6, 2021
abbe11 wrote:

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.


siennaatsafe
Safer
Forum|alt.badge.img+10
abbe11 wrote:

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).


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings