Updating using the Overwrite the active diagram option

The Overwrite the active diagram option works on GIS features that remain selected after a tracing or selection operation in one of the map document's data frames. It allows you to overwrite the entire active diagram content from the input GIS features selected in the map. Updating a diagram using this option is similar to regenerating it from a new set of GIS features that are highlighted after a selection or tracing operation. The only difference concerns the geometry of the schematic features in the diagram after the update: if the diagram has been laid out and saved, the schematic features contained in the diagram before the update that are associated with GIS features currently selected in the map keep their saved geometry after the update.

NotaNota:

If no GIS features are currently selected in the map document and no tracing operation has been performed, or when the active diagram is entirely built from custom queries, the Overwrite the active diagram option is unavailable.

After checking the Overwrite the active diagram option, you need to specify which input GIS data you want to be used to overwrite your schematic diagram. Two types of input can be used:

In both cases, the update process is performed as follows:

  1. The schematic features contained in the diagram that don't come from custom queries are loaded in memory.
  2. The current set of GIS features highlighted in the map is analyzed, and the builder operates as follows:
    • The schematic features initially contained in the diagram that are associated with highlighted GIS features in the map are updated; their attributes and initial geometry are refreshed, and their current geometry is reinitialized if the diagram was not saved.
    • New schematic features coming from GIS features highlighted in the map are created in memory. Their attributes are evaluated, and their topology and geometry are initialized.
    • The schematic features initially contained in the diagram that are no longer associated with GIS features highlighted in the map are removed from the memory.
  3. Then, if schematic rules are specified for the related diagram template, they are executed on all the in-memory schematic features.
  4. If the Persist manually removed, reduced or reconnected features check box is checked, the removal, reduction, and reconnecting operations are reexecuted.
  5. If there is a default schematic layout algorithm configured for the diagram template and the diagram has no saved layout, the algorithm is reexecuted, and the geometry for all the in-memory schematic features is updated accordingly.
  6. All the schematic features in memory are saved in the schematic feature classes in the schematic dataset.
  7. The active schematic diagram is then refreshed with the new schematic dataset content.

NotaNota:

If the diagram template is configured to mix the schematic features associated with the GIS features highlighted in the map document with schematic features coming from custom queries, there are additional steps during the update process:

  • Schematic feature classes with custom queries configured to be launched during the 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 at the diagram loading—that is, queries with the Query on Start Editing evaluation mode—are processed just after executing the rules.
In both cases, the update process is performed as follows:
  • All the schematic features stored in the schematic feature classes with custom queries are loaded in memory.
  • The custom query specified on each schematic feature class is executed, and the in-memory schematic features are updated as follows:
    1. The in-memory schematic features that are still associated with queried records are updated; their attributes and initial geometry are updated, and their current geometry is reinitialized if the diagram was not saved.
    2. New schematic features associated with new queried records are created in memory. Their attributes are evaluated, and their topology and geometry are initialized.
    3. The schematic features in memory that are no longer associated with returned records are removed from the memory.

NotaNota:

If a particular layout was saved for the active diagram before its update, schematic features that are already contained in the diagram before update keep their last saved position, while new schematic features introduced in the schematic diagram during the update are positioned this way:

  • At their geographic coordinates if they come from GIS features organized into a geometric network
  • At their initial coordinates if they were built by custom queries and such initial coordinates are configured
  • At the (0,0) location if they were built by custom queries and no initial coordinates are specified

PrecauciónPrecaución:

For diagrams initially generated from tracing operation results, the tracing operation parameters are stored in the schematic database during the generation process. When updating using the Overwrite the active diagram option, these initial tracing operation parameters are erased during the update. In this case, choosing the Overwrite the active diagram option prevails over the way the diagram was initially generated. The following table shows the state of the persistent tracing operation parameters after updating when using the Overwrite the active diagram option with the Current Selection or Current Trace option:

Diagram initially generated from a trace

Diagram initially generated from a GIS feature selection set

Overwrite from Current Selection

The initial trace parameters that were in the schematic database before the update are lost after the update.

Still, no trace parameters are preserved in the schematic database.

Overwrite from Current Trace

The new trace parameters are included in the schematic database and overwrite those that were initially preserved.

The parameters related to the appended trace are maintained in the schematic database.

Update by overwrite specifics

7/11/2012