Supported with: ArcGIS Engine, ArcGIS Desktop

Library dependencies: System, Geometry, Display, Output, GeoDatabase, Carto

Additional library information: Contents, Object Model Diagram

 

This content is also available in versions that specifically target .NET and Java developers. Click on the appropriate link to view either version.
        .NET overview of the Schematic assembly
        Java overview of the Schematic package

The Schematic library implements the non user-interface functionality of the Schematics extension. It handles the core objects of the Schematics extension used to manage schematic data and schematic processes. The Schematics extension supports the analysis, display and manipulation of schematic data within ArcGIS. 

Developers can extend this library by implementing custom schematic algorithms, custom rules, and custom builders.

The objects that implement this functionality are grouped into a number of library subsystems. These library subsystems are:

• Graphical Core
• Database Core
• Schematic Project Manager
• Schematic Layers Objects
• Builders and Rules Objects
• Linker and Relation Objects

Graphical Core

The graphical core is the set of primitive objects that forms the foundation for the schematic objects in memory.
The NgProject class is the central class for the Schematic graphical core. It handles the core information model that defines the schematic project. It acts as the central point where access is gained to other schematic objects in memory.
The NgProject class implements several interfaces:

• The INgProject interface, that provides access to all graphical components defined in your application. These components mainly concern the diagram types (INgDiagramType) and the element types (INgElementType) that specify your schematic diagrams’ content and their graphic display.
• The INgProjectBuilder, which is the interface that lets you create and define these graphical components.
• The INgProjectEvents, that provides access to events that occur to graphic objects (that is, to diagrams and elements).
• The INgProjectAlgorithm, that controls the management of the schematic algorithms.
• The INgProjectAnalyst, that controls the management of the schematic network trace analysts.

Note: Several predefined layout algorithms and trace analysis are also available. You can implement your own custom schematic layout algorithm and schematic trace analyst.

 

Database Core

The database core is the set of primitive objects that forms the foundation for the schematic objects in the schematic database.
The SchematicDataset class is the central object in the schematic database.
A schematic dataset is a container of schematic data such as schematic data sources, schematic diagram classes, schematic element classes, schematic folders, and schematic diagrams. A schematic dataset resides in a personal or an enterprise geodatabase. Several schematic datasets can be stored in the same geodatabase.

 

Schematic Project Manager

The Schematic Project Manager allows linking the objects related to the schematic database core to the objects related to the graphical core part.
It provides access to the schematic datasets and their related schematic projects. A schematic dataset is related to a single schematic project.

 

Schematic Layers Objects

In ArcMap, schematic data is represented in schematic layers.
The SchematicLayer class is the central object for managing schematic layers. It lets you access the schematic diagram associated with a schematic layer.

 

Builder and Rules Objects

Schematic Builders

Schematic builders are used to generate the diagrams related to a Schematic Diagram Class.
Three types of predefined builders are available; Standard builder, Network Dataset builder and Custom Query Based builder.
You can implement your own custom schematic builder.

Schematic Builder Rules

Schematic builder rules are used to simplify a graph (reduction rules) or create new schematic elements such as containers around the elements contained in a graph (relationship or spatial query rules). Schematic builder rules operate in the geodatabase during diagram generation or update, after the builder has created the elements (associated with the set of features highlighted in the map) in the appropriate schematic element classes.
Six types of predefined rules are available, the Node Reduction By Priority rule, the Node Reduction By Flow rule, the Route Node Reduction rule, the Node RelationShip rule, the Spatial Query rule, and the Collapse Related Elements rule.
You can implement your own custom schematic builder rule.

Note: The provided predefined rules only work with the Standard and Network Dataset builders.

 

Linker and Relation objects

Schematic Linker

The SchematicLinker class handles the interfaces that allow managing associations between features or objects and schematic elements; that is:

• Specifying the association between an object and a schematic element, or removing association between an object and a schematic element.
• Retrieving objects associated with specified schematic elements, and conversely.

Note: Objects are generally features but they can be rows in a table.

Schematic Relation

The SchematicRelationController class handles the interfaces that allow managing relations between schematic elements; that is:

• Creating or removing relations between schematic elements.
• Managing the graphical display of the relations in the diagrams.
• Retrieving elements in relation with other elements.
• Controlling the elements’ behavior when their related element are moved, and conversely.

Two types of relations are available, Schematic Container Relation and Schematic Barycenter Relation.