How does the Standard builder operate from network features?

Diagram templates are always associated with schematic feature classes. For the Standard builder, these schematic feature classes are related to the GIS feature classes with which the builder is supposed to deal.

When generating a diagram based on the Standard builder from a set of GIS features organized into a geometric network or a network dataset, the builder populates the schematic feature classes—that is, it creates the schematic features expected in the diagram as follows:

1. It analyzes the geometric network features currently highlighted in the map document after a selection or tracing operation, or the network elements currently selected in the map document.
2. For each feature layer containing these network features, it verifies whether it is expected to deal with them—that is, it verifies that a schematic feature class associated with the related GIS feature class exists for the diagram template.

   If there is such a schematic feature class for the diagram template, for each feature currently highlighted in the feature layer, it creates the associated schematic feature in memory, evaluates its attributes, and initializes its topology and geometry.

3. If schematic rules are specified for the related diagram template, they are executed on all the schematic features built in memory.
4. If there is a default schematic layout algorithm configured for the diagram template, the algorithm is executed and the geometry for all the in-memory schematic features is updated accordingly.
5. All the schematic features in memory are saved in the schematic feature classes in the schematic dataset.
6. All the created schematic features are queried from the schematic feature classes, and the diagram is displayed.

Then, at any time and for its lifetime—that is, until it is deleted from the schematic dataset—the diagram can be

• Reopened.
• Edited, laid out, and saved.
• Updated so its content stays in accord with the network features, and changes that impacted the associated GIS features are reported on the associated schematic feature. For diagrams based on GIS versioned data, it can also be updated from any other reference version; this means that even if diagram generation was based on a specific version, if this GIS data version no longer exists or is not the reference version anymore, the diagram reference version can also be changed so the diagram content evolves with the change of GIS reference version.

Note:

Diagram templates based on the Standard builder can also be used to generate mixed diagrams that contain schematic features associated with the GIS features highlighted in the map document and schematic features coming from custom queries that operate from any type of database. In this case, there are intermediate steps during the generation process:

• Schematic feature classes with custom queries configured to be launched during diagram building—that is, queries with the Query on Generate/Update evaluation mode—are processed just before executing the rules.
• Schematic feature classes with custom queries configured to be launched during diagram loading—that is, queries with the Query on Start Editing evaluation mode—are processed just after executing the rules.

In both cases, the custom query specified on each schematic feature class is executed, and the schematic features related to each queried record are created in memory, their attributes are evaluated, and their topology and geometry are initialized.

Note:

When configuring the Standard builder properties, you can enable a specific running mode called Automatic schematic feature class creation. When this mode is enabled, the Standard builder will be able to deal with all GIS features highlighted in the map even if, at the time of the generation, there is no schematic feature class associated with the GIS feature classes of the highlighted features in the map. When running in this mode, the builder automatically creates the missing schematic feature classes for the diagram template before populating them.

Caution:

Turns and signposts in network dataset data are nonnetwork elements. You can generate diagrams containing schematic features related to such elements, but they will appear as disconnected elements in your diagrams. This means that those particular elements could have a meaning when your diagram content is displayed with geographic coordinates, but are never correctly positioned after executing any schematic layout algorithm. To get diagrams that are schematically workable, it's recommended that you avoid having schematic features corresponding to those particular elements in your diagrams by doing one of the following:

• Configure the signpost or turn feature layers as nonselectable layers in the map where you select network elements for diagram generation.
• Dissociate the schematic feature classes related to those signpost or turn feature classes from the diagram template used for diagram generation.
• Configure feature removal rules on the diagram template used for diagram generation to automatically remove those schematic features from the diagrams.