Skip To Content

Error feature management

Error features are used to track inconsistent features in a utility network. Inconsistent features are those participating in situations that violate restrictions for a utility network. Error features are created when a topology is enabled or validated, and when subnetworks are updated.

Error features created for utility network features are organized in the following sections based on the operation that caused the error:

Features that are placed geometrically coincident during an edit operation are evaluated when the network topology is validated or enabled. If these features violate restrictions or network rules, or create any other invalid situation, error features are produced and the network features are disconnected. Invalid situations are those that are not supported by the utility network. These situations are listed in the tables below.

Information about an error feature is stored in the respective error attribute table: point error, line error, or polygon error. In an error attribute table, you can see information about the network feature the error is associated with; an ID and description of the error; and, if applicable, the other feature participating in the invalid situation.

To learn more, see View error features.

Error features—Enable and validate network topology

The following errors can result from enabling a network topology or after validating a network topology. To fix an error feature, the associated network feature or features must be corrected. The following table lists details about the error including the situation that produces error features, suggested actions for resolving the error feature, and the error feature or features that are generated.

In the Solution column, Option 1 is often the most useful and has the least impact. However, some options depend on other factors, so the first option may not be the best for your particular case. Some options are flagged with (Admin) as they require the database utility network owner to perform the tasks and often also require that the network topology be disabled. Examples are adding a domain network, assigning terminal configurations, and changing the edge connectivity policy for a feature class at the asset group and asset type level.

Error IDDescription and situationSolutionError feature type

0

Wrong data type.

A field has been assigned the wrong data type. For example, an integer data type for the field was expected instead of a string data type.

Option 1: Correct the data type for the field.

Point or Line

1

The geometry for a network feature is empty.

For example, the shape field is NULL.

Option 1: Delete and re-create the feature.

Point or Line

2

Subtype is unknown.

For example, the Asset Group attribute for a network feature has a value of Unknown.

Option 1: Update the asset group attribute to a value other than Unknown.

Point or Line

3

Get subtype group value failed.

Could not locate the asset group field in the source table or the field is NULL or 0. For example, the Asset Group attribute for a network feature is NULL.

Option 1: Update the asset group attribute.

Point or Line

4

Line feature has fewer than two vertices.

A linear network feature has one or no vertices. For example, a line with a single To and From vertex.

Option 1: Add vertices to the line.

Option 2: Delete and re-create the line.

Line

5

Line feature has length within tolerance.

The length of a linear network feature is too short and fits within the network tolerance. For example, the network tolerance is 1 meter and a line in the network is 90 cm.

Option 1: Adjust the length of the line feature.

Option 2: Adjust the network tolerance. (Admin)

Line

6

Geometry error - Could not locate the vertex along the line feature.

The network topology cannot get the list of vertices associated with a linear network feature.

Option 1: Revalidate the network topology.

Option 2: Delete the vertex, validate the network topology, and create another vertex if needed.

Line

7

Invalid connectivity.

A network point feature is not connected to any other feature. For example, a service point is not connected to anything.

Option 1: Connect the point feature.

Option 2: Delete the point feature.

Point or Line

8

Invalid connectivity - No junction edge rule.

There is no junction-edge rule to support the connectivity between a point and a line. For example, a low-voltage line and the high side of a circuit breaker.

Option 1: Review rules in network properties and change the asset group and asset type of the point or line feature to satisfy an existing junction edge connectivity rule.

Option 2: Add a rule to allow connectivity between the origin and destination features. (Admin)

Point and Line

9

Invalid connectivity - More than one junction edge rule applicable.

A rule exists that allows more than one point to connect to the line end.

For example, a dead end and a rise at the endpoint of an electric line. This is an ambiguous situation where more than one point exists at the endpoint of a line.

Option 1: Offset one of the points (x and y or z).

Option 2: Delete one of the points.

Point and Line

10

Invalid connectivity - Two edge features with different asset type attributes cannot connect.

