How Convert Diagram To Features (Schematics) works

Exporting diagrams into shapefiles or feature classes

TheConvertDiagramToFeatures tool creates either shapefiles or feature classes depending on the output location parameter.

• When the specified output location is a workspace or feature dataset, the diagram content is converted into feature classes.
• When the specified output location is a folder, it is converted into shapefiles in a specific subfolder.

Exporting several diagrams in the same feature classes or in different feature classes

Depending whether the Reuse Existing Structure option is enabled or disabled, the Convert Diagram To Features tool exports several diagrams implemented by the same diagram template into the same feature classes/shapefiles or into different feature classes/shapefiles.

Exporting several diagrams based on the same diagram template into the same feature classes/shapefiles

To convert several diagrams into the same feature classes, the Reuse Existing Structure option must be activated.

During the first diagram conversion, if the specified output location is a geodatabase, the tool begins by creating a new feature dataset in the geodatabase. This feature dataset will have the same name as the diagram template name of the diagram being converted. So if the diagram being converted was based on a diagram template named TestTemplate, then this first step will result in a new feature dataset called TestTemplate. Next, it creates feature classes for each schematic feature class that was part of the diagram template, using the same names as the schematic feature class names. So if the diagram template had a schematic feature class named TestFC, then inside the TestTemplate feature dataset you see a new feature class called TestFC. Finally, using the new feature classes, it creates a feature for each schematic feature contained in the converted diagram. If the diagram being converted had 10 features of the type TestFC, then in the new feature class you see 10 features.

During the next conversion of diagrams based on the same diagram template, these feature classes are automatically reused. New features corresponding to the input schematic diagrams' features are added to the existing feature class tables. The new features are differentiated from the previous diagram's feature by a field called DiagramObjectID. So if you were to put these newly converted feature classes in a map, you would need a definition query (based on this DiagramObjectID) on each of the feature class layers to filter down to just one of the diagrams that could potentially be in the converted feature classes.

Note:

The process is exactly the same when the output location is a folder and the Reuse Existing Structure option is activated. The converted diagrams are merged into the same shapefiles (with names corresponding to the schematic feature class names). The shapefiles are stored in a subfolder with a name corresponding to the diagram template name.

Exporting several diagrams based on the same template into different feature classes/shapefiles

To convert several diagrams into different feature classes, you must deactivate the Reuse Existing Structure option.

In this case, if the specified output location is a geodatabase, the tool starts by creating a new feature dataset in it. The name of this feature dataset is the concatenation of the converted diagram's diagram template name and the name of the diagram itself. If you are converting a diagram named Test that is based on a diagram template named TestTemplate, the feature dataset is named TestTemplate_Test.

Next, in the feature dataset, the tool creates feature classes for each schematic feature class associated with the diagram template related to the converted diagram. The names for those feature classes are the concatenation of the schematic feature class names and diagram name. If the diagram template has a schematic feature class called TestFC, then the converted feature dataset has a feature class called TestFC_Test. Finally, it creates a feature for each schematic feature contained in the converted diagram.

Note:

The process is exactly the same when the output location is a folder and the Reuse Existing Structure option is deactivated. The diagrams are converted into different shapefiles (with names based on the concatenation of the schematic feature class names and diagram name). Those shapefiles are stored in a subfolder with a name that is the concatenation of the converted diagram's diagram template name and the diagram name itself.

Understanding the exported information

Each feature contained in the resulting feature class/shapefile is created with the same specific information. The converted fields are detailed in the following sections:

Information stored for any type of created feature

• SCH_ID: The schematic feature identifier
• FeatureCID: The feature class ID of the real feature that is associated with the schematic feature
• FeatureOID: The ObjectID of the real feature that is associated with the schematic feature
• DiagramCID: The unique ID of the diagram template that implements the input schematic diagram (DIAGRAMCLASSID field value in the SCHxD_DiagramClassName)
• DiagramID: The input schematic diagram unique ID (DIAGRAMOBJECTID field value in the SCHxD_DiagramClassName schematic table)
• DiagName: The input schematic diagram name (NAME field value in the SCHxD_DiagramClassName schematic table)
• DiagType: The input schematic diagram template name (NAME in the SCHx_DIAGCLAS schematic table)
• OBJECTID: The unique identifier in the resulting feature class/shapefile
• SHAPE: The SHAPE type

Note:

Most of these converted fields, such as DiagramCID and DiagramID, can then be very useful when working with Schematics Server. They allow you to filter out features per diagram from the resulting tables by using a Layer Query Definition.

Information stored for point features

For a point feature corresponding to a node, or a node on link schematic feature in the input schematic diagram, the following complementary fields are also stored in the resulting feature class/shapefile:

• X: The initial or saved X-coordinate of the schematic feature in the input schematic diagram
• Y: The initial or saved Y-coordinate of the schematic feature in the input schematic diagram
• Rotation: The rotation angle that may have been applied to the symbol, which represents the schematic feature in the input schematic diagram

Information stored for line features

For a line feature corresponding to a link or sublink schematic feature in the input schematic diagram, the following fields are also stored in the resulting feature class/shapefile:

• FROMSCH_ID: The identifier of the schematic origin node for the converted schematic feature link
• TOSCH_ID: The identifier of the schematic extremity node for the converted schematic feature link
• SHAPE_Length: The length of the line feature

Information stored for polyline features

For a polyline feature corresponding to a node schematic feature represented as a container in the input schematic diagram, you find the same converted fields as for a point feature. There is only one additional field, SHAPE_Length, which provides the length of the polyline feature.

Information stored for polygon features

For a polygon feature corresponding to a node schematic feature represented as a container in the input schematic diagram, you find the same converted fields as for a polyline feature. There is one additional field, SHAPE_Area, which provides the area of the polygon feature.

Note:

When the Export All Attribute Features option is activated, you also find all the attributes related to the associated features in the resulting feature classes/shapefiles. So you have all the fields mentioned above plus you also get all the fields from the related real feature as well. So if the real GIS feature had 15 fields, the resulting converted feature has the fields above plus these 15 fields. This is useful for symbology and labeling using these converted feature classes at a later point in time without trying to use a join back to the real features.