AnchoredSnapper

Features that may have Candidate features snapped to them. Arcs are snapped as linear features, and ellipses are snapped as polygonal features.

Features that may be snapped to Anchor features. Arcs are snapped as linear features, and ellipses are snapped as polygonal features.

Candidates whose geometry is changed by the transformer.

Candidates that leave the transformer without being changed.

• If a line or area feature snaps down to a single location, it will be output as a Point geometry, through the Collapsed port.
• If an Aggregate, MultiArea, or MultiCurve geometry has any parts snap down to a single location, a Point geometry for each part will be bundled up into a MultiPoint geometry and output through the Collapsed port. The remaining parts which did not snap down to a single location (if any) will be output as a group through the Snapped port.

The anchors that were used during snapping. If a candidate was snapped to a point along the segment of an anchor, a new node is inserted into the anchor’s geometry.

If you select Group By attributes, only those features with the same Group By attribute values will be snapped together.

When All Features Received: This is the default behavior. Processing will only occur in this transformer once all input is present.

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 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.

When Snapping Type is End Point Snapping:

• The transformer snaps endpoints of features that enter via the Candidate port to endpoints of features that enter via the Anchor port. Anchor features are not output.
• Point features can be used as Anchor or Candidate features, and Candidate points will be snapped together (or to a linear base feature) as well.
• The transformer will not alter area features.

When Snapping Type is Vertex Snapping:

• The transformer snaps vertices of features that enter via the Candidate port to vertices of features that enter via the Anchor port. Anchor features are not output.
• Point features can be used as Anchor or Candidate features, and Candidate points will be snapped together (or to a linear Anchor feature) as well.
• The transformer will alter area features.

When this parameter is set to Segment Snapping:

• The transformer snaps vertices of curves or points that enter via the Candidate port to lines of features that enter via the Anchor port, if their distances are within the specified tolerance. Anchor features are not output.
• The transformer snaps vertices of Candidate segments to Anchor segments if their distances are within the specified tolerance at any point along the segment.
• Candidate segments which cross Anchor segments will have new vertices introduced at the point of intersection, but the Candidate segments will not be split.
• Segment snapping may cause duplicate points, where segments have degenerated to a point.
• Area features are altered by this operation as its vertices and segments are snapped.

Snapping Distance specifies the distance, in ground units, that the snapping occurs between features.

When Snapping Type is Segment Snapping, this transformer performs data cleaning that is meant to improve the robustness of the results when they are used in other algorithms by ensuring that no two vertices in the snapped output are within tolerance of each other.

If Tolerance is set to Automatic, a tolerance will automatically be calculated for the cleaning operation, based on the size of the inputs. Otherwise, a custom tolerance may be used.

This parameter applies only when the end point of a feature is being snapped.

• NEVER: the endpoint of a line is moved when it is snapped and no additional vertex is added.
• ALWAYS: the original end point (start point) of the line becomes the second from the end (start) and a new vertex is added to complete the snap.
• FORWARD_ONLY: a new vertex is added only when doing so creates an angle greater than 90 degrees with the original line segment. In this case, if adding the vertex would cause a less than 90-degree angle, the old end point is still moved.

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.