Comments and answers for "Clipper attribute merge confusion" https://knowledge.safe.com/questions/86689/clipper-attribute-merge-confusion.html The latest comments and answers for the question "Clipper attribute merge confusion" Comment by ras on ras's answer https://knowledge.safe.com/comments/86761/view.html

Thanks for letting me know.

 Tue, 12 Feb 2019 07:13:44 GMT ras Answer by markatsafe https://knowledge.safe.com/answers/86728/view.html

@ras this is an issue with FME and we'll try and fix it. In the meantime, if you connect the output of your SurfaceFootprintReplacer to the Clipper input port then I think it will give you a workaround

Mon, 11 Feb 2019 18:02:17 GMT markatsafe Answer by ras https://knowledge.safe.com/answers/86722/view.html

@egomm Hi and thanks for the reply, I can replace the chair instances with a BoundingBox (solid), result stays the same.

I guess it's a bug, or the Clipper was never intended to be used this way?

Which is a reall bummer...

Now I wonder, if there is a way how run an inclusion test using Python. I think Scipy has a convex hull function.

But it's kind of crazy that I have to DIY. :(


 Mon, 11 Feb 2019 16:46:46 GMT ras Answer by ebygomm https://knowledge.亚搏在线safe.com/answers/86702/view.html

It looks like the clipper geometries are actually getting rejected. I think you can only clip solids with solids. Still, it shouldn't give the appearance of having worked and features still exit via the inside port.


 Mon, 11 Feb 2019 09:13:23 GMT ebygomm Comment by takashi https://knowledge.safe.com/comments/86694/view.html

It seems to be a defect in the Clipper. I would recommend you to contact Safe support to clarify the issue.

Report a Problem

 Mon, 11 Feb 2019 06:32:55 GMT takashi