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 schematic diagrams) into any other geodatabase.

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

Exporting a schematic dataset allows you to export the following:

This functionality has been developed to help you quickly and easily transfer schematic dataset configuration changes performed in your test environments to your production 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:

Export Schematic Dataset to Geodatabase dialog box

Learn how to configure the parameters in this dialog box

About exporting schematic diagrams

When you want schematic diagrams contained in the input schematic dataset to be exported in the output geodatabase, select the Diagrams option.

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

The Export command helps 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 is 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 to 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—that is, their associations, custom queries, and query attributes definitions— are not modified during the export.

The following figures 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.
    Reattach options, input and output schematic datasets before export
  • Figure 2.2 shows how associations are set in the output schematic dataset after export when the Reattach to a different geodatabase box is 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 is found in the output geodatabase, no association is set.
    Result with Reattach checked
  • Figure 2.3 shows the associations after export when the Reattach to a different geodatabase box is 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.
    Result with Reattach unchecked

注注:

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

About performances when working with exported schematic datasets

If, among the layers properties configured for diagram templates in the schematic dataset to export, you used joins for the symbology or labeling of your diagram features, those joins may become invalid on the exported schematic dataset. For example, this happens when the joins use connections that can't be no longer opened from the environment into which the schematic dataset is exported.

Such invalid connections are often completely hidden on the exported dataset—meaning, you don't see them at all when displaying the Joins & Relates tab—but they result in bad performances when working with the exported schematic dataset afterwards; for example, when displaying exported diagrams, editing this exported schematic dataset, etc.

To repair those invalid connections on the exported schematic dataset, you must proceed as explained in the following section:

  1. Start ArcMap.
  2. Open one of the diagram from the exported schematic dataset or generate a new one in it.
  3. For each sub layer that composes this diagram, create a dummy join or recreate the join you want for the case you really need one.
  4. Click Apply.
  5. Then, for each diagram sub layer with a dummy join, remove this dummy join or recreate it.
  6. Click Apply.
  7. Right click the schematic diagram layer and save it as layer file (.lyr).
  8. Close ArcMap.
  1. Open the exported schematic dataset within Schematic Dataset Editor.
  2. For the diagram template on which your diagrams are based, import the layer file you've just saved 'As default symbology'.
  3. Save the schematic dataset.

The diagrams based on this template should now generate/open faster and so significantly reduce the times you noted.

5/14/2014