Find Subnetworks pane

The Find Subnetworks pane allows you to select a subnetwork that will visually stand out on a map. Highlighting a subnetwork is 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 (global extent). 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 become transparent. In addition to network features, the linear feature associated with the subnetwork of interest in the SubnetLine class is also activated, while all others are set to transparent.

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. Run the Update Subnetwork 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 if 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 when the feature was established. Run the Update Subnetwork tool to apply the name of the subnetwork to your feature. If Unknown is still present after you run the tool, confirm that there is a physical connection or association to the subnetwork controller and that there is a traversable path to that feature from the subnetwork controller. For example, if the connected feature is not a valid participant for subnetworks in the tier (pursuant to the subnetwork definition of the tier), it will not receive the subnetwork's name. To check connectivity, run a Find 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 have that subnetwork name as well as others; for example, a tie switch may have two subnetwork names listed in its Subnetwork Name attribute.

In the list of subnetworks, a yellow warning sign in the Is Dirty column indicates that the subnetwork is dirty. This means that changes have been made to the subnetwork since the last time it was updated. Setting a dirty subnetwork as active may yield unexpected results. For example, if an edit event disconnects a section of the subnetwork, features in that disconnected section will continue to have the subnetwork name to which they were previously connected, that is, until the subnetwork is updated. In this case, those disconnected features are highlighted, appearing as part of the subnetwork.