Dissolver

Dissolved polygon features with specified attributes.

Linear features that represent the portions of the input polygons which are not part of the output dissolved polygon.

Non-polygonal features are output via this port.

The input polygonal features may be partitioned into groups for dissolving by using the Group By parameter. If this parameter is not specified, then all input features are processed together. The Group By parameter enables a single factory to dissolve several sets of potentially overlapping polygons.

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

Parameter	Number of Processes
No Parallelism	1
Minimal	coresThe processor, or CPU, is the physical part of the computer that performs mathematical calculations. It is the most important part of a computer system. Traditional processors have only one core on the processor, meaning that at any given time, only one set of calculations is being performed. If a processor is dual-core, this means the single chip contains hardware for two processors, now called cores to distinguish them from the single chip, running simultaneously, side by side. (Source: http://www.ehow.com/facts_5730257_computer-core-processors_.html) / 2
Moderate	exact number of cores
Aggressive	cores x 1.5
Extreme	cores x 2

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.

No: This is the default behavior. Processing will only occur in this transformer once all input is present.

By Group: 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.

The attribute identified by this parameter will store the number of input polygons dissolved into an output polygon.

For example, if 3 input polygons dissolved into 1 polygon, then that 1 polygon would have this attribute set to 3.

When viewed in 2D (ignoring Z), a path (which may define the border of a polygon) may appear to be closed as shown in the left figure below. This same path, when viewed in 3D, may appear to be open as shown in the right figure below.

To specify how (and if) paths should be closed in 3D, select one of the listed modes.

Mode	Description	Example
Extend	The Curve is extended so that all vertices are left at their original location.
Average	Subsequent vertices that are not connected, but share an x and a y value are combined into one vertex, whose Z value is the average of the original two.
First Wins	Subsequent vertices that are not connected, but share an x and a y value are combined into one vertex, whose Z value is taken from the first encountered vertex.
Last Wins	Subsequent vertices that are not connected, but share an x and a y value are combined into one vertex, whose Z value is taken from the last encountered vertex.
Ignore	Z values are ignored. No change is made to the way the nodes are connected.

If set to No, no attributes from input polygons will be preserved, except those specified explicitly through the transformer parameters (for example, Group By, Attributes to Sum, List Name, etc.).

If set to Yes, all attributes from input polygons will be merged onto the resulting dissolved polygon. If there are conflicts, attributes from input polygons will be preserved in a two-step process:

• First, attributes from one of the polygons with the largest area will be copied onto the output polygon.
• Second, attributes from all other input polygons will be copied, without overwrite, onto the output polygon.

This parameter specifies the name of a list into which the attributes of the input features are stored. Attributes from a feature with the largest area are stored at the head of the list, and no order is defined for the remaining elements.

For example, if 3 input polygons are dissolved into 1 polygon, then that 1 polygon would have a list with 3 entries, each containing a set of attributes from one of the 3 input polygons.

Note: List Name will accumulate input attributes into the specified list regardless of the value of Accumulate Attributes from Input.

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.

Any attributes specified in this field will undergo statistical accumulation.

For example, if two input polygons have an attribute “salary” set to 30000 and 50000, then summing them would result in a “salary” of 80000 on the aggregate output.

Any attributes specified in this field will undergo statistical accumulation.

For example, if two input polygons have an attribute “salary” set to 30000 and 50000, then averaging them would result in a “salary” of 40000 on the aggregate output.

Any attributes specified in this field will undergo statistical accumulation.

For example, if two input polygons have an attribute “salary” set to 30000 and 50000, and the second polygon was 3 times larger than the first polygon, then the weighted average would be 45000.

Attributes to Average, Weighted by Area may produce non-numeric results if some input features have zero, or no area.

No: It is assumed that either input areas are not properly noded, or they have areal overlaps. Two areas that do not have an areal overlap can still be improperly noded if their boundaries overlap but do not have the same coordinates. In this case, a cleaning operation will precede the dissolve operation.

Yes: It is assumed that input areas are properly noded and contain no areal overlaps, so the cleaning operation will not be performed. If the input areas are not clean, this transformer may produce unexpected results.