Skip to main content
Solved

How do I exclude records in a feature class that are contained within another feature class?

kmc5678
Contributor
Forum|alt.badge.img+2

I have a workspace where permit data is joined to GIS data through a series of joins. That data is then written into separate feature classes. The 3 datasets in order are as follows BIN Join, BBL Join, a spatial join using the Point On Area Overlayer transformer. After all of these joins happen I'm dumping any remaining unjoined records into a point feature class called Fallout Points. However all of the records from the spatial join are ending up in the Fallout Points layer. How do I exclude them (or delete them after)?

Screenshot 2023-07-25 160150Screenshot 2023-07-25 160233Screenshot 2023-07-25 160254

Best answer by daveatsafe

daveatsafe wrote:

Please post a new screen shot of the workspace, with the number of features displayed. This will help me see where the features are ending up in the workspace.

Please add a Tester on the Point output of the PointOnAreaOverlayer, and test for _overlaps = 0. This will find all the points that did not fall inside a polygon.

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

6 replies

daveatsafe
Safer
Forum|alt.badge.img+19
  • daveatsafeSafer
  • Safer
  • July 31, 2023

Hi @kmc5678​,

Please try setting the PointOnAreaOverlayer parameter Areas First to No. This will accept all area features, regardless of the input feature order. The present setting will force the transformer to only test the area features that reach it before the point feature does.

kmc5678
Contributor
Forum|alt.badge.img+2
  • kmc5678Contributor
  • Author
  • Contributor
  • August 1, 2023

Thanks for your response @daveatsafe​ . However, changing the Areas First setting to No did not result in the exclusion of the spatially joined records from the Fallout Points Layer.

daveatsafe
Safer
Forum|alt.badge.img+19
  • daveatsafeSafer
  • Safer
  • August 1, 2023
kmc5678 wrote:

Thanks for your response @daveatsafe​ . However, changing the Areas First setting to No did not result in the exclusion of the spatially joined records from the Fallout Points Layer.

Please post a new screen shot of the workspace, with the number of features displayed. This will help me see where the features are ending up in the workspace.

kmc5678
Contributor
Forum|alt.badge.img+2
  • kmc5678Contributor
  • Author
  • Contributor
  • August 2, 2023
daveatsafe wrote:

Please post a new screen shot of the workspace, with the number of features displayed. This will help me see where the features are ending up in the workspace.

Sure no problem. I appreciate the assistance. I was also thinking of maybe producing a list of the Spatially Joined features and then deleting them from the Fallout Points using one of the Unique Identifiers as a final step as a work around. Screenshot 2023-08-02 125216

daveatsafe
Safer
Forum|alt.badge.img+19
  • daveatsafeSafer
  • Safer
  • Best Answer
  • August 2, 2023
daveatsafe wrote:

Please post a new screen shot of the workspace, with the number of features displayed. This will help me see where the features are ending up in the workspace.

Please add a Tester on the Point output of the PointOnAreaOverlayer, and test for _overlaps = 0. This will find all the points that did not fall inside a polygon.

kmc5678
Contributor
Forum|alt.badge.img+2
  • kmc5678Contributor
  • Author
  • Contributor
  • August 3, 2023
daveatsafe wrote:

Please post a new screen shot of the workspace, with the number of features displayed. This will help me see where the features are ending up in the workspace.

Thanks so much @daveatsafe (Safer)​, the Tester transformer was exactly what I was looking for and I was able to replace the attribute filter I was using for a similar step in the process.

Reply


Helpful Members This Week

Community Stats

31,182
Posts
118,183
Replies
38,791
Members

Latest FME

Terms & ConditionsCookie settings

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
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.