Importing a CommunityViz 1 scenario into Scenario 360

1. Export the scenario from CommunityViz 1.

2. Start Scenario 360 from your desktop Scenario 360 icon, from the Windows Start menu CommunityViz Scenario 360 option, or from ArcMap.

3. If the Welcome to Scenario 360 window is not open:
   Click the Scenario 360 toolbar menu, click Analysis, then click New.
   -OR-
   Click the Scenario 360 toolbar menu, click Start, then select Create new analysis.
   -OR-
   Click the Start a Scenario 360 analysis toolbar button , then select Create new analysis.

4. Click to select the Create new analysis from option and click the CommunityViz 1 Scenario option.

5. Click the Browse for file button and navigate to the directory and file saved in the CommunityViz Scenario Export process.  The file will have the format scenarioname.XML and will be located in the CommunityViz 1.x scenario folder for the scenario you exported.  Select the file and click Open.

6. Click Next.

7. If you wish to provide a new name and/or description for your analysis, type the new information into the fields provided.  If there was a description in the CommunityViz 1.x scenario, this description will be preserved as part of the import process.

8. If you wish to change the location to save the analysis files, click the Browse for file button and navigate to the new directory.

9. Click Next.

10. A summary window will be displayed.  Once you have finished reading the summary, click Finish.

11. The import process will begin.  Depending on the size and complexity of your CommunityViz 1 scenario, this process may take a long time.  A progress bar will be displayed indicating the current process operation and percent completion status.

The import process includes the following:

1. Creates a new Scenario 360 analysis with one base scenario.

2. Changes formulas to reflect Scenario 360 formula syntax.

3. Resolves data sources for layers and tables in several ways:

1. Copies all dynamic (automated) layers into the Scenario 360 geodatabase.

2. Copies all other feature layer source files to the \Data subfolder in the analysis directory (note: coverages will not be copied).

3. Prompts you to copy or reference all other layer types (e.g., images).

4. Prompts you to locate any data sources not found in the CommunityViz 1 scenario folder.  You will be given a choice to:

• Browse for the missing layer

• Skip the layer

• Skip all remaining missing layers (don't prompt again)

• Cancel the entire import process

4. Loads data layers and tables into ArcMap

5. Converts CommunityViz 1 scenario components to Scenario 360 analysis components, using the following definitions:

6. Creates a summary report.

12. After import is complete, a report window will be displayed describing import problems, if any.  Note that reported import problems are not necessarily errors.  Some complicated scenarios and formulas cannot be imported completely.  Examples of scenario components that will not import include:

• Custom scripts

• Some Avenue methods (e.g., ".AsString")

• Functions with non-standard format (e.g., Max function with left and right operators)

• Certain specialized layer types may not be imported automatically

All import issues will be displayed in the report.  Most problems can be resolved manually by adding missing layers and unique symbology, or by editing mistranslated formulas.

13. Once you have finished reading the import information, click OK.  A copy of the report is written into the Reports folder for the new analysis.

During export, object names (themes, indicators, tables, constraints, variables, constants, attributes, scenarios) are not turned into valid XML text.  So, if one of these names contains an XML control character (& < > ' ", newline, tab), then the XML will contain incorrect information, or may not be able to be imported.  To fix this problem, open up the XML in an editor and change & to &amp;, < to &gt;, > to &lt;, etc.