Skip to main content
Solved

How to check for intersecting polygons

  • February 27, 2025
  • 2 replies
  • 34 views

tb09114
Supporter
Forum|alt.badge.img+22

I have a multitude of ring buffers and polygons for which I need to figure out what polygon intersects with what buffer. The task should be easy, but I am stuck here.

All data come from the same feature dataset in a file geodatabase (so the spatial reference system is by default the same), however, to be absolutely sure I projected all data before they get into the SpatialFilter to the same EPSG.

The settings for the SpatialFilter can be seen here

and to show that there are certainly intersecting areas and buffers that contain candidates I add the graphics view of the ‘Passed’ port and from the ‘Reprojected’ port of the Tester and the Reprojector.

The candidates are in red…

I did try an AreaOnAreaOverlayer, and that one finds overlaps but the request of merging the attribute data is unsuccessful. Meaning all the attributes are in the attribute table, but values from the buffers are not merged to the intersecting polygons, or the other way around. 
The list I create to check for what buffers the polygon intersects with is created, but when the list is not visible in the feature information view, and when I try to feed the list to a ListExploder the translation fails.

An Intersector also finds intersecting areas, creates the list, but does not add the attributes to the list as my settings implied. Instead of _buffer_id and TEN_Area I am only getting _direction in the list. The merging of attributes doesn’t work here either.

I tested the geometries and I only have polygons and donuts. Validating them reveals a few features that are not compliant to OGC, but it doesn’t matter if I continue with the features that passed the validator, the result is the same.
 

Best answer by liamfez

It looks like you are using Group Processing, do both the Filters and Candidates have those attributes? The way you currently have it set up, it will only check for intersections between buffers and polygons that both have the same value. So for example if the polygons do not have the _buffer_id and only the buffers do, then there will be no matches. This will likely be the same for the other transformers you said you tried, try turning off or adjusting your Group Processing.

For you ListExploder issues, the first thing I would check is that all features have the list. If there are features with no intersections entering that transformer and they have no list to explode that could cause the termination. I would recommend a Tester first to check the features for the presence of the list to ensure it exists.

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

2 replies

liamfez
Influencer
Forum|alt.badge.img+34
  • Influencer
  • Best Answer
  • February 27, 2025

It looks like you are using Group Processing, do both the Filters and Candidates have those attributes? The way you currently have it set up, it will only check for intersections between buffers and polygons that both have the same value. So for example if the polygons do not have the _buffer_id and only the buffers do, then there will be no matches. This will likely be the same for the other transformers you said you tried, try turning off or adjusting your Group Processing.

For you ListExploder issues, the first thing I would check is that all features have the list. If there are features with no intersections entering that transformer and they have no list to explode that could cause the termination. I would recommend a Tester first to check the features for the presence of the list to ensure it exists.


tb09114
Supporter
Forum|alt.badge.img+22
  • Author
  • Supporter
  • February 28, 2025

@liamfez thanks for your reply and the clarification about group processing. I tested before without grouping the data and the result was the same… 🙄Mr. Murphy seems to be my best friend… I tried it today again without grouping and today it works.


Reply


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