Once you have run an EMME/2 simulation using a network that was built by the 2.11 Toolbox, you can import the simulation results into ArcInfo by using the Import program. Import, which should be run from the UNIX prompt, is written in Perl, and builds and runs an AML program to do the importing; therefore it must be run in an environment that has access to both Perl and ArcInfo.
Before running Import, you must "punch" the results of your EMME/2 simulation run using EMME/2 module 2.14. For more information on this procedure, please refer to the EMME/2 documentation. If you want to include extra-attribute information in your network, you will need to copy this information to one of the standard EMME/2 attributes prior to punching, as EMME/2 does not allow these items to be punched with a network.
The Import program will analyze your EMME/2 network, and define item
Running the ProgramIf Import is run with no command line parameters, it will report a brief help message:$ import Syntax: import [-o] <EMME/2 batch file> <shape coverage> <output coverage> -o Overwrite existing coverage<EMME/2 batch file> is the name of the file created by EMME/2 when you punched your simulation network.
<shape coverage> is the name of a coverage that contains shape information about the network to be converted to ArcInfo. During the conversion process, a coverage called shapecov is created, which should be used for this parameter. Note that if you change the configuration or numbering of nodes in EMME/2, new copies of shapecov will not work with older networks. In this case, you should make a backup of shapecov which can be specified on the command line when importing older networks.
<output coverage> is the name of the ArcInfo coverage to be created. If this is the name of an existing file, coverage, or directory, you must specify the overwrite option with the -o parameter.
Structure of the Imported NetworksAfter you have imported an EMME/2 network into ArcInfo, you may notice that the data structure is fundamentally different than that used by the 2.11 Toolbox. In many ways, it very closely resembles that used by EMME/2. For example, all of the imported links are unidirectional, and two-way streets are represented with two co-linear arcs, each "pointing" in opposite directions. Gone too are the _ft and _tf item suffixes found in the 2.11 Toolbox. As each arc needs to represent data flowing in one direction only, these suffixes are no longer needed.
The main reason for using this data structure is to make it easier to create simple EMME/2 style plots than would be possible using a structure similar to the 2.11 Toolbox. As you are unlikely to edit an imported coverage, there seems to be little downside to using this structure.
Creating EMME/2 Style "Bandwidth" PlotsCreating EMME/2 style "bandwidth" plots is relatively easy with an imported coverage. The most important difference between plotting this type of plot in ArcInfo vs. in EMME/2 is that the ArcInfo version will reflect the true shape of the streets, and can be combined with other GIS data, while the EMME/2 version cannot.
A modified version of the following AML routine should create adequate results in most cases, and can easily be made more sophisticated. Note that this example assumes that you have set the map extents and other page setup parameters earlier in the AML. Also, assume that link volume is stored in the item UL3, and that the name of the imported coverage is stored in the variable %cov%./* Simple AML fragment to create crude EMME/2 style plots /* Link volume is stored in UL3, coverage name in variable cov /* To make the bandwidth "bars" appear on the left side of the arc /* (for Britain/Australia), multiply the lineoffset arguments by -1 linesize .1 lineoffset -.05 resel %cov% arc ul3 >= 2000 arcs %cov% clearsel linesize .05 lineoffset -.025 resel %cov% arc ul3 < 2000 and ul3 >= 1000 arcs %cov% clearsel linesize .025 lineoffset -.0125 resel %cov% arc ul3 < 1000 and ul3 >= 500 arcs %cov% clearsel linesize .01 lineoffset -.005 resel %cov% arc ul3 < 500 arcs %cov% clearsel