AreaAmalgamator

Polygonal geometries, including donuts. The polygonal geometries may overlap and share boundaries. However, each geometry should be valid (that is, not self-intersecting or non-planar).

Amalgams computed from input polygonal geometries.

Input polygonal geometries that are not touched by valid triangle connectors.

Holes in the amalgams whose areas exceed the Minimum Hole Area parameter.

Triangles that form the valid connectors joining input polygonal geometries.

Non-polygonal input. Occasionally, if an unexpected condition is met, some invalid intermediate results will be posted to this port.

By specifying one or more Group By attributes, the input polygonal features will be partitioned into groups and the amalgamation process will be executed separately on each group. Within each group, all features will have the same values for the selected Group By attributes.

If no Group By attributes are selected, a single group will be formed containing all input polygonal features. By default, no Group By attributes are selected.

Process At End (Blocking): This is the default behavior. Processing will only occur in this transformer once all input is present.

Process When Group Changes (Advanced): This transformer will process input groups in order. Changes of the value of the Group By parameter on the input stream will trigger processing on the currently accumulating group. This may improve overall speed (particularly with multiple, equally-sized groups), but could cause undesired behavior if input groups are not truly ordered.

Considerations for Using Group By

There are two typical reasons for using Process 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 Process At End (Blocking) 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.

This parameter controls the mode of amalgamation. The AreaAmalgamator is conceptually a binary operator that causes two nearby geometrical details to connect together. However, two geometrical details may be on the same geometry. Imagine two peninsulas protruding from the same coast line, or two different geometries, such as two neighboring islands. Therefore, a number of options are provided here to accommodate the two conceptual models:

• Self Amalgamation: This mode amalgamates a polygonal geometry against itself. It would handle the two peninsulas case, but not the two neighboring islands case.
• Binary Amalgamation (default): This mode amalgamates different polygonal geometries. It would handle the two neighboring islands case, but not the two peninsulas case.
• Self, Binary Amalgamation: This mode combines the Self Amalgamation and the Binary Amalgamation. It would handle both the two peninsulas case and the two neighboring islands case.

Input	Output: Amalgamated
	Self Amalgamation
	Binary Amalgamation
	Self, Binary Amalgamation

This parameter controls whether input polygonal features are dissolved up front. The default value is Yes.

• Yes: This value dissolves input polygonal features. The AreaAmalgamator was designed with the assumption that input features do not overlap. This value enforces that assumption. Dissolving input up front also remedies input polygonal features that may not be overlapping, but whose shared boundaries become overlapping after the densification step due to limited precision. The overlapping due to limited precision could reduce the performance of the AreaAmalgamator.
• No: This value is meant for advanced users who want finer control of the AreaAmalgamator. Some users would rather not dissolve the input to improve performance because in some cases, not dissolving the input will not cause undesirable side effects.

Overlapping Input	Dissolve Input: Yes Amalgamation Mode: Binary	Dissolve Input: No Amalgamation Mode: Binary
Explanation	The input dissolves into one polygon, thus the Binary mode causes the one polygon not to amalgamate.	The input is not dissolved, thus the Binary mode causes the two input features to amalgamate, but because overlapping features were not dissolved, a hole results in the middle of the amalgam.

Overlapping Input	Dissolve Input: Yes Amalgamation Mode: Self	Dissolve Input: No Amalgamation Mode: Self
Explanation	The input dissolves into one polygon, thus the Self mode causes the one polygon to amalgamate.	The input is not dissolved, thus the Self mode causes the two input features not to amalgamate.

This parameter controls the widths of triangles that form the connectors. The width of the triangle is the width of its base, which is incident on the boundary of an input polygonal geometry (see figure below). The larger its value, the wider the triangles will be.

In terms of triangle count, decreasing this value generally increases (and will not decrease) the number of triangles generated. In terms of performance, having this value set too low could cause significant slowdowns. In terms of the appearance of the triangle connectors, having this value set too high could result in coarse looking connectors that appear skewed in shape.

Tip: Set the value of this parameter as high as possible, given that the amalgamated output still looks good to the eye.

More rigorously, after the input polygonal geometries are dissolved, extra vertices are added through a densification process. The densification interval controls the widths of triangles created. This parameter specifies the length of the densification interval.

This parameter controls the lengths of triangles that form the connectors. The length of the triangle is defined by the length of its longest side (see figure below). This value should not be less than the Maximum Triangle Width. The larger its value, the farther apart two input polygons can be and still be connected together by triangles in the formation of amalgams.

In terms of triangle count, decreasing this value generally decreases (and will not increase) the number of triangles generated. Changes in this value are not expected to have a significant impact on performance. In terms of the appearance of the triangle connectors, having this value set too high could result in the input polygons being output as a single amalgam.

This parameter controls which holes should be eliminated from the amalgams. The larger its value, the larger the remaining holes will be. In terms of hole count, decreasing this value generally increases (and will not decrease) the number of holes remaining in the amalgams.

This parameter specifies the name of a unique identifier for the amalgams. If specified, each amalgam will receive an ID value that is unique across groups. All triangles and holes contained in an amalgam will receive the same ID as that amalgam.

Enter a name for the list attribute.

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. Alternatively, AttributeExposer can be used.

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.

The attributes to be added to the list when Add To List is Selected Attributes.

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.

Text Editor

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.

Arithmetic Editor

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.

Content Types

String Functions	These functions manipulate and format strings.
Special Characters	A set of control characters is available in the Text Editor.
Math Functions	Math functions are available in both editors.
Date/Time Functions	Date and time functions are available in the Text Editor.
Math Operators	These operators are available in the Arithmetic Editor.
FME Feature Functions	These return primarily feature-specific values.
FME Parameters	FME and workspace-specific parameters may be used.
Creating and Modifying User Parameters	Create your own editable parameters.

Note: Not all tools are available in all transformers.