When two edge features share an endpoint and do not have an intermediate junction, they must be from the same asset type to establish connectivity in the network topology.

For example, a medium-voltage/overhead single phase line and a medium-voltage/overhead three phase line are snapped together.

Option 1: Modify the asset type attributes of the edge features to match. For example: If the asset type for one feature is incorrect, modify it to match the other.

Option 2: Insert a valid junction feature to connect the two edge features. There must be a supporting edge-junction-edge rule to support these features.

Line

11

A linear network feature has an endpoint with nothing connected to it.

For example, a pipe with nothing connected to one of its endpoints.

Option 1: Place an appropriate point feature at the end.

Line

12

There are more than two lines connected to a point in an edge-junction-edge connectivity situation. For example, two medium-voltage overhead lines and a medium-voltage underground line connected via a riser.

Since geometric coincidence based connectivity is checked when the network topology is validated, this situation can occur while editing and then discovered or marked with error features when the network topology is updated.

Option 1: Delete the extra lines or lines.

Point and Line

13

A linear feature that only allows endpoint connectivity has a point or another line feature placed midspan.

For example, a tap is snapped to a midspan vertex on a lateral with an edge connectivity policy of end vertex. This does not honor the edge connectivity policy for the line.

Option 1: Relocate the feature to a vertex that honors the line edge connectivity policy.

Option 2: Delete the point or line feature.

Option 3: Change the edge connectivity policy for the feature. (Admin)

Point and Line

17

There is no containment rule to support the containment association between two features.

Option 1: Re-create the association.

Option 2: Re-create the features and associations.

Point or Line

18

There is no structural attachment rule to support the structural attachment association between two features.

Option 1: Re-create the association.

Option 2: Re-create the features and associations.

Point or Line

19

A linear network feature is multipart. Multipart features are not allowed.

For example, a multi-part transmission pipe.

Option 1: Modify the feature so it is not multipart.

Option 2: Delete the line and re-create it.

Line

20

A linear network feature loops back and intersects itself.

For example, a valid looped pipe with missing z-values.

Option 1: Place a vertex on each line segment at the point of intersection. Adjust the z-value for each vertex to add vertical space between the lines.

Option 2: Split the line into single features.

Line

21

A linear network feature has vertices existing in the same x, y, z location.

For example, a gravity pipe with missing z-values.

Option 1: Offset one of the vertices (x and y or z).

Option 2: Delete one of the vertices.

Line

22

The linear network feature in the map possesses segments that are not present in the network topology.

For example, a section of a main pipe unaccounted for in the network topology.

Option 1: Revalidate the network topology.

Option 2: Delete the problem segments, validate the network topology, and re-create the segments if needed.

Line

23

A network feature has an asset type other than the defined asset types for the asset group it belongs to.

For example, a pole has a padmounted asset type. Padmounted is not an asset type defined for the Poles asset group.

Option 1: Fix the asset type for that feature.

Point or Line

25

Two or more points are geometrically coincident. For example, a service point and a voltage regulator with the same x, y, z coordinates.

Some features cannot exist in the exact same location, while others can. For more information, see Coincident features.

Option 1: Offset one of the points (x and y or z).

Option 2: Delete one of the points.

Point

34

Feature in unsupported containment relationship.

This error can occur when a containment association rule is deleted and the feature still participates in a containment association that the rule supported. This error can also occur if the asset group or asset type attributes for the feature are modified and there are no supporting rules.

Option 1: Check the rules for allowable containment associations in the network properties and modify the features attributes.

Option 2: Create a containment association rule to support the relationship. (Admin)

Point and Line

35

Feature in unsupported structural attachment relationship.

This error can occur when a structural attachment association rule is deleted and the feature still participates in a structural attachment association that the rule supported. This error can also occur if the asset group or asset type attributes for the feature are modified and there are no supporting rules.

Option 1: Check the rules for allowable structural attachment associations in the network properties and modify the features attributes.

