15 th International EMME/2 Users’ Group Conference October 18 – 20, 2000 Vancouver, B.C
Integration of EMME/2 and CORSIM
Hamid Iravani
Wilbur Smith Associates
1145 Market Street, Tenth Floor
San Francisco, CA 94103
(415) 436 9030
hiravani@wilbursmith.com
Abstract
Development of automated data exchange between travel demand forecast models and traffic simulation models can assist engineers and planners in closing the gaps and inconsistencies that exist between transportation planning analysis and detailed engineering solutions to problems. Data exchange between both tools will also lead to more precise traffic assignment results. This paper will identify a user friendly, menu driven EMME/2 macro named “EMSIM”, which was developed to establish relationships between features of EMME/2 and CORSIM traffic simulation software. This macro takes advantage of features that exist in both packages for data processing and analysis, while it helps EMME/2 users to provide data in a graphical editor to be used as input for the CORSIM model.
Maximizing automation of data entry and data processing through program development can significantly help to accomplish projects more efficiently and quickly, while reducing possible errors. Another advantage of automation relates to economy of scale; once the program is built, it could be used for many other similar projects. Besides using many powerful options in EMME/2, EMSIM also uses a customized graphical editor tailored for CORSIM data needs, and also takes advantage of extensive capabilities of the EMME/2 Network Calculator module to automate data input for various attributes. After exporting data out of EMME/2, the output will then be processed using the AWK programming language to develop input for CORSIM.
Thus far, the macro has been used to develop CORSIM input files for two different projects, including a traffic impact study of Downtown Rochester, Minnesota and a Downtown Access and Mobility Study in Austin, Texas.
Introduction
Travel forecasting models are used to project changes in a transportation system. These models are applied to test different alternatives and to analyse impacts of regional developments. Data management and processing for travel demand models are computationally intensive. As computer processing power has improved, more detailed analyses have become applicable. It is now possible to develop more disaggregate models, including more refined zone systems and detailed transportation networks. However, travel demand models are spatial and designed to predict changes in travel and utilization of the system at a larger scale. The output of these models are used for decision making at the planning stage. Traffic simulation is the next step that is usually performed to test various alternatives in a more microscopic scale. In this stage other variables can be included to account for spot location impacts, as opposed to area wide changes.
Traffic simulation tools help engineers to replicate transportation systems at the detailed level of individual cars. Since simulation is a detailed oriented task, it is also very data intensive. Part of the input requirements for simulators are the output of travel demand models, however, traditionally links between these tools are not developed in a single software package. Integrating these tools can significantly reduce data input requirements. On the other hand, traffic simulators could function as an extension of travel demand models. Simulators also generate detailed results at the intersection level, including delay and optimised signal timing configurations. These results could then be used and looped back into travel demand models again to test changes in traffic assignment results. This process can improve the reliability of traffic assignment models through an iterative process, to the extent that model output can be fed into simulation models and the output can be used again to improve the assignment model. This process will repeat until convergence of the results is obtained. Therefore, building a “bridge” between both tools can improve output results generated for both applications.
EMSIM Basics
EMSIM is a menu driven, user friendly macro developed to link EMME/2 with CORSIM and includes the following features (1):
-
Graphical editor designed to input CORSIM attributes
-
Capability to compute some of the attributes automatically
-
Capability to plot input data automatically
-
Takes advantage of other useful macros developed by EMME/2 Support Center while in EMSIM. One of these macros includes adjusting OD matrix based on turning volume or link volume counts on selected locations.
-
Automatically exports ASCII files in required CORSIM input file format, using a built in AWK programming language (2)
EMSIM Features
-
There is an existing CORSIM graphical editor (ITRAF) but it does not provide any link to travel demand models; also many users in many cases develop their input data in ASCII format (“Record Type Files” in CORSIM lingo). EMSIM provides users with a graphical editor, in which each node or link has its own associated fields for different "Record Types" and user can spatially relate data within the geographical area;
-
EMSIM automatically calculates many link or node attributes needed as input for different record types, thus eliminating time consuming data entry typically done by the user;
-
EMSIM can import a DXF file and user could start developing the network based on the imported file;
-
In many cases there is a regional model available in EMME/2 format and EMSIM can use the model to build CORSIM Record Type Files;
-
In cases where the regional model encompasses a bigger area than a CORSIM project requires, EMSIM lets the user pick an area to keep and automatically deletes the rest of the network. This eliminates the requirement for the user to manually delete all the unnecessary links and nodes;
-
If the original model is in TRANPLAN, a program can be run to quickly convert the TRANPLAN roadway network ASCII file into EMME/2 format and then run EMSIM;
-
To prevent the user from having to manually input data, the following fields of data can be automatically calculated and created by EMSIM:
Record Type 11 (Surface Street Link Description)
Entry 1 - Link's upstream node number
Entry 2 - Link's downstream node number
Entry 3 - Link Length (feet)
Entry 18 - Downstream node k that receives left turning traffic.
Entry 19 - Downstream node m that receives through traffic.
Entry 20 - Downstream node n that receives right turning traffic.
Entry 21 - Downstream node -d (left) or +d (right) that receives diagonal traffic.
Record Type 19 (Freeway Link Geometry)
Entry 1 - Upstream node number i of subject link (i,j)
Entry 2 - Downstream node number j of subject link (i,j)
Entry 3 - Downstream node number k of link (j,k), which receives through-movement traffic from subject link (i,j)
Record Type 195 (Node Coordinates)
Node coordinates are automatically developed
-
EMSIM can also take all turning movements from a regional model and automatically fill the following fields, preventing the user from having to both enter the data and calculate the percentage of turning volumes on each approach:
Record Type 21 (Surface Street Turn Movements)
Entry 3 - Percentage of traffic (or vph) turning left to node k
Entry 4 - Percentage of traffic (or vph) going through to node m
Entry 5 - Percentage of traffic (or vph) turning right to node n
Entry 6 - Percentage of traffic (or vph) turning diagonally to node -d (left) or node +d (right)
Entries 7 through 10 relating to turn prohibition.
Record Type 25 (Freeway Turn Movements)
Entry 3 - Downstream node number k of link (j,k), which receives through traffic from subject link (i,j)
Entry 4 - Percentage of vehicles or the total number of vehicles that have a through movement to link (j,k)
Entry 5 - Downstream node number l of an off-ramp that receives traffic exiting from subject link (i,j)
Entry 6 - Percentage of vehicles or the total number of vehicles that exit at the off-ramp link (j,l)
-
If a regional model is not available, any number of observed turning movement data could be taken, and based on those, the rest of the turning movements at intersections in the entire network could be estimated automatically. This procedure links to the macro built by Heinz Speiss called demadj22.mac (3). Then based on the generated numbers, Record Types 21 and 25 can quickly be built. This procedure uses an algorithm in which a trip table can be estimated based on turn movements and/or link traffic volumes. As a result of this process a demand matrix is also built and the user can perform “what if” analyses and run CORSIM accordingly;
-
Entering link volumes for Record Type 50 can easily be built using the program;
-
Using future variables, EMSIM can take advantage of the assigned future trip table and build the corresponding Record Types accordingly;
-
Finally, since EMSIM is being developed in the EMME/2 environment, CORSIM user can also take advantage of extensive EMME/2 features for their analysis and in presenting the analysis result. Some of the advantages include plotting volumes of the study area network, or any other node or link attributes, as well as features regarding turning movements. This integration (EMME/2 + CORSIM = EMSIM) will enable users to do alternative analysis and generate reports for different alternatives (comparing volume, values associated with speed, VMT, VHT, etc.);
-
Numerous error detection messages are built into EMSIM to communicate with the user; and,
-
When the analysis is done, the EMSIM menu allows the user to export data in CORSIM format, with all data for different CORSIM Record Type Files in their appropriate columns.
EMSIM Screen
When EMSIM is activated, the following screen appears:
This screen will assure the user that the correct scenario is being activated. The user has the option to change the scenario number at this level by answering yes to the question. The next screen will include the main menu.
Main Menu
While on the above screen, the user can see the name of the project and scenario automatically, that is already defined in EMME/2’s data bank.
Create Subnetwork
The following shows the entire Rochester, Minnesota network.
The above network covers an area coded in a regional model which is much larger than required for the CORSIM model. It also includes many centroid connectors that should not be coded in CORSIM. The user has the option to automatically delete centroid connectors and part of the network and keep just the CORSIM study area. By choosing first option in EMSIM’s main menu, the user will be prompted to the next screen as follows.
Based on answers provided by the user, part of the network will be kept, using node number 1 as the center with a radius of 5 miles.
EMSIM generates the new subnetwork in a different scenario (scenario 91 in the above example).
When study area network is defined the user is ready to select option 2 in the main, menu, which is creating CORSIM files.
By pressing option 2 of the main menu user will be prompted to the next screen.
The above screen will enable the user to quickly create attributes needed for various CORSIM Record Types.
The user will be prompted to a sub menu for various Record Types to choose options to calculate some of the attributes automatically, eliminating the need to manually enter the data. For instance by choosing option 2 the next screen will be displayed as follows.
After activating the above options the next screen will be displayed for data entry. As shown in the following network from Downtown Austin in Texas, length and downstream node numbers for through, right, left and diagonal nodes are entered in their link attributes automatically. Also as the user modifies the network each link turns red, making it easy for the user to trace the modifications. If the user chooses to stop and returns to the program later, all links that are already modified will still be shown in red.
When the user selects to input turn volumes, if the model already has those volume then the option for transferring the turn attribute to link attribute can be selected, to have all the values moved in link fields while converted to percentages. Otherwise the user will be prompted to the following screen to manually enter the turn volume. In the following example all turn volumes are entered in up2 field belonging to node 479.
Since CORSIM requires turn volumes in percentages and entered on links, EMSIM lets the user automatically transfer all the turning volumes in their link attributes as node 479 in the above example is transferred into it’s associated links in percentages. In this example turning volume was transferred from model, then EMSIM converted the result to percentages in links. Below displays link 512 to 479, showing 85% going through, 6%turning left and 9% turning right.
After all attributes are inputted either manually or automatically, the user is ready to export all data in CORSIM format.
In the main menu, the option for exporting data will lead the user to the following screen. This will batchout different link or node attributes and using an external AWK program developed for this purpose, the EMME/2 output will be converted to CORSIM format input files.
Conclusion
As a consequence of development of an EMME/2 macro called EMSIM, integration of EMME/2 with CORSIM has now become possible, A user with minimal training on EMSIM can run the program to develop CORSIM input files. EMSIM is being developed by applying the advance EMME/2 macro language features in a user friendly, menu driven context. Many error detection messages are also created in the macro to make the program communicate with the end user. Since many of the fields are also generated through an automation process, error made by users are minimised. Using EMSIM also reduces the time spent for many hard and time consuming tasks. EMSIM allows users to take advantage of features already built in EMME/2 software. An area to consider for further research is using functions to estimate signal configurations in EMME/2 which could be exported into CORSIM and looped back into EMME/2 again through an iterative process until convergence is reached (4).
References
-
EMME/2 User’s Manual, Software Release 9.2. INRO, Montreal, Quebec, Canada, Ninth printing, 1998.
-
CORSIM, TSIS, and TRAFVU, Users Guide – CORSIM Version 1.03. Kaman Sciences Corporation, Colorado Springs, CO, 1997.
-
Spiess H. (1990b). A gradient approach for the O-D Matrix Adjustment Problem. Publication 693, Centre de recherche sur les transports, Université de Montréal.
-
Aashtiani H. and Iravani H. Use Of Intersection Delay Functions To Improve Reliability Of Traffic Assignment Model. Tehran, Iran, 1998.
Share with your friends: |