Skip to main content
Solved

Clipper attribute merge confusion

  • February 10, 2019
  • 5 replies
  • 14 views
R
Forum|alt.badge.img

Hello,

I am stuck on a problem that is probably very simple, I just don't get it...

  • I have a simple test IFC file with two rooms and some random furniture:

  • I would like to use FME to run an inclusion test, which furniture is in which room.

My thinking is to extract a center point of every furniture instance and run a spatial join using the Clipper tool. Something like this:

Now, the confusing part.

  • The clipper attribute merge is telling me all the furniture are in just one room:

Why is that?

It works fine using an AreaOverlay, but I really need a 3D inclusion test...

Test IFC and my workspace:

Thanks.

Best answer by markatsafe

@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

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

5 replies

takashi
Influencer
  • takashiInfluencer
  • February 11, 2019

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

Report a Problem

ebygomm
Influencer
Forum|alt.badge.img+33
  • ebygommInfluencer
  • Influencer
  • February 11, 2019

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.

 

R
Forum|alt.badge.img
  • ras
  • Author
  • February 11, 2019

@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. :(

 

M
Forum|alt.badge.img+2
  • markatsafe
  • Best Answer
  • February 11, 2019

@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

R
Forum|alt.badge.img
  • ras
  • Author
  • February 12, 2019
markatsafe wrote:

@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

Thanks for letting me know.

Reply


Helpful Members This Week

Community Stats

31,184
Posts
118,216
Replies
38,795
Members

Latest FME

Terms & ConditionsCookie settings

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
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.