Skip to main content

Hi, I can't find an explanation in the doc about what this error means so that I can avoid it. I'm using a Clipper with Clipper Type 'clippers first' for performance. I'm grouping by row and column tiler output columns which are unique although I do have multipart polygons.

Hi @tfsrichard, you can use the "Clippers First" option only if it's sure that all the Clipper features will have been entered into the Clipper transformer before the first Clipee feature. Is it sure?


Thanks @takashi I do have my clipper above my clippee in the navigator order but clippee's seem to be read in first.


Thanks @takashi I do have my clipper above my clippee in the navigator order but clippee's seem to be read in first.

The reader for Clippers should work first if you have it above the reader for Clipees in the Navigator.

 

However, if you have inserted a blocking-transformer between the reader feauture type and the Clipper port, all the features will be stored there to be processed, so the order of readers won't be preserved.

 

Perhaps have you inserted a Tiler before the Clipper port? The Tiler is a blocking-transformer. If you have inserted it, you cannot use the "Clippers First" option, unless you implement a process to control the order of the features explicitly.

 

 


The reader for Clippers should work first if you have it above the reader for Clipees in the Navigator.

 

However, if you have inserted a blocking-transformer between the reader feauture type and the Clipper port, all the features will be stored there to be processed, so the order of readers won't be preserved.

 

Perhaps have you inserted a Tiler before the Clipper port? The Tiler is a blocking-transformer. If you have inserted it, you cannot use the "Clippers First" option, unless you implement a process to control the order of the features explicitly.

 

 

Thanks Takashi, yes I have blocking transformer (tiler) before the clipper.

 

 


Reply