Skip to main content

Analyze Network Data (Utility Network Tools)

Summary

Analyzes a utility network dataset to summarize and report errors in an output mobile geodatabase for resolution.

The output of this tool creates an error resolution database containing a summary of all topology errors identified in the network, their location, the features that participate in the error scenario, and the potential rules that can be added to resolve the error.

Learn more about analyzing and addressing errors in the utility network

Usage

  • The network topology can be enabled or disabled.

  • This tool does not modify the data of the input utility network.

  • The output layer file includes the error layers with definition queries and map relates to the source data to aid in the navigation of the rows and populating the Error Resolution table.

  • When working with an enterprise geodatabase, the Input Utility Network parameter value must be from a database connection established as the database utility network owner.

  • The output of this tool can be modified for use with the Apply Error Resolutions tool to address errors discovered in the utility network. While you can enable the network topology and manually resolve individual errors, it is recommended that you use the tools included in the Migration toolset to identify and resolve the following error types:

    Error

    Description

    The geometry for the network feature is empty. (Error ID: 1)

    A line feature has a zero or near-zero length.

    Unknown asset group (Error ID: 2)

    The subtype that is used for the asset group attribute is unknown.

    Shape length (Error ID: 5)

    The line feature has a length that is within the tolerance. This error can occur when a line feature has a zero or near-zero length.

    Missing rule (Error ID: 8)

    Connectivity exists between junction and edge features without a required junction-edge rule.

    Ambiguous connectivity (Error ID: 9)

    There is more than one rule available for a potential connection.

    Missing junction (Error ID: 10)

    Two lines with a different asset type are connected without a junction or device.

    Edge connectivity policy (Error ID: 13)

    A line has a connection that violates its edge-connectivity policy.

    Multipart geometries (Error ID: 19)

    A linear network feature is a multipart feature.

    Self-intersecting line (Error ID: 20)

    The geometry of a line intersects itself.

    Duplicate vertices (Error ID: 21)

    A line has two or more duplicate vertices or vertices within the tolerance of one another.

    Invalid asset type (Error ID: 23)

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

    Invalid asset group (Error ID: 23)

    A network feature has an asset group with a value outside of the range for the subtype, or the subtype is invalid.

    Stacked points (Error ID: 25)

    Two or more junctions or devices occupy the same x,y,z location.

    Invalid terminal (Error ID: 36)

    The From terminal ID or To terminal ID field of a line is not valid for one of the devices or junctions it is connected to.

    Subnetwork tap (Error ID: 37)

    A feature with the subnetwork tap category is drawn at the end point of two lines.

    Midspan terminal device (Error ID: 38)

    A device that has a terminal configuration is drawn midspan on a line.

    Vertex within tolerance (Error ID: N/A)

    Two or more vertices from separate features are within the spatial tolerance of the dataset but are not topologically coincident.

Parameters

Label Explanation Data type

Input Utility Network

The utility network that will be analyzed for errors.

Utility Network Layer

Output Location

The output folder where the output error resolution mobile geodatabase will be created. The default is the output folder for the project.

Folder

Output Name

(Optional)

The name of the output mobile geodatabase. The default is AnalysisResults.

String

Set default resolution actions

(Optional)

Specifies whether errors will be populated with default actions in the Error Resolution table.

When set to SET_DEFAULTS, the following error types will be populated:

  • Empty geometry—Delete all.

  • Shape length—Delete all.

  • Self-intersecting line—Delete all but the first.

  • Duplicate vertices—Delete all but the first.

  • Stacked points—Delete all but the first.

  • Vertex within tolerance—One Anchor is assigned based on priority (junction > endpoint > midpoint) and Snap is assigned for all others.

  • Checked—The specified error types will be populated with default actions in the Error Resolution table.

  • Unchecked—No error types will be populated with default actions. This is the default.

Boolean

Derived output

Label Explanation Data type

Output Geodatabase

The output geodatabase.

Workspace

Output Layer File

The output layer file.

File

Environments

Extent

Licensing information

  • Basic: No
  • Standard: Yes
  • Advanced: Yes