Set Circuit Properties (Utility Network Tools)
Summary
Sets the properties for circuits in a telecom domain network.
The circuit properties for a telecom domain network can be modified using this tool. Configuration parameters are used to define circuit properties which are honored when creating or modifying circuits, and when a trace is run on verify, export, and tracing.
Learn more about how to set or modify the circuit properties.
Usage
This tool allows you to set and alter the circuit properties. To alter the values of a telecom domain network's circuit properties, modify the parameter values and run the tool again.
The utility network dataset must be utility network version 8 or later and contain a telecom domain network.
The network topology must be disabled.
The following requirements must be met when working with an enterprise geodatabase:
The active ArcGIS Enterprise portal account must be the portal utility network owner.
The Input Utility Network parameter value must be from a database connection established as the database utility network owner.
This tool must be connected to the default version to run.
- All other sessions connected to the default version are blocked from running verify or enable operations during an enable network topology operation.
Parameters
| Label | Explanation | Data type |
|---|---|---|
|
Input Utility Network |
The input utility network that contains the circuit. |
Utility Network; Utility Network Layer |
|
Domain Network |
The telecom domain network that will be updated. |
String |
|
Share circuit locations (Optional) |
Specifies whether the features that are used to define the start and stop locations for a circuit can be shared between circuits. This applies to all start and stop locations which define a circuit. A junction or junction object must be assigned the Circuit Location network category to serve as the start or stop location for a circuit or circuit section; however, a line or edge object does not require the Circuit Location network category and can serve as the start or stop location when it does not have connectivity on both the From and To sides.
|
Boolean |
|
Import circuits as clean (Optional) |
Specifies whether circuit definitions will be imported to the Circuit table as Clean or Dirty.
|
Boolean |
|
Max Hops (Optional) |
The maximum number of hops between edges that will be 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 container features and objects traversed during the trace will be included in the trace results.
|
Boolean |
|
Include content (Optional) |
Specifies whether the trace will include content of containers traversed during the trace will be included in the trace results.
|
Boolean |
|
Include structures (Optional) |
Specifies whether structure features and objects with attachments to features traversed during the trace 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.
|
Boolean |
|
Validate locatability (Optional) |
Specifies whether an error will be returned during a trace operation if nonspatial junction or edge objects are encountered without the necessary containment, attachment, or connectivity association in their association hierarchy of the traversed objects. This parameter ensures that nonspatial objects returned by a trace operation can be located through an association with features or other locatable objects.
|
Boolean |
|
Summaries (Optional) |
The
Note:This parameter is not currently implemented and is reserved for future work. Value table columns:
|
Value Table |
|
Condition Barriers (Optional) |
The traversability barrier condition that will be set on features based on a comparison to a network attribute or a check for a category string. A condition barrier uses a network attribute, an operator and a type, and an attribute value. For example, stop a trace when a feature has the Device Status attribute equal to the specific value of Open. When a feature meets this condition, the trace stops. If you're using more than one attribute, you can use the Combine Using column to define an And or an Or condition. Value table columns:
|
Value Table |
|
Function Barriers (Optional) |
Sets a traversability barrier on features based on a function. 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. For example, the length of each line traveled is added to the total distance traveled so far. When the total length traveled reaches the value specified, the trace stops. Value table columns:
|
Value Table |
|
Apply Traversability To (Optional) |
Specifies the type of traversability that will be applied. Traversability scope determines whether traversability is applied to junctions, edges, or both. For example, if a condition barrier is defined to stop the trace if Device Status is equal to Open and traversability scope is set to edges only, the trace will not stop even if it encounters an open 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. Learn more about wavelength propagation Learn more about bitwise operators Value table columns:
|
Value Table |
|
User Attributes (Optional) |
User-defined attribute fields in the circuit management tables that will mark a circuit as dirty when modified. Value table columns:
|
Value Table |
Derived output
| Label | Explanation | Data type |
|---|---|---|
|
Updated Utility Network |
The updated input utility network. |
Utility Network |
Environments
This tool does not use any geoprocessing environments.
Licensing information
- Basic: No
- Standard: Yes
- Advanced: Yes
