Solved
Intersector - Overlap issue
I have a street table on which I am executing an Intersector to find out the intersecting nodes. I want to root out the end points and on doing a search in FMEPedia found out that if I filter for Overlap greater than or equal to 2, I will get my intersecting nodes. But, my overlap attributes are all coming up as blank. What does this mean? Am I doing something wrong here.
Best answer by takashi
Hi,
There may be several ways, I would use the SpatialRelator transformer.
After intersecting, input nodes to BASE, segments to CANDIDATE port separately, and select 'TOUCHES' for 'Test to Perform' parameter of the SpatialRelator.
Each output feature (node) will be added the related candidates (segments) count attribute (named _related_candidates by default), which will contain the number of touched segments in this case. So, then you can filter output nodes by testing this attribute value.
Takashi
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.
Hi,
The transformer description says "The Overlap Count Attribute parameter names an attribute that will be added by the transformer, containing the number of collinear input lines that overlapped the output segment".
I suppose this attribute will be added to only output segments (lines).
Takashi
Hi Takashi,
Thanks for responding. What you are saying looks correct as that is what I am seeing. Then how can I eliminate those end points and get only the intersection points?
- Best Answer
Hi,
There may be several ways, I would use the SpatialRelator transformer.
After intersecting, input nodes to BASE, segments to CANDIDATE port separately, and select 'TOUCHES' for 'Test to Perform' parameter of the SpatialRelator.
Each output feature (node) will be added the related candidates (segments) count attribute (named _related_candidates by default), which will contain the number of touched segments in this case. So, then you can filter output nodes by testing this attribute value.
Takashi
Worked great for me as well, Takashi! I just set the Tester after the SpatialRelator to pass through anything with 3 or greater touches. A point with 2 line segment touches only represents a segment end/begin point along a line, but a point with 3 line segment touches is a true intersection. Thanks for posting this!