What is a schematic builder?

Any schematic diagram template is based on a schematic builder. Schematic builders are used to build/update the content of diagrams implemented by a schematic diagram template. They expect specific data and a specific context from which they are able to generate/update the schematic diagrams. Three types of builders are provided with Schematics: Standard builder, Network Dataset builder, and XML builder.

Note:

You can also develop your own custom schematic builder using the Schematics APIs.

Schematic builders and input data

Each predefined schematic builder has been developed to deal with specific input data:

• The Network Dataset builder works from network datasets. It expects solved network analyst layers in input (such as solved route, service area, closest facility, or vehicle routing network analysis task).
• The XML builder works from XML data based on the XMLBuilderDiagram XML Schema Definition file. It is the builder to use if you work with external applications such as industry applications (e.g., Network Engineer), ERPs (e.g., SAP), PLMs (e.g., Matrix One), or analysis packages (e.g., CYME). It allows you to avoid developing specific interfaces that are costing a lot and not easy to maintain.
• The Standard builder works from any GIS feature class/layer or object table.
  • In particular, because it is able to decode geometric network topology, it is especially dedicated to work with GIS feature classes organized into a geometric network. It allows you to quickly generate schematic diagrams in a minimum amount of time from any set of features organized into a geometric network that are currently highlighted in an ArcMap document further to a selection or a trace operation.
  • The Standard builder can also be used to generate schematic diagrams in which whole contents are built from custom queries. These custom queries can operate on any type of database. The main prerequisite for working with custom queries is that the data stored in the database contains the information required to maintain connectivity—that is, the information required to identify the origin (start) and extremity (end) of each link in the diagrams that will be generated.

Note:

Any predefined schematic builder can also be used to generate mixte diagrams that contains:

• Schematic features coming from the specific input data/context with which they are supposed to deal (for example, a solved network analysis layer for the Network Dataset builder, XML data for the XML builder, or a set of GIS features highlighted in a map for the Standard builder)
• Other schematic features built from custom queries that operate on any type of database

Schematic builders and the schematic features they built

Schematic diagrams contain a set of expected types of schematic features. Each type of schematic feature is implemented by a schematic feature class associated with the diagram template. Specifying the schematic feature classes associated with a schematic diagram template is specifying the type of objects the schematic builder that implements those diagrams is supposed to work with when it analyzes the data in input. That is, during the diagram generation, even if the builder is able to analyze and deal with each element in the specified input dataset, it will only build the schematic features related to the elements expected in the diagram.

These schematic feature classes are real feature classes stored in the schematic dataset. When schematic builders work, they store the schematic features they built in those schematic feature classes. The built schematic features are stored in the schematic feature classes for all the diagram life. Then, when Schematics displays the generated diagram, it queries the schematic features from these schematic feature classes.