Option 2: Create a structural attachment association rule to support the relationship. (Admin)

Point and Line

36

The line feature has an invalid terminal.

An error is encountered when the line feature has a value (other than None or Single Terminal) for the From Terminal or To Terminal fields, and one of the following apply:

  • The device at the line's end point doesn't support terminals.
  • There is no user device at the end point of the line.
  • The device supports terminals but the from/to device terminal value on the line is not a value in the terminal configuration.

If the device at the line's end point doesn't support terminals:

  • Option 1: Assign a terminal configuration (that has the terminal ID listed in the applicable From Terminal/To Terminal field) to the device at the lines end point.
  • Option 2: Replace the value in the From Terminal/To Terminal field for the line with None or Single Terminal.

If there is no user device at the end point of the line:

  • Option 1: Place a device with a terminal ID that corresponds to value in the From Terminal/To Terminal field on the line.
  • Option 2: Replace the value in the From Terminal/To Terminal field for the line with None or Single Terminal.

If the device supports terminals but the From Terminal/To Terminal device terminal value on the line is not a value in the terminal configuration:

  • Option 1: Update the value in the From Terminal/To Terminal field for the line to correspond to a terminal on the device.
  • Option 2: Replace terminal configuration assigned to the device with one that has the corresponding terminal ID from on the line.

Point and Line

37

A feature with the Subnetwork Tap category was found midspan to multiple lines.

An error is encountered when subnetwork tap features have the following unsupported conditions:

  • A subnetwork tap feature is only located at the endpoint of a line feature (not midspan on any line feature).
  • A subnetwork tap feature is midspan to multiple line features.

Learn more about subnetwork taps

Edit the line and tap features to ensure the tap feature is midspan to only one line.

Point and Line

38

Devices with multiple terminals cannot be midspan.

An error is encountered when a device with terminals (terminal configuration) is connected to a line midspan. Even though the line feature supports midspan connections (Any Vertex Edge Connectivity), features with terminals should not be midspan.

Option 1: Relocate the device feature to a vertex at the end point of the line.

Option 2: Replace the midspan device feature with a feature that does not have a terminal configuration.

Point and Line

39

Point feature has invalid terminal configuration.

The device feature has an invalid value for the Terminal configuration attribute. This is used to store the valid path for the device feature.

Inspect and edit the Terminal configuration attribute for the specific error feature.

Option 1: Modify the path assigned to the feature using the Modify Terminal Path pane.

Option 2: While it is recommended to use the Modify Terminal Path pane, it is also possible to manually edit the Terminal configuration attribute using the Attributes pane to point to a valid path.

Tip:

Use the network properties to find the valid paths for the feature by determining the Terminal Configuration Name for the specific asset group and asset type and inspect the Terminal Configurations section for the Valid Paths.

Point

Error features—Update subnetwork

The following errors can result from updating a subnetwork in a utility network. To fix an error feature, the associated network feature or features must be corrected. The table below lists details about the error including the situation that produces error features, the suggested action for resolving, and the error feature or features that are generated.

In the Solution column, Option 1 is often the most useful and has the least impact. However, some options depend on other factors, so the first option may not be the best for your particular case. Some options are flagged with (Admin) as they require the database utility network owner to perform the tasks and often also require that the network topology be disabled. Examples are adding a domain network, assigning terminal configurations, and changing the edge connectivity policy for a feature class at the asset group and asset type level.

Error IDDescription and situationSolutionError feature generated

24

Invalid line feature was discovered during update subnetwork.

An invalid line feature exists based on the Valid Lines value for the tier. For example, the subnetwork definition for subnetworks in a medium-voltage tier does not allow low-voltage lines. Lines created with asset group and asset types not defined in the Valid Lines property for the tier are flagged during the Update Subnetwork process.

Option 1: Disconnect or break traversability to the line.

Option 2: Update the asset group and asset type attribute for the line feature to comply with the Valid Lines property for the tier's subnetwork definition. Reference the network properties to review the Tiers subsection of the specific domain network.

