Adding an edge–junction rule

This topic applies to ArcEditor and ArcInfo only.

Steps:

1. In the Catalog tree, right-click the geometric network and click Properties.
2. Click the Connectivity tab.
3. Click the drop-down arrow and click the feature class for which you want to create a rule.
4. Click the subtype of the feature class if your feature class has subtypes.
5. Navigate to and check the junction feature class or subtype you want to make connectable to this edge feature class or subtype.
Default junctions are not set automatically.
6. If you want to set a default junction type, right-click the junction subtype or feature class in the Junction subtypes list, then click Set as default.

   Only one default junction is allowed per edge–junction rule.

7. If you want to restrict the number of edges of this type that can connect to a single junction of this type, check the check box and enter the minimum and maximum number of permissible edges.
8. If you want to restrict the number of junctions of this type that can connect to a single edge of this type, check the check box and type the minimum and maximum number of permissible junctions.
9. Click OK.

   The rule is created in the database.

Note:

• You can use the edge–junction rules to make edge–edge rules more flexible. For example, to add a rule such that an edge of type A must have a junction of type B at one end and a junction of type C at the other end, you must first add the edge–edge rule between the edge types and the two junction types. Then, the edge–junction rules will automatically be created. Navigate to each edge–junction rule and set the edge–junction cardinality so that only one junction of each type may connect to any edge.
• The cardinality of a junction is the number of edge features to which it is connected. When specifying the cardinality of junctions, be aware of one exception. If the junction is connected at midspan to a complex edge feature and nothing else, the cardinality of that junction will be two. In this instance, the cardinality of the junction is based on the number of connected edge elements, not the number of edge features. For example, for this junction to be considered valid, its cardinality should be 0 to 2.
• Stand-alone junctions may be subsumed when new edges are created if an edge–junction rule has been specified with a default junction. When a new edge feature is created and snapped to a stand-alone junction of any type, the junction will be subsumed by the default junction type.
• Setting the default junction class to be the Orphan junction feature class is a valid solution if your business rules that drive the creation of connectivity rules do not have a clear default junction class or type.