Update Subnetwork (Utility Network Tools)
Summary
Updates subnetwork information in the Subnetworks table, the SubnetLine feature class, and subnetwork system diagrams for the specified subnetworks.
For the Subnetworks table, this tool changes the status of associated subnetwork controllers to clean (the Is dirty attribute is set to False). If validate consistency failures or subnetwork errors are discovered during tool operation, the status of the associated subnetwork controllers will be marked invalid (the Is dirty attribute is set to Invalid). In the SubnetLine feature class, a record for new subnetworks will be generated, the records for deleted subnetworks will be removed, and the shape and information for modified subnetworks will be updated. Certain attributes will also be created or updated for subnetwork features.
If the update subnetwork policy for a tier is configured so the Is dirty attribute is not managed, the update subnetwork operation can be used to delete rows in the Subnetworks table when the Is deleted attribute is set to true.
Usage
The following requirements must be met when working with an enterprise geodatabase:
The utility network must be registered as branch versioned.
The input utility network must be from a utility network service.
The update subnetwork operation can be used on the default version to delete rows in the Subnetworks table for tiers that do not manage the
Is dirtyattribute.If this tool is run on the default version, the geometry, subnetwork name attribute, and propagated fields of the SubnetLine feature class will be updated in place. If this tool is run on a named version, the default behavior (without events) limits updates to features and objects edited in the version. The edit mode can be changed to use events (with events). This option runs geodatabase behavior and can be set in the subnetwork definition for both the default version and named versions.
Learn more about the edit mode used by the Update Subnetwork tool
Only update a subnetwork using a single process at a time. Do not run the tool with the All subnetworks in tier parameter checked when running multiple processes. This may result in a failure when two processes attempt to update the same subnetwork at the same time.
-
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.
This tool is supported for use with traditional domain networks only.
This tool creates or updates network diagrams for the updated subnetworks if a diagram template was specified when setting the subnetwork definition.
Any edits must be saved before running this tool.
The network topology must be enabled.
No dirty areas exist that intersect with subnetwork features.
Parameters
| Label | Explanation | Data type |
|---|---|---|
|
Input Utility Network |
The utility network that contains the subnetwork. |
Utility Network; Utility Network Layer |
|
Domain Network |
The domain network that contains the subnetwork. |
String |
|
Tier |
The tier that contains the subnetwork. |
String |
|
All subnetworks in tier |
Specifies whether all subnetworks in the tier will be updated. To update a subset of subnetworks in the tier, use the Subnetwork Name parameter.
|
Boolean |
|
Subnetwork Name (Optional) |
The name of the subnetwork that will be updated from the tier. If the All subnetworks in tier parameter is checked, this parameter is ignored. When the subnetworks table contains 10,000 or more records for a tier, the parameter's choice list is not populated and an empty field is provided for the subnetwork name. |
String |
|
Continue on failure (Optional) |
Specifies whether the update process will stop if a subnetwork fails to update when updating multiple subnetworks.
|
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 Note:This parameter is only available for Python. 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. Note:This parameter is only available for Python. Value table columns:
|
Value Table |
|
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.
|
Boolean |
|
Apply Traversability To (Optional) |
Specifies the type of traversability that will be applied. Traversability scope determines whether traversability will be applied to junctions, edges, or both. For example, if a condition barrier is defined to stop the trace if Note:This parameter is only available for Python.
|
String |
|
Propagators (Optional) |
Specifies the network attributes to propagate as well as how that propagation will occur during a trace in a traditional domain network. Propagated class attributes denote the key values on subnetwork controllers that are disseminated to the rest of the features in the subnetwork. For example, in an electric distribution model, you can propagate the phase value. Note:This parameter is only available for Python. Value table columns:
|
Value Table |
Derived output
| Label | Explanation | Data type |
|---|---|---|
|
Updated Utility Network |
The updated utility network. |
Utility Network |
Environments
This tool does not use any geoprocessing environments.
Licensing information
- Basic: No
- Standard: Yes
- Advanced: Yes