Skip to main content
  • EN
The AreaOnAreaOverlayer is a great little tool but I have 2 issues when using it. You may know of a better way to do this.

 

 

Issue 1: I want my output to have the fields from all layers used. Similar to a join in ArcGIS. I can’t tell if I’m limiting that because my existing output file may not have all of the fields, so they are possibly being ignored. Could it be that I’m limiting it? Should the AreaOnAreaOverlayer automatically output all fields? (In my example below I’ve exploded the data to try and resolve my issue).

 

 

Issue 2: This concerns me a little. Do you know if you can do multiple AreaOnAreaOverlayer transformers (Like I illustrate below) in an FME job? I have to make 3 comparisons as it moves through the process. FYI: All of these layers are polygons. Here’s a description of what is shown in the illustration below (Each number is represented in the picture I've posted of the FME job).

 

  1. The first AreaOnAreaOverlayer comparison is Leases against Boundary Units. (NOTE: IT PERFORMS THIS COMPARISON)
  2. The second AreaOnAreaOverlayer comparison is the Leases/Boundary Units output from the first AreaOnAreaOverlayer against Rig Schedule Units. (NOTE: IT DOES NOT PERFORM THIS COMPARISON)
  3. The third AreaOnAreaOverlayer comparison is the Leases/Boundary Units/Rig Schedule Units output from the second AreaOnAreaOverlayer against Thermal Windows. (NOTE: IT DOES NOT PERFORM THIS COMPARISON)
As it moves through and reaches the “Test output to file geodatabase” the output should be split based on the 3 overlays along with ALL of the fields from the 4 layers used. Directly below is a screenshot of my FME job showing the connections and a diagram showing exactly what it is trying to achieve.

 

 

Thanks to all of you for your help. If anyone knows of a better way to achieve this I would have no problem giving it a try. I'm open to your suggestions.

 

 

Thanks,

 

Tony

 

 

My FME job:

 

 

 

 

This diagram I created really explains the output I’m after:

 

 

 

Hi,

 

 

Have yuou tried the clipper?
AoA should work.

 

 

I use input attribute like fme_featuretype and overlaps attribute, and when needed the list to filter whatever  i need.

 

(If type of cardinality is an issue i often use an intersector followed by a spatialrelator. In fact today i had a AoA failure due to (most likely) messed up input (spatialindex or wathever), made me go theintersector route and remerging trough GUID's)

 

 

Reasons for total failure are always down to inputdata (afaik ;)).

 

Are both in the same projection? Are untis the same, often seen with autocad files, mm instead of meters for instance.( that is, can they spatialy relate at all?)

 

Are both feeding area's? (rather then polylines)

 

 

Reasons for partial failure, that it is unexpected ouput, can be donuts, aggregates, collections.

 

 

Though i cannot see failure by your posted picture. Maybe the filtering is not valid?

 

Only overlap bits get all attriubtes inherited after all.

 

 

 

 

All lease objects are to be passed.

 

 

U can AoA just like u did.

 

Just keep the parts by testing for existance of fme_feature_type = Lease attribute and overlaps attribute (>0 or 1, depends on input). of layers.

 

Of course u need to expose this attribute on the Lease reader.

 

 

I think u can even get away with just one AoA with all the area's entered at once.

 

I agree the AOAO should work with all inputs, as usual many way to achieve the same ....
Gio:

 

 

Turns out you were on to 3 issues I was unknowingly encountering.

 

  1. The projection was causing a major issue on one feature class. I did not realize it was the only layer that is projected in our database. 
  2. And your suggestion to do it all in one AreaOverlayer was genius. I don't know why I didn't think about it, I guess I wasn't thinking outside the box.
  3. Your best suggestion led me to another great tweak to the job. I exposed fme_basename and tested for LEVEL, passing on only the matches which deleted the non-LEVEL portions of polygon.
Excellent advice!!! Thank you! Thank you! Thank you!

 

 

Also thanks to ETLS-Itay for his advice too!

Reply


Community Stats

30,108
Posts
114,295
Replies
37,743
Members
Terms & ConditionsCookie settings
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.