This function allows you to split or trim a single network feature using a point, or one or more features using an intersection line. Both linear features (lines) and polygon features (areas such as Protective Tubes, Trench Boundary, and other polyline features) are supported.
All features affected by the cut are listed and highlighted on the map, allowing you to review and exclude individual features from the operation.
The following cutting options are available:
•Split: Divides a feature into two separate features at the selected location, retaining both sides of the cut.
•Trim: Removes one side of a feature at the selected location, retaining only the selected side of the cut.

To cut features:
1.Go to Edit > Cut.
2.From the left panel, choose between cut by point or by line:
▪By Point: The mouse pointer changes to a circle symbol. Snapping is automatically activated and the network feature to be cut is highlighted when you move over it. The mouse pointer can now be placed on the feature with a mouse click.
The network rules validation running in the background may cause a slight delay when executing the snap function.
▪By Line: The mouse pointer changes to a cross symbol. You can now use the mouse to draw an intersecting line over one or more feature(s). Double-click to end the line.
Cut with line can split or trim both linear features and polygon features (areas):
- Linear features are split where the line intersects them.
- Polygon features are only split if they are completely intersected by the line.
3.You can perform the following actions on the selected features using the functions available in the Action menu.
Button |
Description |
|---|---|
|
Zoom to the selected feature on the map. |
|
Pan to the selected feature on the map. |
|
Remove everything except the selected feature from your current selection. |
If you select more features that are not related to the intersecting line, you can remove them by clicking Minus next to the feature.
When splitting, the function is first applied to selected features, otherwise to intersected features.
If an intersecting line is placed over several unselected linear features, all these lines are added into the cut selection.
If only one of these lines is selected, only the selected line will be cut.
4.From the left panel, choose between split or trim:
▪Split: Choose split to separate the feature into two parts, while retaining both segments.
▪Trim: Choose trim to cut out a segment, while keeping the other.
The Side to Keep button is marked on the map with its mentioned color.
5.Click Cut.
Your cut features are saved.
If one or more attachments are present in the line you split, the attachments are copied to the resulting split lines.
When you split a structure line that has a cross section description attached:
•Cross Section Data Distribution: If a structure line feature with cross section description attached is split:
▪The JSON attachment is kept for the segment where the reference line is located.
▪The other segment gets a automatically generated cross section.
•Data Validation: The system does not automatically check for errors in outdated cross section data structure. If you encounter issues, you can reset the cross section data using the Cross Section Panel.
•Placement Block Considerations: If a Placement Block exists in the cross section data, the system will automatically clear it when the split line geometry no longer matches the original reference line, preventing geometric inconsistencies between the cross section data and the actual line segments.
After splitting structure lines with cross sections, review your cross section data in the Cross Section Panel to ensure accuracy and make any necessary adjustments.
Areas can only be divided with a cutting line. When using "Split with Point", the system checks whether a feature with line geometry is found underneath. If no line geometry is found, you will receive an error message: "Error splitting a feature with a point! No feature with line geometry found."
When you split features with existing containment associations, these connections are updated based on the features being split:
•Containment Associations: The associations between containers and contained features are updated as follows:
oBoth Container and Contained Features Split: The resulting features are associated based on their spatial proximity.
oOnly Container Split: The contained features are associated to the closest resulting container segment or to both container segments, if they are spatially equally close.
oOnly Contained Features Split: Only the closest resulting segment is associated to the original container. If both resulting segments are spatially equally close, both are associated to the original container.
When you split features with existing relationships, these connections are updated based on the features being split:
•Feature Relationships: Relationships between origin and destination features are updated as follows:
oBoth Origin and Destination Split: The resulting features are related based on their spatial proximity.
oOnly Origin Split: The spatial destination feature is related to the closest resulting origin segment.
oOnly Destination Split: Both resulting destination segments are related to the original origin feature if the relationship cardinality allows it. Otherwise, the relationship is assigned to the destination segment with the larger geometry if the origin feature has geometry.
When you split a line that has a relationship with a non-spatial feature, the relationship is updated based on the origin and destination roles and the relationship cardinality:
•Line as Origin (Non-Spatial Destination):
oCardinality Allows Multiple Relationships: The non-spatial feature is related to both resulting line segments.
oCardinality Restricts Multiple Relationships: The non-spatial feature is related only to the longer resulting line segment.
•Line as Destination (Non-Spatial Origin):
oCardinality Allows Multiple Relationships: Both resulting line segments are related to the original non-spatial feature.
oCardinality Restricts Multiple Relationships: The relationship can only be maintained with one resulting line segment.
When you split a line/polygon with linked annotations:
•Linked Annotation Placement: The annotations are linked to the newly split features based on their geometrical closeness, to get to the nearest Annotation/Line segment combination:
oPolygon split: The center point of the polygon is taken as a reference to determine to which polygon the annotation is placed.
oLine split: The linked annotation is linked to the line with the smallest projected distance.
•Annotation Text: Annotation text is only updated if it is not triggered automatically.
The table below provides information on split policy for attribute domains.
Policy |
What Happens |
Works with |
Example |
When to Use |
|---|---|---|---|---|
DefaultValue |
The attributes of the resulting features take on the default value for the attribute of the given feature class or subtype. |
Coded & Range Values. |
A pipe with status "In Service" is split into two pieces. Both new pipe segments get the default status "Planned" instead of keeping the original "In Service" status. |
When the original value no longer applies logically to the new segments. |
Duplicate |
The attributes of the resulting features take on a copy of the original object's attribute value. |
Coded & Range Values. |
Split plastic pipe - both segments retain the same material (plastic). |
When the attribute should remain unchanged (e.g., material type). |
GeometryRatio |
The attribute values of the resulting features are split proportionally based on geometry. |
Range Values ONLY. |
A 10-meter pipe divided in a 60/40 split results in 6-meter and 4-meter segments. |
When the attribute value should be proportional to the size of each segment. |
The value five is the default value of the system.
The section below describes the splitting behavior of the Networks Editor and the rules it is based on. In order to clarify this, we use an example of a use case where the user creates a new network point feature in the middle of a line, via snapping, and not at its end points.
Possible subsequent actions:
1.Automatic split of the line.
The Networks Editor automatically takes over splitting.
2.Optional split of the line.
The user is free to decide whether he wants to split the line. From a network topological point of view, both (line split/no line split) are correct and wouldn’t create a dirty area.
3.No split of the line.
From a network topological point of view, the insert of network point must not split the line.
4.Error message.
It is not possible to insert the point from a network topological point of view (neither splitting nor non-splitting).
The follow-up action that is performed depends on several factors:
a.Does the network point have connection points (terminals)?
b.Is there a junction-edge rule?
c.Is there a junction-edge-junction rule?
d.What edge connectivity does the line have (Any vertex—Features/End vertex—Features)?
Terminals |
Junction-Edge Rule |
Edge-Junction-Edge Rule |
Edge Connectivity: Any Vertex |
Edge Connectivity: End Vertex |
Action |
|---|---|---|---|---|---|
X |
(X) |
X |
X |
|
Automatic split |
X |
(X) |
X |
|
X |
Automatic split |
|
|
X |
X |
|
Automatic split |
|
|
X |
|
X |
Automatic split |
|
X |
|
|
X |
Automatic split |
|
X |
X |
X |
|
Optional split |
|
X |
|
X |
|
No Split |
X |
|
|
|
|
Error |
X |
|
|
X |
|
Error |
X |
|
|
|
X |
Error |
X |
X |
|
X |
|
Automatic split |
X |
X |
|
|
X |
Automatic split |
|
|
|
|
X |
Error |
|
|
|
X |
|
Error |
This function is used to merge split network features, this is useful for when you plan on extending an existing structure.
To merge lines/areas:
1.Go to Edit > Merge.
The mouse pointer changes to a circle symbol. Snapping is automatically activated and the feature to be merged is highlighted when you move over it.
2.Select the lines/polygons you want to merge.
A table comparing the source and target features is shown in the merge menu.

