Solved

FME Desktop 2020: The “clipper” tool fails to generate the expected result,

  • 20 December 2021
  • 5 replies
  • 1 view

Badge +5

FME Desktop 2020: The “clipper” tool fails to generate the expected result,

 

In the screenshot below, I wanted to clip the blue color from the red color. As there is not intersection between these two colors, the result should be the red color itself. However, the result not exactly the red color.

 

What could be the issue here?

 

Clip_1382 

Clip_1383 

Clip_1384 

Clip_1385 

 

 

 

 

 

 

 

 

 

 

 

 

 

The data and the work bench are attached

icon

Best answer by caracadrian 21 December 2021, 06:38

View original

5 replies

Badge +20

There seems to be a "bug" in the feature geometry.

If you insert a GeometryRefiner (I inserted it after GeometryCoercer) FME should give you the correct result.Refiner

Badge +5

Thank you caracadrian for the help.

 

Does the “geometryrefiner” tool change the original geometry?

 

 

Clip_1398

Badge +20

Thank you caracadrian for the help.

 

Does the “geometryrefiner” tool change the original geometry?

 

 

Clip_1398

This is a trick question 😀

It does but it doesn't...

If you are thinking at vertices, lines, arcs and so on, it doesn't.

If you are thinking at path and curves, it does.

I think the help explains it best:

  • Any homogeneous IFMEAggregate will become a multi (IFMEMultiCurve, IFMEMultiArea, IFMEMultiPoint, or IFMEMultiText).
  • Any IFMEAggregate or multi with only one member will be replaced by its single part.
  • Any IFMEDonut with no holes will become an IFMEPolygon or IFMEEllipse.
  • Any IFMEPath with only one segment will be replaced by that segment.
  • Consecutive IFMELine segments within an IFMEPath will be combined.

https://docs.safe.com/fme/2021.2/html/FME_Desktop_Documentation/FME_Transformers/Transformers/geometryrefiner.htm

Badge +5

Thank you for the input. This is very useful

Badge +5

I found out that the “geometryrefiner” tool does change the geometry and appears not to bring the solution we are looking for.

 

I’m not sure if this bug is going to be fixed soon

 

Could be there a tool that can IDENTIFY the cause of this issue such that it can be fixed at the level of the source of data (AutoCAD)?

Reply