Create Project to Export Data

Data for standard exports is retrieved from the corporate GIS database and exported to an XML file that may be imported into your analysis engine or its Vendor API.

Two conditions must be met for a feature to be exported from the GIS. The feature must be selected in ArcMap, and the associated feature class must have the export model name designated by the client. If no model name is designated, all selected features will be exported.

The data exported is determined by how model names are assigned in the configuration section and by the current selection set in ArcMap. Once what is to be exported is determined, it is up to the project you've created to determine how the data is exported. This step determines the how.

In this step, you will create a project (e.g., C#, VB6) that uses the MMSelectionAnalysisAPI class to export data from the GIS. The MMSelectionAnalysisAPI class exposes the interfaces that help you determine how data is exported (e.g., XML, DOM document). The selected set is exported to a specific format based on which IMMXMLData method has been called and the items included in its property set parameter.

Interfaces:
IMMXMLData
IMMAnalysisAPI

CoClasses:
MMSelectionAnalysisAPI

Export Properties

Import to Analysis Engine:
MultiSpeak

Implement the IMMXMLData interface using the method that corresponds to the type of export file you wish to use. Each method has a parameter that uses a property set (IPropertySet). This is where you determine which properties are included in the XML. It is recommended that you export using the ClassModelName and FieldModelName properties and assign model names in the geodatabase. This allows you to limit the features and attributes included in the export and improves performance.

The IMMAnalysisAPI interface allows you to query the state of the Analysis API. This allows you to determine whether the export is enabled and whether the selection has changed.

Import Data: Once Network Adapter has exported, you can convert the data to the format required by your analysis engine and import it. This section discusses importing into CYMDIST, SynerGEE, and MultiSpeak. The required import properties for each analysis engine are included in this section.

Export Load Cases & Import Results: The IMMDistopsWorkspace interface may be used when exporting load case data or importing analysis results into the Network Adapter database. It contains two methods. One to determine whether the export is enabled (i.e., a selected set exists) and another to determine whether the selection has changed since the last export.

MultiSpeak: Selected features are exported to a Network XML document as the return value of the IMMXMLData::ExportDataToDOM method. The property set passed into this method contains the usual export properties in addition to the AddMspConnectivity property which requests that connectivity information required by Engineering Analysis applications be included in the exported XML. This property and its valid values are discussed on the Export Properties page.

MultiSpeak Default Values: The MspDefaults.xml file allows you to define default values for specific fields during export. If a field does not have a value during export and has a default value defined in the MspDefaults.xml file, the default value will be used.

XML Snippet

Copy Code

<DEFAULTS>
  <MSPDEFAULTS noun="ohPrimaryLine">
    <ELEMENT>
      <ELEMENTNAME>condN</ELEMENTNAME>
      <ELEMENTVALUE>1/0_ACSR</ELEMENTVALUE>
    </ELEMENT>
    <ELEMENT>
      <ELEMENTNAME>constr</ELEMENTNAME>
      <ELEMENTVALUE>Default OH</ELEMENTVALUE>
    </ELEMENT>
  </MSPDEFAULTS>
  <MSPDEFAULTS noun="capacitorBank">
    <ELEMENT>
      <ELEMENTNAME>connectionCD</ELEMENTNAME>
      <ELEMENTVALUE>ShuntWye</ELEMENTVALUE>
    </ELEMENT>
  </MSPDEFAULTS>
</DEFAULTS>