In this example, several attributes of the input features are modified:

• GlobalID is renamed, changing the case of the attribute name. Several address attributes are renamed as well.
• A new attribute “FULLNAME” is created, concatenating the values of two other attributes
• Several unwanted attributes are removed
• X and Y attributes are created and values are assigned by extracting geometry with an FME function
• “UPDATEDBY” is created and set to the fixed value “Smith”.
• All other attributes pass through untouched

The altered attributes are reflected in the transformer.

Adjacent Feature Attributes are accessed under Advanced: Attribute Value Handling. When turned on, you can specify a number of features preceding and following the current feature to reference in calculating new values.

Suppose we are given the dataset below:

If the Number of Prior Features and Number of Subsequent Features parameters are both set to 2, then when the first feature is read, the AttributeManager has access to the following features:

Note that some attributes are missing because no features exist prior to the first feature.

After the second feature is read, the window of prior and subsequent features available to AttributeManager shifts to produce the following:

This statement would calculate the average latitude of the two preceding features:

Calculations referencing adjacent features can be created in the Arithmetic Editor and the Text Editor. These editors will list the attributes of the currently processed feature first, then the prior features, then the subsequent features.

This transformer accepts any feature.

Features with the created and modified attributes.

When an AttributeManager transformer is connected and opened for the first time, this matrix is automatically populated with the incoming features’ attributes as they currently exist. It will also adjust dynamically to reflect upstream attribute changes in the workspace.

By default, the Actions are set to “Do Nothing” and pass through the features unaltered. As you make changes to individual items, FME interprets the appropriate Action based on your inputs. Action can be overridden manually, but you generally should not need to adjust it.

Expanding the Advanced section provides access to the attributes of adjacent features that can be used to define values. While this section may appear complex, most users will rarely need this functionality.

Check “Enable Adjacent Feature Attributes” to use this feature.

You can now set an attribute value (in the Attribute Actions matrix) based on the attributes of features prior or subsequent to the current feature by referencing them as follows:

• Attributes of prior features are referenced as feature[-1].AttrName, feature[-2].AttrName, etc.
• Attributes of subsequent features are referenced as feature[+1].AttrName, feature[+2].AttrName, etc.
• Attributes of the currently processed feature are accessed directly without a prefix, such as AttrName.

When retrieving the value of a prior feature, any changes made by the AttributeManager to that feature will take effect.

Number of Prior Features

This parameter specifies the maximum number of prior features that can be referenced by the AttributeManager. If Multiple Feature Attribute Support is enabled, this must be a value from 0 to 100. As additional features must be read for each feature processed, defining only the maximum number of features needed to be retrieved will improve performance.

Number of Subsequent Features

This parameter specifies the maximum number of subsequent features that can be referenced by the AttributeManager. If Multiple Feature Attribute Support is enabled, this must be a value from 0 to 100. As additional features must be read for each feature processed, defining only the maximum number of features needed to be retrieved will improve performance.

Substitute Missing, Null, and Empty by

This parameter specifies the desired behavior when the referenced attribute does not exist, has a null value, or has an empty string value.

Such attributes can be thought of as unresolved attributes. For example, since there are no features prior to the first input feature, the AttributeManager will fail to resolve the value of feature[-1].AttrName for the first input feature.

If this parameter is set to No Substitution, the AttributeManager will resolve all unresolved attributes with an empty string if they are used in a larger expression. If the unresolved attribute is assigned directly and is not part of a larger expression, then the Output Attribute will be unresolved in the same way. For example, if B is missing, and A is set to @Value(B), then A will be missing as well. But if A is set to "B = @Value(B)", A will have the value of "B = ".

As another example, if the value of feature[+2] is the empty string and Default Value is specified, then the empty string will be treated as an unresolved attribute, and will be resolved as the value specified under Default Value.

If this parameter is set to Closest Adjacent Feature, then the unresolved attributes will be resolved as the corresponding attribute of the closest feature, if such a feature exists. When looking for closest features, features with unresolved attributes are skipped. If a prior or subsequent feature has unresolved attributes, it is possible that the current feature is used to resolve the missing attributes.

For example, if the value of feature[-2].AttrName is unresolved, then to resolve the value of feature[-2].AttrName the AttributeManager will look at the closest features to feature[-2], alternating between features prior to and subsequent to feature[-2]. It will first look at feature[-3].AttrName, followed by feature[-1].AttrName if needed, and then feature[-4].AttrName if needed, until all prior and subsequent features specified have been exhausted.

If the attribute remains unresolved within the specified prior and subsequent features, then it will be resolved as the value specified in the Default Value parameter.

Default Value

This parameter specifies the value used to resolve unresolved attributes in these cases:

• Substitute Missing, Null and Empty by: is set to Default Value
• Substitute Missing, Null and Empty by: is set to Closest Adjacent Feature and a value is not found in within the number of prior and subsequent features specified.

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 - whether entered directly in a parameter or constructed using one of the editors.

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.
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.
Working with User Parameters	Create your own editable parameters.

AttributeCopier

AttributeCreator

AttributeKeeper

AttributeRemover

AttributeRenamer

AttributeValueMapper

BulkAttributeRenamer

BulkAttributeRemover