Beruflich Dokumente
Kultur Dokumente
user’s
guide
prepared for
prepared by
April 2001
user’s guide
prepared for
prepared by
April 2001
MARC ArcView GIS Conflation System of EMME/2
Transportation Model to CMS Street Network
Table of Contents
List of Figures
1.0 Introduction
The ArcView conflation software has been developed because of the need to relate the
Kansas City ArcView Congestion Management System (CMS) network to the EMME/2
transportation model network. This system will allow the CMS network to display
EMME/2 network data and attributes, perform other analytic functions outside the
EMME/2 modeling system and to use attribute data from the CMS layer as inputs into the
EMME/2 transportation model. The relationship will be based on a unique identifier
created from each EMME/2 model network link and transferred to the representative
street segment(s) in the CMS conflation.
An “A” node and a “B” node number identify every model network link in the MARC
EMME/2 transportation model and combining the node numbers of each link will create a
unique “link-ID.” In the transportation model each network link as two directions, “A”
node to “B”node and a “B”node to “A”node (see Figure 1.1). If the link is specifically
defined as being a one-way, it will only have an “A”node to “B”node link identifier. For a
bi-directional link, the link-ID is created based on the following rules:
The first step in creating this relationship is to define, “by viewing,” which EMME/2
model links correspond to the CMS street segment(s). After this is determined, the unique
model network link identifier is transferred to the representative CMS street segment(s).
The transfer process will add the “A to B” and “B to A” link identifier to the CMS street
segments in the database fields “AB_Link_ID” and “BA_Link_ID.” If the EMME/2 model
link is a one-way link, only the “A to B” link identifier will be added to the CMS street
database.
The purpose of relating these two databases is to preserve the EMME/2 transportation
model link attributes. The relationship is a one to many relate, meaning that one
EMME/2 model link can be related to many CMS street segments (see Figure 1.2).
However, there can never be multiple model link-IDs related to one CMS street segment.
In this case the CMS street segment needs to be split to preserve this relationship (see
Figure 1.3).
This system was designed and developed using ArcView GIS v 3.2 on the Windows 2000
Platform. The software and accompanying programs are stored in the ArcView 3.2 project
file. The system requirements are listed below.
Intel Pentium II
Windows NT/2000/98
64MB RAM
SVGA
ArcView 3.2 with Dialog Designer Extension
4. In the System Properties dialog box, click on Advanced, then Environment Variables.
5. Click New for System and User Variables In the Variable text box type: MARCPATH.
6. In the Value text Box type: “path on your system where the CD files were copied to
e.g., C:\CONFLATE.”
Next start the ArcView GIS 3.2 software. The following dialog box will appear.
Choose the radio button to open an existing project and click OK. Use the standard open
project dialog box (see Figure 4.1) to navigate to the location where the files from the CD
were copied and highlight the project “Conflate.Apr,” and click OK.
The project will open to a custom view (see Figure 4.2) created for the conflation process.
The conflation view provides a user interface to the conflation features and displays the
updated GIS coverages.
The program has several customized user interfaces designed for the specific purpose of
accomplishing the conflation task. These include a custom legend, a toolbar and
conflation tools.
The legend has been predefined so that the user is able to discern what has been conflated
or transferred. The user may change the color specifications by using the legend editor in
ArcView. See ArcView User Guide for more information. Figure 5.1 shows the default
legend set-up.
Model Nodes
The model nodes theme is provided for defining where a model link begins and ends.
This theme exists purely as reference by the user.
CMS Streets
The street theme is the GIS street database provided by MARC. This theme has two color
distinctions. These provide an easy way for the user to determine which street segments
have link-IDs assigned and which do not.
• Transferred – The color black represents street segments that have had model link-IDs
transferred to them.
• Not Transferred – The color green represents street segments that have not had link-
IDs transferred to them.
Model Network
This theme is the model network output from the MARC EMME/2 software package. It is
geo-rectified to match the CMS street network as closely as possible. This theme has two
distinct color classifications to assist the user.
• Transferred – The color blue informs the user that the link-ID has been transferred to a
CMS street segment.
• Not Transferred – The color red informs the user that this link-ID has not been
transferred to a CMS street segment.
In ArcView, the user can only select features of an active theme. A theme is active if a
raised box appears around the theme in the legend. To make a theme active, click on the
desired theme in the legend. To make more than one theme active at a time, hold down
the “Shift” key. Figure 5.2 shows that the model links theme is the active theme. Note, the
raised box around the model links theme.
Active
Theme
The custom toolbar will open automatically when the system is started. The toolbar
consists of two sections, “AV tools” and “Transfer.” “AV Tools” are for operations like
zooming and panning. “Transfer Tools” are used to transfer the EMME/2 model network
link-IDs to the CMS street database and to split the CMS street segments. Figure 5.3
shows the custom toolbar.
These tools give the user the ability to accomplish a variety of tasks including, identify,
zooming, panning, and selection of features. These tools are part of ArcView’s default
tools and are organized on the custom toolbar for ease of use. A brief explanation of these
tools will be given. However, for further reference please consult the ArcView Guide.
Identify Tool
This tool allows the user to click on a feature in the active theme and return all of the
attribute data for that feature.
Pointer Tool
The pointer tool is a generic tool that acts as a cursor for selecting graphics.
Zoom In Tool
The zoom in tool allows the user to zoom in to an area by clicking or by creating a
rectangle by dragging the tool.
The zoom out tool allows the user to zoom out to an area by clicking or by creating a
rectangle by dragging the tool.
Pan Tool
The pan tool allows the user to pan to a new location in the map window.
Select Tool
The select tool is used to select features from the active theme. This tool will be used for
selecting model network links and CMS street segments to transfer the link-ID.
The transfer tools have been designed for easy transfer (conflation) of the model network
link-IDs to CMS street segment(s).
The split segment tool is designed to split one CMS street segment to create a consistent
topology with the model network. This tool is similar to the ArcView standard split line
tool, but has been modified for the purpose of this project.
Transfer A to B Tool
The transfer tool allows for the transfer of the AB and BA link–IDs in the Model
Network to the CMS street layer. This tool will work properly only when one model link
is selected and at least one CMS street segment is selected.
Since the CMS street network and the EMME/2 model link topologies do not correspond
to each other exactly, the system has been designed for two types of transfer situations.
The basic transfer process allows the user to use the Select tool to choose one EMME/2
model network link, and then use the select tool again to pick all the corresponding CMS
street segment(s). It is possible that more than one CMS street segment represents a
model link. However there can not be multiple model links representing one CMS street
segment. When the appropriate features are selected, the transfer tool is used to transfer
the model network link-ID to the CMS street database. Next, a description of the step-by-
step transfer process, and examples are provided.
1. Make the EMME/2 model network the active theme by clicking on it in the legend.
2. Use the Select tool to highlight the model link. With the select tool a link can be
selected by pointing and clicking or making a box and dragging. Figure 6.1 shows the
result of a model link selected. The model link will turn yellow when selected (this is
the default ArcView selection color).
4. Use the Select tool to choose the CMS street segment associated with the model link
selected in Step 2. Figure 6.2 shows an EMME/2 model link and a CMS Street
segment selected.
6. When the transfer is complete, the CMS street segment(s) color changes to black, and
the EMME/2 model network link changes color to blue as indicated in the legend.
The color change allows the user to easily identify which CMS streets have had a
model link-ID transferred. Figure 6.3 shows an example of a completed transfer.
The EMME/2 model network and the CMS streets topologies are not consistent, therefore
it is necessary to split the CMS Street segments to adhere to the EMME/2 model network
topology. Figure 6.4 shows that the beginning and ending points of the EMME/2 model
network link do not line up with the CMS street segment. In this particular case there are
two model links that span the length of one CMS street segment.
Because is not possible to transfer multiple EMME/2 model link-IDs to one CMS street
segment, it is necessary to split the CMS street segment before transferring the EMME/2
model network link-ID. The process is given below.
2. Select the Split Line tool from the Transfer tools section of the Toolbar.
3. A dialog box will prompt the user to draw a line segment through the CMS street
segment. To draw the line click the left mouse button to mark the starting point, drag
the line through the CMS street segment and double click the left mouse button mark
the end of the line.
4. After the line segment has been drawn, a dialog box will ask if the split is correct. If
yes is clicked, it will be saved, otherwise it will not be saved. Figure 6.5 shows a
successfully split link.
Now that the CMS streets and the EMME/2 model network topology are consistent, the
link-ID for each model link is transferred using the Basic Transfer method outlined
previously. The line segment used to split the CMS street segment will remain in the view
and acts as a new CMS street node. At the end of the conflation process the line segments
can be removed by selecting the links that have no attributes, setting the CMS theme to
editable and deleting the selected records.
In the regular view there are two custom buttons that allow the user to import the
EMME/2 model network and result files as shapefiles.
1. Select the “N” button. A message box will prompt the user to select an EMME/2
network file.
2. Next, the user is prompted to supply file names for the resulting node and link
shapefiles. When the process is complete, these shapefiles will be loaded into the
view.
1. Select the “R” button. The user will be prompted to identify the CMS layer.
2. Next, the user is prompted to supply a filename for the resulting shapefile. A new
shapefile is created.
3. Next, the user is prompted to select the attribute fields from the result shapefile that
will be attached to the CMS layer. The result file will appear in the view as a shapefile.
The selected result fields will be present in the CMS attribute table for both the AB and
BA link IDs.
If you have comments or questions regarding the operation of this software, contact:
Anthony Kroon
Cambridge Systematics, Inc.
150 Cambridge Park Drive, Suite 4000
Cambridge, MA 02140
Phone: (617) 354-0167
Fax: (617) 354-1542
E-mail: ajk@camsys.com