Skip to main content
Solved

AreaOnAreaOverlay not working as expected

  • December 13, 2012
  • 7 replies
  • 21 views
B
Forum|alt.badge.img
Hello,

 

 

I'm trying to calculate the amount of overlays of features in a geodatabase. Im using the AreaOnAreaOverlay transformer for this. However, what comes out of the transformer is quite strange. The amount of input features is 13, yet, the _overlays attribute gives values upto 24. Additionally, it fills in gaps (holes) that aren't part of the shape but are surrounded by the shape. 

 

 

In the attached file I provided the workspace and files I'm working with. 

 

ftp://ftp.safe.com/incoming/FME_AOA_error.zip

 

 

I would really appreciate the assistance, I don't quite understand how this is happening. 

Best answer by boyen

I've contacted the help desk, apparently FME 2012 has a FILEGDB reader that does work while the GEODATABASE_FILE reader of 2011 doesn't.  
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.

7 replies

B
Forum|alt.badge.img
  • boyen
  • Author
  • December 13, 2012
Oh, I'm sorry. I'm using FME desktop 11 32bit on windows vista, if it makes any difference. 
redgeographics
Celebrity
Forum|alt.badge.img+62
I'm having some trouble downloading your file, so it's hard to come up with an answer. If 2 features overlap, the AreaOnAreaOverlayer will cut them up into the overlapping parts and create an _overlaps attribute per part that notes how many parts exist on that particular spot.

 

 

Off the top of my head, the only way to get that kind of _overlaps numbers with only 13 input features is if they're either large aggregates or self intersecting ones. But again, I'd have to see your actual data to give a defiitive answer.
FME rocks! \m/
B
Forum|alt.badge.img
  • boyen
  • Author
  • December 14, 2012
Hello RedGeographics,

 

 

Thanks for your reply; another attempt at uploading the data: https://sendit.wur.nl/Download.aspx?id=7266daf4-36d5-4bc2-bfc7-e768a6737545
B
Forum|alt.badge.img
  • boyen
  • Author
  • December 14, 2012
It seems like the previous file already reached the limit on downloads.

 

 

https://sendit.wur.nl/Download.aspx?id=79d09597-91b4-4a5a-b225-f1c0d5cb54e1

 

 

 

takashi
Celebrity
  • takashiCelebrity
  • December 14, 2012
Hi,

 

  I saw your workspace. Probably, you should check "Group by" parameter of Aggregator. If you erase "_overlaps" in the parameter box, what will happen?  
Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
B
Forum|alt.badge.img
  • boyen
  • Author
  • December 14, 2012
Hello Takeshi,

 

That doesn't quite fix it. Holes are still filled with overlaps. Even when the aggregator is entirely removed (or a visualizer is connected prior to the aggregator) the problem persists. Thanks for helping though!
B
Forum|alt.badge.img
  • boyen
  • Author
  • Best Answer
  • December 19, 2012
I've contacted the help desk, apparently FME 2012 has a FILEGDB reader that does work while the GEODATABASE_FILE reader of 2011 doesn't.  

Community Stats

32,154
Posts
122,043
Replies
39,812
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.