Skip to main content
Question

AreaOnAreaOverlayer Not Including All Overlapping Polygons In Output

  • June 20, 2018
  • 5 replies
  • 31 views
R
Forum|alt.badge.img

I'm using the AreaOnAreaOverlayer to intersect two large sets of polygons (Polygon 1 & Polygon 2 for clarity), one of which (Polygon 1) contains overlapping polygons which are sometimes coincident with each other, but with different attributes. The transformer is only overlaying one of several polygons from Polygon 1 with Polygon 2 and dropping the others from the output, but I need all of them to be intersected and output.

What other transformers can I use to prepare the data so that all polygons are intersected?

I'm using FME Workbench 2016.1, and can't currently upgrade.

Thanks,

Matt

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

5 replies

fmelizard
Safer
Forum|alt.badge.img+20
  • fmelizardSafer
  • Safer
  • 3719 replies
  • June 20, 2018

@ronaldmcoker Why are 822 features getting rejected? Try a GeometryFilter and GeometryValidator - possibly an Intersector. Are you generating a list with the AreaOnAreaOverlayer?

R
Forum|alt.badge.img
  • ronaldmcoker
  • Author
  • 20 replies
  • June 21, 2018

@ronaldmcoker Why are 822 features getting rejected? Try a GeometryFilter and GeometryValidator - possibly an Intersector. Are you generating a list with the AreaOnAreaOverlayer?

Hi Dan,

 

Generating List: No. I will try out Filter and Validator and see if anything comes of that.

 

I'm also having the same issue with SpatialRelator though. Only one of many stacked polygons' attributes from the Supplier is being included in the output.

 

Thanks.

 

 

 

R
Forum|alt.badge.img
  • ronaldmcoker
  • Author
  • 20 replies
  • June 21, 2018

@ronaldmcoker Why are 822 features getting rejected? Try a GeometryFilter and GeometryValidator - possibly an Intersector. Are you generating a list with the AreaOnAreaOverlayer?

"WARN |Output 822 features which had incorrect geometry for the given input port"

 

 

R
Forum|alt.badge.img
  • ronaldmcoker
  • Author
  • 20 replies
  • June 21, 2018

@ronaldmcoker Why are 822 features getting rejected? Try a GeometryFilter and GeometryValidator - possibly an Intersector. Are you generating a list with the AreaOnAreaOverlayer?

@DanAtSafe For some reason these transformers compare spatially with the last polygon out of many coincident polygons. I noticed the OBJECTID for the polygon with attributes carried over to the product of the SpatialRelator is always the highest out of a group of matching/coincident polygons.

 

 

Of course, I'm new to FME, so I haven't really grasped the necessity of using lists or some other tools, so I apologize for that.

 

fmelizard
Safer
Forum|alt.badge.img+20
  • fmelizardSafer
  • Safer
  • 3719 replies
  • June 21, 2018
@DanAtSafe For some reason these transformers compare spatially with the last polygon out of many coincident polygons. I noticed the OBJECTID for the polygon with attributes carried over to the product of the SpatialRelator is always the highest out of a group of matching/coincident polygons.

 

 

Of course, I'm new to FME, so I haven't really grasped the necessity of using lists or some other tools, so I apologize for that.

 

Hi @ronaldmcoker Please file a case via https://www.safe.com/support/report-a-problem/ Thanks!

 

Community Stats

32,085
Posts
121,845
Replies
39,727
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.