Hello, got wrong result through clipping function: lines which are out of the Clipper-Area are in the Output as Clipper_inside. Can someone tell me the reason? Workbench with input-Shapes are attached.
Very strange! looking more into it shows the Spatial Relator creating the correct result (does not intersect) and setting the Clippees on Clipper Boundary on outside results in the lines returned as outside which can mean that the clipper is somehow still detecting the boundry of the clipper.
I would contact Safe about this.
Very strange! looking more into it shows the Spatial Relator creating the correct result (does not intersect) and setting the Clippees on Clipper Boundary on outside results in the lines returned as outside which can mean that the clipper is somehow still detecting the boundry of the clipper.
I would contact Safe about this.
I think it's a known bug since FME 2017 RC does not exhibit this behavior.
You can test the 2017 RC with your dataset, according to the change log there are a lot of improvements to the Clipper: http://www.safe.com/support/support-resources/fme-downloads/beta/
I think it's a known bug since FME 2017 RC does not exhibit this behavior.
You can test the 2017 RC with your dataset, according to the change log there are a lot of improvements to the Clipper: http://www.safe.com/support/support-resources/fme-downloads/beta/
I wonder if this is still an issue in the latest 2016 version, I am using 2016.1.0.1 here, otherwise 2017 or 2015 is the answer....
I wonder if this is still an issue in the latest 2016 version, I am using 2016.1.0.1 here, otherwise 2017 or 2015 is the answer....
I wonder if this is still an issue in the latest 2016 version, I am using 2016.1.0.1 here, otherwise 2017 or 2015 is the answer....
@greenzone
the Clipper gets the blames.
The 3 input objects are self intersecting. (have 3 vertices in a switchback move..)
Use Chopper by 2 on them and then a Matcher 2D lenient. Input the 3 single matched into Clippee input port...now the are correctly treated as outside.
@greenzone
the Clipper gets the blames.
The 3 input objects are self intersecting. (have 3 vertices in a switchback move..)
Use Chopper by 2 on them and then a Matcher 2D lenient. Input the 3 single matched into Clippee input port...now the are correctly treated as outside.
You're right about the switchback, but it is clearly a regression in the Clipper since it used to work in FME 2015 and now works again in 2017.
@gio thanks for Information! As for me: it is not about blaming, it is about having tool doing what it did, without searching for Workarounds.