Find Subnetworks pane

The Find Subnetworks pane allows you to locate and work with subnetworks in a map. For example, you can select a subnetwork so that it visually stands out on a map. Highlighting a specific subnetwork can be helpful for clarity while editing, as it helps you distinguish paths in dense areas. It can also be used to draw focus to the subnetwork of interest in large-scale maps.

By default, the Find Subnetworks pane presents a list of all subnetworks present on the active map with a record in the SubnetLine feature class. This list can be filtered by map extent or by querying the subnetworks table. The subnetwork you select from this list becomes the active subnetwork when you click the Activate button. The active subnetwork remains visible on a map, while all other subnetworks have a transparency applied. In addition to network features, the SubnetLine feature for the active subnetwork is also highlighted while all others have the transparency applied.

In the list of subnetworks, the presence of an icon in the Status column indicates that the subnetwork is either dirty or invalid.

• A yellow warning icon indicates that the subnetwork is dirty. This means that changes have been made to the subnetwork since the last time it was updated.
• A red warning icon indicates that the subnetwork is invalid. This is displayed when either a subnetwork error is created or a validate consistency failure is encountered during the update operation.

Caution:

Activating a dirty or invalid subnetwork may yield unexpected results. For example, if an edit event disconnects a section of the subnetwork, the subnetwork name remains on the disconnected features until the subnetwork is updated. In this case, the disconnected features would remain highlighted and appear as part of the active subnetwork.

To learn more, see Find a subnetwork.

A subnetwork will not appear in the Find Subnetworks pane if the subnetwork has never been updated by the Update Subnetwork tool or if one or more of its subnetwork controllers are not connected to any other features.

To determine why a subnetwork does not appear in the pane, do the following:

• Check the Last Updated Subnetwork attribute in the Subnetworks table. If NULL is present, it means that your subnetwork has never been updated. You can confirm this by verifying that there is no shape associated with the subnetwork in the SubnetLine class. Update the subnetwork from the Find Subnetworks pane or run the Update Subnetwork geoprocessing tool to update the subnetwork of interest.
• Check the Is Connected attribute of the feature or features directly connected to the subnetwork controller or controllers defining the subnetwork of interest.

To determine whether the feature in question has connectivity to the correct subnetwork controller or controllers, check the Subnetwork Name attribute. If Unknown is present, it may indicate that there is no connectivity to the subnetwork controller or controllers, or that the subnetwork was not updated after the network feature was created. Update the subnetwork from the Find Subnetworks pane or run the Update Subnetwork geoprocessing tool to apply the name of the subnetwork to your feature. If Unknown is still present after you run the tool, confirm that the features are connected either through geometric coincidence or an association to the subnetwork controller and that the network feature is traversable from the subnetwork controller. For example, if the connected feature is not listed as a valid feature or object in the tier's subnetwork definition, it will not be updated with the subnetwork's name. To check connectivity, run a Connected trace. Once you've confirmed the features have connectivity, check for traversability by running a Subnetwork trace.

An active subnetwork is composed of features with the active subnetwork's name in their Subnetwork Name attribute. This includes features that participate in multiple subnetworks with concatenated subnetwork names separated by two colons, for example, subnetwork1::subnetwork2.