Dissolver
Dissolves area features by removing common boundaries to create larger areas. Input attributes may be accumulated.
Aggregate input will be deaggregated by the transformer. Attributes on the aggregate feature will be propagated to its parts.
Because aggregates are deaggregated inside the Dissolver, it is possible that the number of output features will exceed the number of input features.
Dissolved polygons are formed when shared edges and interior edges between adjacent polygons are removed.
Example
The example below shows areas before and after a Dissolver transformer was used.
Configuration
Input Ports
This transformer accepts two-dimensional polygonal features, including donuts. These polygonal features are broadly referred to as polygons.
Output Ports
Dissolved polygon features with specified attributes.
Geometries and attributes that are left over after dissolving.
If the fme_remnant_type is INTERIOR_LINE, this remnant is a linear feature that represents the portions of the input polygons which were not part of the output dissolved polygon because the linear feature was either collinear with another feature, or was inside an overlapping region.
If the fme_remnant_type is UNUSED_DATA, this remnant is a feature that contains the remaining input data that was not part of the dissolved output. If the remnant feature has a geometry, this geometry was not used in the output. If the remnant feature does not have a geometry, this feature contains the attributes that were not used in the output.
Non-polygonal features are output via this port.
Parameters
Group By |
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. |
||||
Complete Groups |
Select the point in processing at which groups are processed:
Considerations for Using Group By
There are two typical reasons for using When Group Changes (Advanced) . The first is incoming data that is intended to be processed in groups (and is already so ordered). In this case, the structure dictates Group By usage - not performance considerations. The second possible reason is potential performance gains. Performance gains are most likely when the data is already sorted (or read using a SQL ORDER BY statement) since less work is required of FME. If the data needs ordering, it can be sorted in the workspace (though the added processing overhead may negate any gains). Sorting becomes more difficult according to the number of data streams. Multiple streams of data could be almost impossible to sort into the correct order, since all features matching a Group By value need to arrive before any features (of any feature type or dataset) belonging to the next group. In this case, using Group By with When All Features Received may be the equivalent and simpler approach. Note Multiple feature types and features from multiple datasets will not generally naturally occur in the correct order.
As with many scenarios, testing different approaches in your workspace with your data is the only definitive way to identify performance gains. |
Tolerance |
The minimum distance between geometries in 2D before they are considered equal, in ground units. If the tolerance is Automatic, a tolerance will be automatically computed based on the location of the input geometries. Additionally, a custom tolerance may be used. |
||||||||||||||||||
Connect Z Mode |
If applicable, select a method for handling z values. Connect Z Mode
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.
|
||||||||||||||||||
Aggregate Handling |
Choose how aggregate geometries are to be handled. Deaggregate: Decompose aggregates into their individual components. With this setting, the transformer might output more features than were given as inputs. Reject: Do not process aggregates and output them via the <Rejected> port. |
Accumulation Mode |
Specifies how attributes should be accumulated. If Drop Attributes is selected, all incoming attributes are removed from the features. Use Attributes From One Feature takes all attributes from the largest source feature. Merge Attributes merges all attributes from overlapping segments. If there are conflicts, attributes from input polygons will be preserved in a two-step process:
|
Attributes to Sum |
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. |
Attributes to Average |
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. |
Attributes to Average, Weighted by Area |
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. |
Generate List
When enabled, adds a list attribute 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.
List Name |
Enter a name for the list attribute. Note List attributes are not accessible from the output schema in FME Workbench unless they are first processed using a transformer that operates on them, such as ListExploder or ListConcatenator. Alternatively, AttributeExposer can be used.
|
Add To List |
All Attributes: Every attribute from all input features that created an output feature will be added to the list specified in List Name. Selected Attributes: Only the attributes specified in the Selected Attributes parameter will be added to the list specified in List Name. |
Selected Attributes |
The attributes to be added to the list when Add To List is Selected Attributes. |
Dissolve Count |
Name the attribute to contain 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. |
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.
Defining Values
There are several ways to define a value for use in a Transformer. The simplest is to simply type in a value or string, which can include functions of various types such as attribute references, math and string functions, and workspace parameters. There are a number of tools and shortcuts that can assist in constructing values, generally available from the drop-down context menu adjacent to the value field.
Using the Text Editor
The Text Editor provides a convenient way to construct text strings (including regular expressions) from various data sources, such as attributes, parameters, and constants, where the result is used directly inside a parameter.
Using the Arithmetic Editor
The Arithmetic Editor provides a convenient way to construct math expressions from various data sources, such as attributes, parameters, and feature functions, where the result is used directly inside a parameter.
Conditional Values
Set values depending on one or more test conditions that either pass or fail.
Parameter Condition Definition Dialog
Content
Expressions and strings can include a number of functions, characters, parameters, and more.
When setting values - whether entered directly in a parameter or constructed using one of the editors - strings and expressions containing String, Math, Date/Time or FME Feature Functions will have those functions evaluated. Therefore, the names of these functions (in the form @<function_name>) should not be used as literal string values.
These functions manipulate and format strings. | |
Special Characters |
A set of control characters is available in the Text Editor. |
Math functions are available in both editors. | |
Date/Time Functions | Date and time functions are available in the Text Editor. |
These operators are available in the Arithmetic Editor. | |
These return primarily feature-specific values. | |
FME and workspace-specific parameters may be used. | |
Creating and Modifying User Parameters | Create your own editable parameters. |
Dialog Options - Tables
Transformers with table-style parameters have additional tools for populating and manipulating values.
Row Reordering
|
Enabled once you have clicked on a row item. Choices include:
|
Cut, Copy, and Paste
|
Enabled once you have clicked on a row item. Choices include:
Cut, copy, and paste may be used within a transformer, or between transformers. |
Filter
|
Start typing a string, and the matrix will only display rows matching those characters. Searches all columns. This only affects the display of attributes within the transformer - it does not alter which attributes are output. |
Import
|
Import populates the table with a set of new attributes read from a dataset. Specific application varies between transformers. |
Reset/Refresh
|
Generally resets the table to its initial state, and may provide additional options to remove invalid entries. Behavior varies between transformers. |
Note: Not all tools are available in all transformers.
FME Community
The FME Community is the place for demos, how-tos, articles, FAQs, and more. Get answers to your questions, learn from other users, and suggest, vote, and comment on new features.
Search for all results about the Dissolver on the FME Community.
Keywords: aggregate aggregation "technology preview"