PointCloudMerger
Requestor points are joined to Supplier points when the components specified in the Join On parameter ALL have the same value for both the Requestor and Supplier.
When a Requestor finds a Supplier, the components from the Supplier are merged on to the Requestor. If the Requestor already had a component with the same name, the Conflict Resolution option may be used to control which value is preferred for the merged point cloud.
Each Requestor point cloud will be split into two parts: Points that found a Supplier (Merged) and points that did not find a Supplier (NotMerged).
Each Supplier point cloud will be split into three parts: Points that were found by at least one Requestor (Referenced), points that were not found by any Requestor (Unreferenced), and duplicate points (DuplicateSupplier).
If you want to combine or accumulate point clouds together, as opposed to merging their components, you should use the PointCloudCombiner.
Input Ports
Receives new component values from point clouds connected to the Supplier port.
The source of new component values for point clouds that enter through the Requestor port.
Output Ports
Requestor points that find a Supplier.
Requestor points that do not find a Supplier.
Supplier points that are found by at least one Requestor.
Point clouds output via this port will have an additional reference_count component added, specifying the number of times each point was referenced.
Supplier points that are not found by any Requestor.
Supplier points with the same Join On component values as an earlier Supplier point.
Parameters
If Group By attributes are selected, features with the same values in the Group By attributes are grouped together, and point clouds will only be merged with other point clouds in the same group.
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.
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.
Specifies which components are used to match up Requestor and Supplier points.
Two points are considered to match only if the values for ALL components are equal.
If more than one Supplier point has the same set of values, all points after the first will not be merged with Requestors, and will instead be output the DuplicateSupplier port.
Conflicts occur when Requestors and Suppliers both have a component with the same name.
- Use Requestor: If a conflict occurs, the Requestor values will be maintained.
- Use Supplier: If a conflict occurs, the Supplier values will be transferred onto the Requestor.
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 Licensing Level
FME Professional edition and above
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 samples and information about this transformer on the FME Community.
Keywords: point "point cloud" cloud PointCloud merge merging "merging point clouds" LiDAR sonar