Export Circuits (Utility Network Tools)
Summary
Exports feature and connectivity information about the features and objects that compose circuits in a telecom domain network. The data is saved as separate .json files for each circuit in a specified output folder.
The exported data can be used for archiving or as input to other tools using ModelBuilder, script or model tools, or through integration with external third-party systems.
Note:
The export circuits operation is processed asynchronously using the UtilityNetworkTools geoprocessing service when working with a utility network in an enterprise geodatabase. The UtilityNetworkTools service is preconfigured in the System folder for feature services that include a utility network. It has a longer time-out setting and is reserved for utility network geoprocessing tasks.
Usage
The Input Utility Network parameter value must reference a Utility Network Version value of 8 or later.
The following requirements must be met when working with an enterprise geodatabase:
The Input Utility Network parameter value must be from a utility network service.
The connected ArcGIS Enterprise portal account must be the portal utility network owner.
-
License:
The active portal account must be assigned a license with the ArcGIS Advanced Editing user type extension to use this tool in an enterprise deployment.
When the Set export acknowledged parameter is checked, the following are required:
The network topology must be enabled.
The Input Utility Network parameter value must reference the default branch version.
Parameters
| Label | Explanation | Data type |
|---|---|---|
|
Input Utility Network |
The utility network that contains the circuits that will be exported. |
Utility Network; Utility Network Layer |
|
Domain Network |
The telecom domain network that contains the circuits that will be exported. |
String |
|
Set export acknowledged |
Specifies whether the
|
Boolean |
|
Output folder |
The name and location of the output folder that will store the |
Folder |
|
Max Hops (Optional) |
The maximum number of hops between edges allowed in the path, excluding the start location. All edges and junction-junction connectivity associations are evaluated as having a fixed unit length of 1 on traversal. The default is 100. |
Long |
|
Include Containers (Optional) |
Specifies whether the container features will be included in the trace results.
|
Boolean |
|
Include up to First Spatial Container (Optional) |
Specifies whether the containers returned will be limited to those encountered up to, and including, the first spatial container for each network element in the trace results. If no spatial containers are encountered but nonspatial containers are present for a given network element, all nonspatial containers will be included in the results. This parameter is only enabled when
|
Boolean |
|
Include Content (Optional) |
Specifies whether the trace will return content in container features in the results.
|
Boolean |
|
Include Structures (Optional) |
Specifies whether structure features and objects will be included in the trace results.
|
Boolean |
|
Include Barrier Features (Optional) |
Specifies whether the traversability barrier features will be included in the trace results. Traversability barriers are optional even if they have been preset in the subnetwork definition. This parameter does not apply to device features with terminals.
|
Boolean |
|
Ignore Barriers At Starting Points (Optional) |
Specifies whether dynamic barriers in the trace configuration will be ignored for starting points.
|
Boolean |
|
Validate Locatability (Optional) |
Specifies whether an error will be returned during a trace if nonspatial junction or edge objects are encountered without the necessary connectivity, containment, or attachment association in their association hierarchy. This parameter ensures that nonspatial objects returned by a trace or update subnetwork operation can be located through an association with features or other locatable objects.
|
Boolean |
|
Run in asynchronous mode on the server (Optional) |
Specifies whether the export operation will process asynchronously when working with a utility network in an enterprise geodatabase.
|
Boolean |
|
Condition Barriers (Optional) |
Sets a traversability barrier condition on features based on a comparison to a network attribute or check for a category string. A condition barrier uses a network attribute or network category, an operator and a type, and an attribute value. For example, stop a trace when a feature has the Learn more about using multiple conditional expressions Value table columns:
|
Value Table |
|
Function Barriers (Optional) |
Sets a traversability barrier on features based on a function to restrict the circuit trace used to filter the circuits that will be exported. Function barriers can be used to do such things as restrict how far the trace travels from the starting point, or set a maximum value to stop a trace. This can be used to constrain the circuits that will be exported. For example, consider a scenario where you want to export circuits with a length greater than 1 kilometer. A function barrier could be used to only export the specified circuits when the total length exceeds 1,000 meters. Value table columns:
|
Value Table |
|
Apply Traversability To (Optional) |
Specifies whether traversability barriers will be applied to junctions, edges, or both. For example, if a condition barrier is defined to stop the trace if Device Status is equal to Proposed and traversability scope is set to edges only, the circuit trace will not stop—even if it encounters a proposed device—because Device Status is only applicable to junctions. In other words, this parameter indicates to the trace whether to ignore junctions, edges, or both.
|
String |
|
Propagators (Optional) |
Specifies the network attributes to propagate as well as how that propagation will occur during a trace. Propagated class attributes denote the key values on features in a network that are disseminated to the rest of the features in the circuit. For example, in a telecom domain network, you can propagate wavelengths values from features defined as circuit locations. Note:This parameter is only available for Python. Value table columns:
|
Value Table |
|
Include geometry (Optional) |
Specifies whether geometry will be included in the results.
|
Boolean |
|
Include domain descriptions (Optional) |
Specifies whether domain descriptions will be included in the output
|
Boolean |
|
Synthesize Geometries (Optional) |
Specifies whether geometries will be inferred and created (synthesized) for nonspatial junction and edge objects traversed as part of a circuit trace when using the
|
Boolean |
|
Result Types (Optional) |
Specifies the types of results that will be returned.
|
String |
|
Result Network Attributes (Optional) |
The network attributes that will be included in the results when using the Features result types option. |
String |
|
Result Fields (Optional) |
The fields from a feature class that will be returned as results when using the Features result types option. The values of the fields will be returned in the results for the features in the circuit. Value table columns:
|
Value Table |
Derived output
| Label | Explanation | Data type |
|---|---|---|
|
Updated Utility Network |
The updated utility network. |
Utility Network |
|
Updated Workspace |
The updated workspace. |
Utility Network |
|
Output Circuits Table |
The output table containing information about the exported circuits. |
Value Table |
Environments
This tool does not use any geoprocessing environments.
Licensing information
- Basic: No
- Standard: Yes
- Advanced: Yes