Skip to main content
Solved

Percentage of polygon overlap using Area on Area overlayer & Expression Evaluator totals 101% when it should be 100%

  • April 26, 2021
  • 11 replies
  • 425 views

helenwhiteley
Contributor
Forum|alt.badge.img

I am using an Area on Area Overlayer and Expression Evaluator to calculate the percentage of overlap of one polygon dataset with another -the scenario is percentage ownership. I have noticed that those polygons that should have 100% overlap / ownership because they are completely within the other, do not show as a nice round 100%, always 99.something up to 101.something. I'm guessing this is something to do with geometry and /or tolerance, but how to solve it? 101% ownership will raise questions when the data is presented!

Best answer by ebygomm

Have attempted to attach... Thanks

The figure held in the Shape_Area field of the smaller polygon does not match the area of the polygon as calculated by FME (before doing any area on area overlaying). So if you are measuring the area after the area on area overlayer and then using this with the Shape_Area to calculate the percentage you are going to see strange results.

 

My suspicion is the differing area values are something to do with the fact that this small polygon is made up of arc segments.

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.

11 replies

david_r
Celebrity
  • 8392 replies
  • April 26, 2021

The obvious, but perhaps somewhat cheeky solution would be to simply set the value to 100.0 if it's > 100.


caracadrian
Contributor
Forum|alt.badge.img+23
  • Contributor
  • 571 replies
  • April 27, 2021

Try setting the Tolerance in AreaOnAreaOverlayer to 0. It can slow down the workspace a little but it should fix the isue.


helenwhiteley
Contributor
Forum|alt.badge.img
  • Author
  • Contributor
  • 5 replies
  • April 27, 2021

The obvious, but perhaps somewhat cheeky solution would be to simply set the value to 100.0 if it's > 100.

Thanks David. I suppose I could! I guess, it makes me concerned for the relative accuracy of all the other percentages though...


helenwhiteley
Contributor
Forum|alt.badge.img
  • Author
  • Contributor
  • 5 replies
  • April 27, 2021

Try setting the Tolerance in AreaOnAreaOverlayer to 0. It can slow down the workspace a little but it should fix the isue.

Thanks. Unfortunately, the issue remains with tolerance set to 0.


caracadrian
Contributor
Forum|alt.badge.img+23
  • Contributor
  • 571 replies
  • April 27, 2021

Thanks. Unfortunately, the issue remains with tolerance set to 0.

Run a topology or an AreGapAndOverlapCleaner.

AoAO uses all the features, maybe you have gaps or unwanted overlaps.

Also run a GeometryValidator and fix any issues regarding geometry validity.


ebygomm
Influencer
Forum|alt.badge.img+44
  • Influencer
  • 3427 replies
  • April 27, 2021

Are you able to share the geometry of two polygons you are comparing that you think should show 100% overlap but don't?


helenwhiteley
Contributor
Forum|alt.badge.img
  • Author
  • Contributor
  • 5 replies
  • April 27, 2021

Are you able to share the geometry of two polygons you are comparing that you think should show 100% overlap but don't?

Have attempted to attach... Thanks


helenwhiteley
Contributor
Forum|alt.badge.img
  • Author
  • Contributor
  • 5 replies
  • April 27, 2021

Thanks. Unfortunately, the issue remains with tolerance set to 0.

Thanks, that definitely identified a lot of 'donuts', but, they are legitimate donuts. However, even with a non-donutty subset of data (see below) I don't get 100%


ebygomm
Influencer
Forum|alt.badge.img+44
  • Influencer
  • 3427 replies
  • Best Answer
  • April 28, 2021

Have attempted to attach... Thanks

The figure held in the Shape_Area field of the smaller polygon does not match the area of the polygon as calculated by FME (before doing any area on area overlaying). So if you are measuring the area after the area on area overlayer and then using this with the Shape_Area to calculate the percentage you are going to see strange results.

 

My suspicion is the differing area values are something to do with the fact that this small polygon is made up of arc segments.


helenwhiteley
Contributor
Forum|alt.badge.img
  • Author
  • Contributor
  • 5 replies
  • April 28, 2021

Have attempted to attach... Thanks

Amazing, thank you! I have used the Area Calculator to calculate an FMEArea field and used that in my percentage calculations and now have nice round 100%s. Why would the 2 area calculations (Shape_area and FMEArea) be different?


ebygomm
Influencer
Forum|alt.badge.img+44
  • Influencer
  • 3427 replies
  • April 28, 2021

Have attempted to attach... Thanks

Looks like that input polygon is actually not made up of arcs, but Bezier curves. These are stroked when read into FME which is probably introducing the area difference