Which transformer is useful for turning your Geometry published parameter into useable features with geometry?

Which transformer is useful for turning your Geometry published parameter into useable features with geometry?

• A. NeighborFinder
• B. ParameterFetcher
• C. SpatialFilter
• D. GeometryReplacer

Answer: (D)

Using a published geometry parameter as actual feature geometry is achieved by replacing the feature geometry with the geometry stored in that parameter. GeometryReplacer is built for this exactly: it takes each incoming feature and substitutes its geometry with the geometry provided by a parameter (or an attribute). That makes the geometry from the parameter—the shapes you defined at run time—the active geometry that downstream transformers can work with. The other options don’t serve this purpose. NeighborFinder looks at spatial proximity between features, ParameterFetcher only retrieves parameter values without applying them to geometry, and SpatialFilter tests features against a spatial condition. None of these replace a feature’s geometry with a parameter’s geometry, which is what GeometryReplacer does.

Using a published geometry parameter as actual feature geometry is achieved by replacing the feature geometry with the geometry stored in that parameter. GeometryReplacer is built for this exactly: it takes each incoming feature and substitutes its geometry with the geometry provided by a parameter (or an attribute). That makes the geometry from the parameter—the shapes you defined at run time—the active geometry that downstream transformers can work with.

The other options don’t serve this purpose. NeighborFinder looks at spatial proximity between features, ParameterFetcher only retrieves parameter values without applying them to geometry, and SpatialFilter tests features against a spatial condition. None of these replace a feature’s geometry with a parameter’s geometry, which is what GeometryReplacer does.