Importing ArcInfo Models from Visio to Enterprise Architect

Esri's ArcGIS platform supported geodatabase design with Visio 2003, which was useful for creating isolated designs. There are now some limitations however, such as currency of supported tools and the difficulty in tracing isolated Visio drawings upstream and downstream. Have you thought about moving your existing Visio drawings to an enterprise model? Consider some advantages:

  • Your designs become more scalable and matainable
  • You use a more complete, up-to-date UML profile for ArcGIS
  • Exported schemas support the latest versions of ArcCatalog
  • Trace your geodatabase design directly to other business/IT models
  • Reporting for a wide range of stakeholders is supported

And there is no need to remodel your existing Visio drawings from scratch! Here we guide you on how to automate the migration:

Install Enterprise Architect 12.1, Build 1225 (or later)

If you already have this (or a later) version of Enterprise Architect, you may skip this step and proceed to step 2. You can determine which edition and version you are using via Enterprise Architect's Help menu. From the main menu select: Help > About EA...

If you are a registered user, with an earlier version of Enterprise Architect:

  1. Download the latest trial or registered version of Enterprise Architect 12.1:
  2. Run the setup file, which will uninstall any prior version of Enterprise Architect.

To complete the model migration, you need Enterprise Architect Corporate edition or higher.


2. Install the MDG Link for Visio add-in for Enterprise Architect

MDG Link for Visio is a free plug-in for Enterprise Architect that allows you to import Visio files into an Enterprise Architect model. If you have already installed MDG Link for Visio version 1.8 or later, you may skip this step and proceed to step 3.

  1. Download MDG Link for Visio 1.8
  2. Run the setup file and complete the installation.

3. Deploy the model migration script

Save the following file to the VBScript subfolder of your Enterprise Architect installation directory: VBScript-PostProcessImportedVisioArcInfoModel.vbs (Right click and select "Save Link As...")

For example, on a 64-bit windows machine, the default path is:

C:\Program Files (x86)\Sparx Systems\EA\Scripts\VBScript\


4. Import a Visio file into Enterprise Architect using MDG Link for Visio

  1. Create a new, empty Enterprise Architect project. From the main menu, choose: File > New Project. Name the project file and click OK.
  2. When prompted for a Model Pattern, click the Cancel button to exit the Model Wizard. Use the Project Browser to create an empty package instead. You can type any name for this package, which is simply a container for your imported Visio model. Project Browser EmptyProject Browser New View
  3. Select the package you have just created in the Project Browser. New Package
  4. Invoke the Visio Importer by choosing from the main menu: Extensions > Microsoft Visio > Import Visio Documents
  5. You will be prompted for a file location. Browse to the Visio file that you wish to import.
  6. When prompted for the default conversions, select the Class diagram type and Click OK: Choose Default Element Type
  7. During the import process, you may be prompted to enable Macros and ActiveX. This option must be enabled for the import to succeed. When prompted, choose the option to enable macros. Note: Because this dialog can appear behind another window, you may need to use Alt+Tab to make it visible. Enable Macros
  8. The import process can take several minutes to complete, depending on the size of the model. During the import, you may be prompted to activate the busy program. You can click Retry, to resume the process if it stalls temporarily. Switch-Retry Prompt
  9. Once the importer completes, you have the option of saving a detailed report of what was imported. Enterprise Architect's Project Browser will be updated to reflect the imported elements. File Imported Project Browser After Import

5. Migrate the imported model using the migration script

  1. Access Enterprise Architect's scripting window from the main menu: View > Scripting.
  2. Select the "Local Scripts" folder and right-click and run the script: VBScript - PostProcessImportedVisioArcInfoModel.vbs Scripting Window
  3. While running, the script will log information to Enterprise Architect's Output window. On completion, right-click the Output window and choose "Copy All To Clipboard" Output Window
  4. Paste the log text into a word processor.
  5. Note any warnings or errors. If the script identifies errors, you may need to correct these in the original Visio model, then repeat steps 4 and 5.

6. Verify that your model was successfully imported and migrated

If your model has been migrated successfully, most elements under your ArcGIS workspace will be stereotyped according to Enterprise Architect's UML profile for ArcGIS. These stereotyped elements will also have a property sheet that is dedicated to ArcGIS. Check the following to ensure this is the case:

  1. Locate one of the FeatureDataset stereotyped packages in the Project Browser and open its properties (double-click the package in the Project Browser). You should see a property tab labelled "ArcGIS". Clicking this tab should reveal properties similar to those shown below. Package Properties
  2. Locate a RelationshipClass connector on one of the imported diagrams. Double-click the connector on the diagram to view its properties. In the Tagged Values tab you should see properties similar to those shown below. Relationship Tagged Values
  3. Classes stereotyped as Point, Polyline, Polygon etc. should all have a dedicated properties tab for ArcGIS.

Notes:

  • While Enterprise Architect attempts to retain Visio's original diagram layout information, such as connector way-points, generally some tidy-up of diagrams will be necessary after migrating your model. You may be able to apply Enterprise Architect's Diagram Layout tool to help automate some of the tidy-up: Main Menu > View > Diagram Layout. The Digraph, Spring and Box layouts have generally been the most helpful for this purpose.
  • Composite connectors are currently not supported by Enterprise Architect's ArcGIS schema generator.