Option 3: Make adjustments to the subnetwork definition to include the line or device features by adding their corresponding asset group and asset type as Valid Lines. (Admin)

Line

26

Invalid device feature was discovered during update subnetwork.

An invalid device feature exists based on the Valid Devices values defined for the tier. For example, the subnetwork definition for subnetworks in a medium-voltage tier does not allow service points. Devices created with asset group and asset types not defined in the Valid Devices property for the tier are flagged during the Update Subnetwork process.

Option 1: Disconnect or break traversability to the points.

Option 2: Update the asset group and asset type attribute for the device feature to comply with the Valid Devices property for the tier's subnetwork definition. Reference the network properties to review the Tiers subsection of the specific domain network.

Option 3: Make adjustments to the subnetwork definition to include the line or device features by adding their corresponding asset group and asset type as Valid Devices. (Admin)

Point

27

Invalid parent subnetwork discovered during update subnetwork. An invalid parent subnetwork from a subnetwork controller is discovered during update subnetwork.

This can occur if geometric coincidence was used to establish connectivity to a subnetwork that is not the direct parent. Validating the network topology and then updating your subnetwork reveals this error. For example, in a gas network valve isolation zone (3), the controller is directly connected to the system zone (1) instead of the pressure zone (2).

Option 1: Ensure your subnetworks are named correctly and were created in order (rank).

Option 2: If the connectivity is incorrect, correct it. For example, connect the value to the pressure zone first.

Point

28

Disjoint subnetwork discovered during update subnetwork.

A disjoint subnetwork was discovered in a tier that does not support this type. Updating the subnetwork will create error features for subnetwork controllers if the subnetwork is disjoint and the Support Disjoint Subnetwork property is set to False for the subnetwork definition of the tier.

Option 1: Review the network properties for the specific tier and ensure that all subnetwork controllers that have the same subnetwork name are traversable to each other to prevent disjoint subnetworks. A subnetwork trace can be used to determine traversability.

Option 2: Enable support for disjoint subnetworks in the subnetwork definition. (Admin)

Point

29

Inconsistent subnetwork name on multiple subnetwork controllers in the same subnetwork discovered during update subnetwork.

A subnetwork controller feature was found with an inconsistent subnetwork name when updating the subnetwork. This occurs when multiple subnetwork controllers are traversable to one another but do not have the same subnetwork name. For example, a mesh subnetwork named BPDJ_20 with four subnetwork controllers; one has A_26 instead of BPDJ_20 listed for the Subnetwork Name attribute.

Option 1: If the subnetwork name for the subnetwork controller is wrong, rename it using the Modify Subnetwork Controller pane.

Option 2: If the subnetwork controller should not be defining the subnetwork, break traversability by disconnecting this controller from the rest of the subnetwork features.

Point

30

Inconsistent parent subnetwork name on multiple parent subnetwork controllers in the same subnetwork discovered during update subnetwork.

A subnetwork controller feature was found with an inconsistent parent subnetwork name when updating a set of subnetworks for a hierarchical domain network. This occurs when multiple subnetwork controllers define a parent subnetwork and one is found with a different subnetwork name.

Option 1: If the subnetwork name for the subnetwork controller is wrong, rename it using the Modify Subnetwork Controller pane.

Option 2: If the subnetwork controller should not be defining the subnetwork, break traversability by disconnecting this controller from the rest of the subnetwork features.

Point

33

Inconsistent controller asset group/asset type.

The asset group or asset type of subnetwork controller has been modified. The asset group and asset type for subnetwork controller features cannot be modified. This is to ensure the terminal configuration that is assigned to a specific asset group and asset type for device features stays consistent with what is being stored for the subnetwork controller.

Option 1: Change the asset group and asset type back to the original value for the subnetwork controller.

Option 2: To safely make edits to the asset group and asset type fields of a subnetwork controller, disable the subnetwork controller from the device feature before making edits to these attributes.

Point