FME Transformers: 2024.1
FME Transformers: 2024.1
LineBuilder
Connects sequential point and/or line features to create line or area geometry.
Typical Uses
- Connecting points to form a line
- Connecting multiple lines into longer, continuous lines
How does it work?
The LineBuilder receives features with point and/or line geometry, and connects them in the order received, producing line or area geometry.
Both the order in which the features enter the transformer and the orientation of any line geometry received are honored. Gaps between line features are connected, and duplicate points may be either processed or ignored.
Z values are supported. If some input features have z values and others do not, those without are assigned a z value of zero (0). Features with matching x and y coordinates but differing z values are not considered duplicates.
If the output feature is closed (the first and last x and y coordinates are the same), an area is output whether or not the z values match.
Features may be grouped by attribute values to produce multiple outputs.
Attributes may be merged, dropped, or collected as List Attributes.
Examples
Example: Connecting a series of GPS points to form a line
In this example, we have a set of point features captured by GPS along a route. We want to create a line from these sequential points.
The features are routed into a LineBuilder.
In the parameters dialog, the default settings are used.
A single line feature is output, connecting all of the input points in the order they were received.
Usage Notes
- The Sorter may be useful for ordering features before using the LineBuilder.
- As the LineBuilder fills in gaps between features, it can produce unexpected results if the input features are not sorted correctly. To combine adjoining lines (without creating new geometry to connect gaps), use a LineCombiner.
- The CoordinateSwapper may be useful in specific cases.
Creating and Modifying Linear Features
These transformers work with lines in a variety of ways.
Line Transformers Comparison
|
Function |
Transformer Description |
---|---|---|
Simple creation of lines from lines and/or points. |
Connects sequential point and/or line features to create line or area geometry. |
|
Combining adjoining lines into longer lines or complex paths, with more advanced geometry handling options than the LineBuilder. |
Connects line features that meet at common start or end points to create longer lines or paths. |
|
Combining arcs and lines into longer paths. |
Connects sequential line and/or arc features to create path geometry, preserving input segments. |
|
Converting linear features into areas. |
Converts a linear feature to an area by connecting the end point to the start point. |
|
Extending linear geometry. |
Extends line, arc, or path features at both ends by a specified length. |
|
Chopping features into smaller features, breaking them at their existing vertices. |
Chops line, arc, path, or area features into smaller features based on number of vertices or approximate length. |
|
Breaking a path into its component segments (lines and arcs). |
Splits path geometry into its component line and/or arc segments. |
|
Shortening linear geometry. |
Shortens linear geometry by cutting off the ends. |
|
Intersecting lines and areas. |
Performs a line-on-area overlay, either splitting lines where they intersect area boundaries or subdividing areas where split by lines. Attributes may be shared between related lines and areas (spatial join). |
|
Intersecting lines and lines. |
Performs a line-on-line overlay in which all input lines are intersected against each other and resultant line features are created and output. Intersection points are turned into point features that can contain the merged list of attributes of the original intersected lines. |
|
Finding where points lay on lines. |
Performs a point-on-line overlay. Each input line is split at its closest place to any point within the specified point tolerance, and attributes may be shared between related points and lines (spatial join). |
Configuration
Input Ports
Output Ports
Point
If the resulting feature is a single point, it will be output through this port.
Line
If the resulting feature does not begin and end at the same point, it is output through this port.
Polygon
If the resulting feature forms a ring (begins and ends at the same point), it is output through this port.
<Rejected>
Any features that are not points or lines are output through this port.
Rejected features will have an fme_rejection_code attribute with one of the following values:
INVALID_GEOMETRY_TYPE
Rejected Feature Handling: can be set to either terminate the translation or continue running when it encounters a rejected feature. This setting is available both as a default FME option and as a workspace parameter.
Parameters
Group Processing
Group By |
The default behavior is to use the entire set of input features as the group. This option allows you to select attributes that define which groups to form – each set of features that have the same value for all of these attributes will be processed as an independent group. If only one point feature was received with a given value for the Group By value, it will be output as a Point. If the feature output forms a ring (begins and ends at the same point), it is output as a Polygon. Anything else is output as a Line. |
||||
Complete Groups |
Select the point in processing at which groups are processed:
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. |
General
Remove Duplicate Points |
If Yes, duplicate coordinates from input features are removed. That is, if two point features, both at (0,0,0) are input, one point at (0,0,0) is output. If No, duplicate coordinates from input features are not removed. That is, if two point features at (0,0,0) are input, a line is output with two coordinates, both at (0,0,0). |
||||||
Accumulation Mode |
Specify how attributes are accumulated on combined lines:
|
||||||
Generate List
|
When enabled:
|
Editing Transformer Parameters
Transformer parameters can be set by directly entering values, using expressions, or referencing other elements in the workspace such as attribute values or user parameters. Various editors and context menus are available to assist. To see what is available, click beside the applicable parameter.
How to Set Parameter Values
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.
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.
Content Types
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
Table Tools
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.
For more information, see Transformer Parameter Menu Options.
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 all results about the LineBuilder on the FME Community.
Keywords: "point joiner" "line creator" PointConnector