A subnetwork represents a topological subpart in a tier in which all connected features are defined by the same subnetwork controllers. Subnetwork controllers can be imported into a utility network from a CSV file.
The Import Subnetwork Controllers geoprocessing tool is used to import the CSV file. The Export Subnetwork Controllers geoprocessing tool can be used to export subnetwork controllers into a CSV file.
Requirements
To import subnetwork controllers, the following requirements must be met:
- Subnetwork controllers must be in the correct CSV format and contain the required columns.
- Features and terminals listed in the CSV file must be present in the utility network Device feature class or JunctionObject table and meet the prerequisites to be set as a subnetwork controller.
- If the Input Utility Network is from a database connection, the connection must be established as the database utility network owner.
Import subnetwork controllers
To import subnetwork controllers into a utility network, complete the following steps:
- On the Analysis tab, in the Geoprocessing group, click Tools
to open the Geoprocessing pane. - In the Geoprocessing pane, search for and select Import Subnetwork Controllers.
- For the Input Utility Network parameter, specify a utility network from a database connection or file geodatabase.
- For the Input File parameter, specify the name and location of the CSV file containing the subnetwork controllers.Refer to the Import Subnetwork Controllers tool help for the format of the CSV file.
- Click Run.
The specified CSV file containing the subnetwork controllers is imported into the selected utility network. Rows are written to the subnetworks table and marked as dirty. When you enable the network topology, features listed in the CSV file are now set as subnetwork controllers.
Update the subnetwork or subnetworks for the imported subnetwork controllers to apply the name of the subnetwork to any connected features.