You can choose to compare only attributes which differ between both features, or choose to compare all attributes in the table by clicking on the Show only differences check-box.
If two structure lines both with attached cross section descriptions are merged, only the cross section description of the target feature will be kept. After merging the structure lines, this cross section description may have become inconsistent. Review your cross section data in the Cross Section Panel to ensure accuracy and make any necessary adjustments.
3.Choose which feature is the target feature (highlighted in green). The remaining feature is automatically assigned as the source feature.
If there are one or more associations, relationships, and/or attachments present in one of the merged features, they will be moved to the target feature that you choose.
When merging lines, the tool detects the suitable intersections at line ends, and the nearest valid point is used. If no intersection can be created, an error message is displayed.
When merging polygon features, make sure the areas overlap, otherwise, the merge cannot happen.
The target feature keeps all of its attributes after the merge is complete.
When merging lines with multiple annotations, all annotations are linked to the newly merged lines.
In the Split and Merge features, you can split Utility Network layers, as well as, simple feature layers.
The table below provides information on merge policy for attribute domains.
Policy |
What Happens |
Works With |
Example |
When to Use |
|---|---|---|---|---|
Area Weighted |
The attribute of the resulting feature is the weighted average of the values of the attributes from the original features. |
Range values ONLY. |
Two parcels are merged where Parcel A covers 40% of the total merged area with a ground value of 1000 €/m², and Parcel B covers 60% of the total merged area with a ground value of 500 €/m². The merged parcel gets a weighted average value of (0.4 × 1000) + (0.6 × 500) = 700 €/m². |
When you want a size-weighted average of the original values. |
Sum Values |
The resulting feature's attribute is the sum of the original features' attribute values. |
Range values ONLY. |
Merging a 12 meter pipe with an 8 meter pipe results in a new 20 meter long pipe. |
When you need to add attribute values together (e.g., total capacity). |
Default (Target Feature Adoption) |
The attribute of the new feature is adopted from the designated target feature. |
Coded & Range Values. |
Merging two pipes results in a new pipe that inherits all properties from the pipe you selected as the target. |
When you want to preserve all attributes from a specific feature. |