Computes intersections between all input features, breaking lines and polygons wherever an intersection occurs. In addition, all overlapping segments are reduced to one segment before being output.
Output Ports
Intersected
The intersected features are output to this port. If the List Name parameter was specified, these features will have an attribute containing their number of overlapping input features. They will also have all attributes of the original features. If the input is an aggregate with one valid geometry part and one invalid geometry part, the geometry will be deaggregated. The valid part will output through the Intersected port, and the invalid part will output through the <Rejected> port.
Node
The locations of topologically significant nodes are represented by point features and are output to this port. The transformer parameters modify which attributes are included on the output features.
<Rejected>
All null, surface, solid, raster, and point cloud features are output through this port. If the input is an aggregate with one valid geometry part and one invalid geometry part, the geometry will be deaggregated. The valid part will output through the Intersected port, and the invalid part will output through the <Rejected> port.
Parameters
Group By
If you select Group By attributes, only those features with the same Group By attribute values will be processed. If you do not select Group By attributes, then all features will be processed.
Parallel Processing Level
Note: How parallel processing works with FME: see About Parallel Processing for detailed information.
This parameter determines whether or not the transformer should perform the work across parallel processes. If it is enabled, a process will be launched for each group specified by the Group By parameter.
Parallel Processing Levels
For example, on a quad-core machine, minimal parallelism will result in two simultaneous FME processes. Extreme parallelism on an 8-core machine would result in 16 simultaneous processes.
You can experiment with this feature and view the information in the Windows Task Manager and the Workbench Log window.
Input is Ordered by Group
Yes: This transformer will process input groups in order. Changes on the value of the Group By parameter on the input stream will trigger batch processing on the currently accumulating group. This will improve overall speed if groups are large/complex, but could cause undesired behavior if input groups are not truly ordered.
No: This is the default behavior. Processing will only occur in this transformer once all input is present.
Duplicate Nodes at Each Elevation
The creation of nodes can be calculated in 3D, if requested. Constructing nodes in 3D would mean that line segments would only share a node if they shared the same Z value at the point they intersected. Constructing nodes in 2D would mean that all intersecting segments would share a common node, regardless of their respective Z values.
Consider, for example, a situation where two lines (that crossed) represented roads, where one road was an overpass above the other road. Suppose these two lines had differing elevations. If you constructed nodes in 3D, these two roads would not be linked to the same node where they crossed. Two nodes would be produced at the crossing point – each one with a different Z value. If you constructed nodes in 2D, these lines would both link to a common node, which would be present at the location where they crossed. In either the 2D or 3D case, the full dimensionality of the input is preserved in the output – 3D features are never converted to 2D. The 2D or 3D choice only indicates how the nodes are created and which lines are linked to them; it does not affect the dimension of the features that are output.
If the Duplicate Nodes at Each Elevation parameter is set to Yes, then whenever 3D lines intersect at differing heights, two 2D nodes will be output via the Node port. Each node will have the same x and y coordinates, but a different node number.
If the Duplicate Nodes at Each Elevation parameter is set to No, then whenever 3D lines intersect at differing heights, a single 2D node is output at the intersection point.
Overlap Count Attribute
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.
Segment Count Attribute
The Segment Count Attribute parameter, if specified, names an attribute that will be added by the transformer, containing the number of segments into which the segment’s original feature was divided.
If an input feature was broken into n output segments, each of those segments will have an attribute named <attribute name> which has a value of n.
Separate Collinear Segments
This parameter causes overlapping segments not to be merged into a single segment: one copy is output for each original feature sharing the segment. Each such segment will have the respective original feature’s attributes as its main attributes, and attributes from all other collinear features will be added as a list attribute, if the list name was supplied.
When a coverage of polygons is input, the set of topologically significant lines which form their boundaries is output.
Split Self-Intersecting Features
If the Split Self-Intersecting Features parameter is set to Yes, self-intersections in the input features are removed by splitting the feature.
No feature-to-feature comparisons are made. In this case, the value set to the Overlap Count Attribute will be the number of features that result from removing self-intersections. If the feature did not self-intersect, the attribute will be set to 1.
If the segment had several overlapping input features, the attributes of each of the input features will be added to the feature in the list identified by List Name, if one was specified. In any case, each output feature is also assigned the attributes of one of its original input features. This transformer also adds a "direction" attribute for each attribute resulting from the List Name parameter, labelling it as same if the geometry is oriented in the same direction, and opposite if the geometry is oriented in the opposite direction to the current geometry.
Accumulation Mode
Specifies how attributes should be accumulated. If Drop Attributes is selected, all incoming attributes are removed from the features. Merge Attributes merges all attributes from overlapping segments. Get Attributes From One Representative Feature takes all attributes from one representative feature.
Prefix
When Separate Collinear Segments is Yes, and Accumulation Mode is Merge Attributes, this value prefixes all incoming attributes on collinear segments. It does not affect node output.
Generate List
Allows you to specify a List Name.
List Name
If specified, a list of the attributes of each line that overlapped an output segment is made. This allows later inspection of overlapping segment attributes.
Note: List attributes are not accessible from the output schema in Workbench unless they are first processed using a transformer that operates on them, such as ListExploder or ListConcatenator. All list attribute transformers are displayed in the Contents pane of the Transformer Help under Lists. Alternatively, AttributeExposer can be used.
Example
Using the Intersector and ListConcatenator to Solve Problems
What if you have linear street centerlines and, at each intersection point, you'd like to know which streets come together? The output should be a set of points, each with a single string attribute containing a comma-separated set of the street names.
You can solve this by setting up a workspace that routes all the street centerlines into an Intersector. Adjust the parameters of the Intersector to supply a list name; for example, all_streets.
Let's assume that the input street lines had an attribute called NAME. Now, among other things, the Node output of the Intersector will have an unqualified list on it called all_streets{}.NAME. This list will hold the names of all the streets that intersect at each particular point (or Node) that is output.
To turn the list of NAMEs into a single string, add a ListConcatenator transformer and run the Node features into it. Then set up the ListConcatenator's parameters so that it would put the contents of the all_streets{}.NAME list together, separated by commas, into the "result" attribute. Then route the output of the ListConcatenator to an output file, and ensure that the "result" attribute was routed to an attribute in the output. After running the translation, you will have the desired result.
Note that you could also access the individual street names by "exposing" some elements of your list (by right clicking on the attribute unqualified list name (in our example, "all_streets{}.NAME") and saying "Expose Elements", and entering the number of elements to expose. You'd then have to do something with those elements in your translation. (The disadvantage of this approach is that you need to know ahead of time how many list elements you want to work with -- so if 3 streets intersect at the same node and you only set yourself up to handle two, you'd have to do something special to handle that.)
Editing Transformer Parameters
Using a set of menu options, transformer parameters can be assigned by referencing other elements in the workspace. More advanced functions, such as an advanced editor and an arithmetic editor, are also available in some transformers. To access a menu of these options, click 
beside the applicable parameter. For more information, see Transformer Parameter Menu Options.
Transformer Categories
Search FME Knowledge Center
Search for samples and information about this transformer on the FME Knowledge Center.