Skip to main content
Solved

Repair Invalid Polygon Geometry Type

  • October 14, 2021
  • 4 replies
  • 438 views

chris_acc
Contributor
Forum|alt.badge.img+5

Repair Invalid Polygon Geometry TypeHello,

I wish to generate a count of points within Polygons [PointOnAreaOverlayer] but I am unable to generate a count for some polygons because of fme_rejection_code: INVALID_POLYGON_GEOMETRY_TYPE

These Polygons are either Self Intersecting or Multi Polygons. I believe I need to resolve this before I can start counting points inside but Aggregator and Geometry Validator do not seem to fix the issue.

Thanks.

 

Best answer by ebygomm

chris_acc wrote:

The problem with setting Aggregate Handling to Deaggregate is that it then produces too many polygons and I don't know how to merge them back again to the same input amount.

I added another Aggregator after PointOnAreaOverlayer which has helped a little but still a few too many.

There will be some polygons that have 0 Overlaps but I need to include them also.

You should be able to aggregate back after the point on area overlayer, it looks like you can group by the original OBJECTID and select _overlaps under Attributes to Sum

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

4 replies

ebygomm
Influencer
Forum|alt.badge.img+33
  • Influencer
  • October 14, 2021

The PointOnAreaOverlayer does not accept aggregate polygons, you will need to deaggregate them - this can be done within the transformer by setting Aggregate Handling to Deaggregate. You will then need to combine totals from each part of the aggregated polygon to get a total


chris_acc
Contributor
Forum|alt.badge.img+5
  • Author
  • Contributor
  • October 15, 2021
ebygomm wrote:

The PointOnAreaOverlayer does not accept aggregate polygons, you will need to deaggregate them - this can be done within the transformer by setting Aggregate Handling to Deaggregate. You will then need to combine totals from each part of the aggregated polygon to get a total

The problem with setting Aggregate Handling to Deaggregate is that it then produces too many polygons and I don't know how to merge them back again to the same input amount.

I added another Aggregator after PointOnAreaOverlayer which has helped a little but still a few too many.

There will be some polygons that have 0 Overlaps but I need to include them also.


ebygomm
Influencer
Forum|alt.badge.img+33
  • Influencer
  • Best Answer
  • October 15, 2021
chris_acc wrote:

The problem with setting Aggregate Handling to Deaggregate is that it then produces too many polygons and I don't know how to merge them back again to the same input amount.

I added another Aggregator after PointOnAreaOverlayer which has helped a little but still a few too many.

There will be some polygons that have 0 Overlaps but I need to include them also.

You should be able to aggregate back after the point on area overlayer, it looks like you can group by the original OBJECTID and select _overlaps under Attributes to Sum


chris_acc
Contributor
Forum|alt.badge.img+5
  • Author
  • Contributor
  • October 15, 2021
chris_acc wrote:

The problem with setting Aggregate Handling to Deaggregate is that it then produces too many polygons and I don't know how to merge them back again to the same input amount.

I added another Aggregator after PointOnAreaOverlayer which has helped a little but still a few too many.

There will be some polygons that have 0 Overlaps but I need to include them also.

Thanks!

I think the main issue with the Aggregator following on from PointOnAreaOverlayer was that I had selected all of the fields to 'group by' instead of just selecting OBJECTID.


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