Schematic map packages are an interesting way to share your schematic diagrams and schematic configuration with others inside or outside your organization. In particular, when your schematic data is contained in an enterprise geodatabase, schematic map packages can be provided to people outside your organization who cannot access the source geodatabase.
Packaging schematic diagrams
To set up your schematic diagrams in a map for packaging, you must proceed in the exact same way you do when authoring a schematic map for publishing a schematics service.
Learn how to author a schematic map step-by-step
Once you finish authoring your map with the desired schematic layers, you create your schematic package in the exact same way you do for any map package.
Understanding the resulting package content
The built map package contains:
- A map document (.mxd) with all the schematic layers it references
- The whole schematic dataset definition related to the schematic layers this map references
- All the schematic diagrams related to those schematic layers
- The entire GIS feature classes/tables that are used for joins on schematic feature classes associated with the packed schematic diagrams
Limitations when packaging schematic diagrams
You can't package a map containing schematic layers coming from different schematic datasets.
Compared to the original schematic dataset configuration, the configuration in the packaged schematic dataset will not be exactly the same. The differences are mainly due to the fact that within the packaged schematic dataset, you can no longer guarantee to connect to the real GIS data or object tables on which your schematic dataset is based:
- Any schematic feature class configured with a query and has an evaluation mode of Query On Start Editing will be packaged with the Query On Generate/Update evaluation mode.
- Any schematic attribute configured with the On Start Editing evaluation mode will be packaged with the On Generate/Update evaluation mode.
- The schematic data source related to any GIS feature class/table associated with a schematic feature class may have changed to point to the original data source.
- The schematic data source related to any query may have changed to point to the original data source.