Exporting schematic datasets into geodatabases

This functionality is available in the Catalog window. It allows you to export any schematic dataset content (schematic dataset configuration parameters and/or schematic diagrams) into any other geodatabase.

The schematic dataset acts as the entry point for your schematic application. It contains the following:

• The configuration parameters; that is, a set of schematic definitions that provides access to the Schematics application's configuration parameters, including schematic data sources, schematic diagram templates, and schematic feature classes.
• A collection of schematic tables that constitutes the schematic database for that application. These schematic tables contain the schematic diagrams that have already been generated according to the rules and symbology specified by the configuration parameters and the schematic feature classes where the schematic features contained in the generated schematic diagrams are stored.
• The table of associations that specifies the GIS feature class/object table associated with each schematic feature class contained in the schematic dataset.

Exporting a schematic dataset allows you to export the following:

• The configuration parameters stored in a given source schematic dataset into a target schematic dataset:
  • The query, data sources, attributes, and schematic diagram default layers properties specified for all the schematic diagram templates contained in the source schematic dataset
  • The query, data sources, and attributes specified for all the schematic feature classes contained in the source schematic dataset
• The schematic diagrams stored in the source schematic dataset when the Definitions and diagrams option is checked. Depending on the specified options, the schematic diagrams that may already exist in the output schematic dataset can be kept (or not) after export.
• The associations between the schematic feature classes and geographic feature classes/object tables. Depending on the Associated Data Options, the associations specified in the target schematic dataset can be kept if desired after export.

This functionality has been developed to help you quickly and easily transfer schematic dataset configuration changes performed in yourtest environments to yourproduction environments.

Exporting a schematic dataset step by step

Right-click a schematic dataset in the Catalog tree and point to Export > To Geodatabase.The Export Schematic Dataset to Geodatabase dialog box appears:

Learn about how to configure the parameters in this dialog box

About exporting schematic diagrams

If you want both schematic dataset configuration parameters and schematic diagrams contained in the input schematic dataset to be exported in the output geodatabase, you must select the Definitions and diagrams option. Then the diagram export can operate in three different ways:

• By synchronizing schematic diagrams in the output schematic dataset from those contained in the input schematic dataset
• By only exporting the diagrams in the input schematic dataset that do not already exist in the output schematic dataset
• By overwriting diagrams in the output schematic dataset with those contained in the input schematic dataset

Each option is described in the following paragraphs. Figure 1.1 shows the contents of the input and output schematic datasets before export.

• Synchronize diagrams

  This option allows you to synchronize the diagrams contained in the output schematic dataset with those contained in the input schematic dataset. In this case, the output schematic dataset content will be the same as that in the input schematic dataset. Figure 1.2 shows the list of the schematic diagrams in the output schematic dataset after exporting with the Synchronize diagrams option. The new Diagram 1 and Diagram 3 are exported; Diagram 2, which was already in the output schematic dataset,is overwritten; and Diagram 4 is removed.

• New diagrams only

  This option must be used if you want diagrams contained in the input schematic dataset—and not already in the output schematic dataset—to be exported. In this case, only those diagrams are affected during the export process. Figure 1.3 shows the list of the schematic diagrams in the output schematic dataset after exporting with the New diagrams only option. The new Diagram 1 and Diagram 3 are exported; Diagram 2 and Diagram 3, which were already in the output schematic dataset,are retained.

• Overwrite existing diagrams

  This option must be chosen if you want all schematic diagrams in the input schematic dataset to be overwritten in the output schematic dataset while the diagrams existing in the output but missing in the input are retained. Figure 1.4 shows the list of schematic diagrams in the output schematic dataset after exporting with the Overwrite existing diagrams option. The new Diagram 1 and Diagram 3 have been exported; Diagram 2, which was already in the output schematic dataset,is overwritten, and Diagram 4 is retained.

About redirecting schematic configuration parameters and schematic diagram contents to another geodatabase

The Export command has been developed to help you quickly and easily transfer schematic dataset definition changes that could have been performed in your test environments to your production environments. As the test geodatabase is often not the same as the production one, the associations, custom queries, and query attributes configured in the input schematic dataset must be redirected during export so they point to the production data instead of the test data in the output schematic dataset. In the same way, when diagrams are exported from the input schematic dataset to the output schematic dataset, their schematic features must be redirected so they are associated with features/objects contained in the specified output geodatabase. The Associated Data Options section groups the options that can be configured so these redirections happen automatically during export.

Reattach to a different geodatabase

When this option is checked, all the associations, custom queries, and query attributes configured in the input schematic dataset are automatically redirected to another geodatabase in the output schematic dataset, this geodatabase being either the output geodatabase specified in the Output Geodatabase or Schematic Dataset field (by default, Use output geodatabase) or any other geodatabase specified by clicking the Open button at the right of the Use output geodatabase field.

• Regarding associations between schematic feature classes and feature classes/object tables, the export process operates on the names of the geographic feature class/object tables contained in the specified geodatabase. When no geographic feature class/object table with the same name exists in the specified geodatabase, the related schematic feature classes are exported with no association.
• Regarding custom queries and query attributes, the process automatically redirects their related data sources to the specified geodatabase.

For schematic feature classes that already exist in the output schematic dataset before export, their definitions parameters are not modified during the export. That is, their associations, custom queries, and query attributes definitions are not modified during the export.

The following screen shots show how the redirection is done during export:

• Figure 2.1 shows how the schematic feature classes are associated with GIS feature classes in the input and output schematic dataset contents before export. The red and blue arrows are used to symbolize these associations.
• Figure 2.2 shows how associations are set in the output schematic dataset after export when the Reattach to a different geodatabase box was checked. The associations for the SchFeatureClass1, SchFeatureClass2, and SchFeatureClass3 schematic feature classes are kept; the new SchFeatureClass4 and SchFeatureClass5 schematic feature classes are exported. Since in the output geodatabase there is a FeatureClass4 feature class that has the same name as the feature class associated with the SchFeatureClass4 schematic feature class in the input, the exported SchFeatureClass4 is automatically associated with this FeatureClass4 feature class. For SchFeatureClass5, since no feature class with the same name was found in the output geodatabase, no association is set.
• Figure 2.3 shows the associations after export when the Reattach to a different geodatabase box was unchecked. The associations for the SchFeatureClass1, SchFeatureClass2, and SchFeatureClass3 schematic feature classes are retained, and the new SchFeatureClass4 and SchFeatureClass5 schematic feature classes are exported without any change to their associations.

Note:

If the associations between schematic feature classes and GIS feature classes/object tables exported in the output schematic dataset are not set as you want, you can redefine them within Schematic Dataset Editor. Learn more about associating a GIS feature class or object table with a schematic feature class within Schematic Dataset Editor