I want to cut the lines inside a polygon. I thought of using the Clipper transformer however it is very slow. any ideas how I can optimize it and make it faster.
see below:
been a few mins now and looks like it only finished 6 lines..leaving it running until I think of another way to do it.
This may improve the performance.
+45
For example, use a BoundingBoxAccumulator on the polygons, then use that bounding box as the filter in a SpatialFilter to find what lines are completely outside of it. Those lines can be discarded, as if they are completely outside the bounding box, they are never going to be touched by the Clipper.
Depending on how many features there are, it could save the Clipper a lot of work.
I don't say for sure this would be faster, and if this is a one-off project it might not be worth bothering with, but I've had some success with that technique in the past (outside of FME) so if this is a recurring process it would be worth experimenting.
+28
For example, use a BoundingBoxAccumulator on the polygons, then use that bounding box as the filter in a SpatialFilter to find what lines are completely outside of it. Those lines can be discarded, as if they are completely outside the bounding box, they are never going to be touched by the Clipper.
Depending on how many features there are, it could save the Clipper a lot of work.
I don't say for sure this would be faster, and if this is a one-off project it might not be worth bothering with, but I've had some success with that technique in the past (outside of FME) so if this is a recurring process it would be worth experimenting.
I agree, when dealing with 20,000+ features there is usually a performance boost in pre-filtering the data. Less than that performance gain in the clipper is offset by the cost of the spatialFilter.
+15
Depending on how many objects you have, i suggest a AreOnArea overlayer followed by a tester.
AreaonArea has as added advantage the possible use of parallel processing.
First make sure all objects have a unique id.
Use a (single) tiler on both inputs, then separate them using a tester on "fme_feature_type" (expose on readers). Then use a AreaOnArea overlayer and group by tile id's (for instance row_id and column_id).
Mind setting parallel processing on aggressive or higher...you will hog down your entire machine for the duration of the proces ( all cores at 100%..lol).
After this a tester to test for overlaps >1 and fme_feature_type = clipperobjectnames.
Even though the tiling takes a bit o' time, the total proces will be fast.
Try it out.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
