Hi, I’ve got two polygon datasets A and B, and I’d like to identify which polygons from dataset B that touch polygons from dataset A, but only edge to edge contact count as touch. How can I get the ideal result or exclude vertex touches?
Solved
How to exclude vertex touches from OGC-touches while using SpatialRelator?
+3- Contributor
Best answer by takashi
Hi
Alternatively, if you set Yes to the Calculate Cardinality of Intersections parameter in SpatialRelator, the resulting features will have these list members which indicate the number of intersections by their shape - point, line, and area.
- _relationships{}.card_point
- _relstionships{}.card_line
- _relationships{}.card_area
After exploding the list with ListExploder, you can then filter them by the condition 0 < card_line to select B (Supplier) features that share a boundary line with an A (Requestor) feature.
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.
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.
+43- Influencer
Hi
I think you could use the chopper to generate verticies. Then buffer. Then use buffer to clip the original set of polygons.
Then run the relate with edge. So you can use the verticies to Cut out the portion of the polygon that touches at one point (verticy). With that removed, the remainder will be edge.
Hope that helps.
- Best Answer
Hi
Alternatively, if you set Yes to the Calculate Cardinality of Intersections parameter in SpatialRelator, the resulting features will have these list members which indicate the number of intersections by their shape - point, line, and area.
- _relationships{}.card_point
- _relstionships{}.card_line
- _relationships{}.card_area
After exploding the list with ListExploder, you can then filter them by the condition 0 < card_line to select B (Supplier) features that share a boundary line with an A (Requestor) feature.
Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
+43- Influencer
Oh that is a much more elegant solution
At your rest service ^B
+45- Influencer
You can also use a spatial predicate in the Spatial Filter to differentiate between touch at a point and share an edge
+43- Influencer
Always learning. I love it. Thanks
+
One question two things I learned. Thank you for sharing.
+3- Contributor
Hi
Alternatively, if you set Yes to the Calculate Cardinality of Intersections parameter in SpatialRelator, the resulting features will have these list members which indicate the number of intersections by their shape - point, line, and area.
- _relationships{}.card_point
- _relstionships{}.card_line
- _relationships{}.card_area
After exploding the list with ListExploder, you can then filter them by the condition 0 < card_line to select B (Supplier) features that share a boundary line with an A (Requestor) feature.
It works! And is it possible to set tolerance on this paramerter, some polygons they do share a boundary line but card_line ouput 0 while card_point outputting 1.
+3- Contributor
You can also use a spatial predicate in the Spatial Filter to differentiate between touch at a point and share an edge
I see, but can I set a tolerance on this one?
There is no option to set tolerance for determining spatial relations with SpatialRelator or SpatialFilter. If there could be tiny gaps or overlaps between adjacent polygons and you would like to ignore them when determining spatial relations, consider using an appropriate transformer - e.g. Snapper (Snapping Type: Segment Snapping) or AreaGapAndOverlapCleaner beforehand to resolve the gaps and overlaps.
Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?