Exercise 2: Creating a multimodal network dataset

Available with Network Analyst license.

Complexity:

Beginner

Data Requirement:

ArcGIS Tutorial Data for Desktop

Data Path:

C:\ArcGIS\ArcTutor\Network Analyst\Tutorial\Exercise02

Goal:

Create a multimodal network dataset

In Exercise 1, you learned how to create a network dataset representing a road network; however, travelers and commuters frequently use multiple modes of transportation, such as walking on sidewalks, driving on road networks, and riding on trains. Goods also travel on multimodal networks. In this exercise, you'll create a multimodal network dataset from multiple feature classes within a feature dataset.

Note:

The data for this exercise and the other exercises in the Network Analyst tutorial is available on ArcGIS.com. After downloading the data, you can extract it wherever you like. It may be helpful, however, to extract it to C:\arcgis\ArcTutor since the tutorial refers to this path as the default location for the data.

Starting the New Network Dataset wizard

1. Start ArcCatalog.
2. Enable the ArcGIS Network Analyst extension.
   1. Click Customize > Extensions.

      The Extensions dialog box opens.

   2. Check Network Analyst.
   3. Click Close.
3. If you don't already have a connection to the Network Analyst Tutorial folder, you need to create one by following the substeps below.
   1. On the Standard toolbar, click the Connect To Folder button .

      The Connect to Folder dialog box opens.

   2. Browse to the folder with the Network Analyst tutorial data.

      The default location for the tutorial data is C:\ArcGIS\ArcTutor\Network Analyst\Tutorial.

   3. Click OK.

      A shortcut to the folder is added to Catalog Tree under Folder Connections.

      

4. In the Catalog Tree, expand ...\ArcTutor\Network Analyst\Tutorial > Exercise02 > Paris.gdb.
5. Click the Transportation feature dataset.

   The feature classes it contains are listed on the Contents tab of ArcCatalog.

6. Right-click the Transportation feature dataset and click New > Network Dataset.

   

   The New Network Dataset wizard opens.

Naming the network and selecting source feature classes

1. Type ParisMultimodal_ND as the name of your network dataset.

   

2. Leave Choose a version for your network dataset set to the latest version.

   This option is useful if you need to share your network dataset with people who use older releases of ArcGIS. They will be able to open the network dataset that you create and share when you choose a version that is less than or equal to their ArcGIS release number. The drawback of doing this, however, is you won't be able to include any new network dataset functionality that was introduced in later releases of ArcGIS—controls in the New Network Dataset wizard to add that functionality will be disabled. If you don't need to share a network dataset, or the people you share with use the same ArcGIS release as you, choosing the latest version is the best option.

3. Click Next.

   The wizard page for choosing the feature classes that participate in the network dataset is displayed.

4. Click Select All to select all the feature classes to participate as sources in the network.

   

5. Click Next.
6. Click Yes to model turns in the network.

   Although there are not any turn feature classes for this network, choosing Yes allows the network dataset to support global turns and gives you the option of adding turn features anytime after the network is created.

   

7. Click Next.

   The page for setting connectivity is displayed.

Setting the connectivity and elevation policies

Connectivity in the ArcGIS Network Analyst extension begins with the definition of connectivity groups. Each edge source is assigned to exactly one connectivity group, and each junction source can be assigned to one or more connectivity groups. A connectivity group can contain any number of sources. How network elements connect depends on which connectivity groups the elements are in. For example, two edges created from two distinct source feature classes can connect if they are in the same connectivity group. If they are in separate connectivity groups, the edges won't connect unless they are joined by a junction that participates in both connectivity groups.

You will create connectivity groups in the following steps:

1. Click Connectivity to set up the connectivity model for the network.

   The Connectivity dialog box opens.

2. Click the Group Columns up arrow once to increase the number of connectivity groups to 2.

   A column for the second connectivity group is created in the Connectivity Groups table.

In this exercise, connectivity group 1 represents the metro system, and group 2 represents the street network.
3. Click the Streets row and check the check box under the column labeled 2 to move the Streets source to connectivity group 2.
4. Click the Metro_Entrances row and check the check box under the column labeled 2 to include the source feature class in groups 1 and 2.

   Metro entrances are points of transfer between the streets and the walkways that lead to the metro stations.

Each feature of Metro_Entrances is coincident with a vertex of the streets feature class. However, the streets feature class has a policy of endpoint connectivity. Since the metro entrances need to be connected to the streets at the coincident vertex, you must set Metro_Entrances to override the default endpoint connectivity of the streets.

5. Change the Connectivity Policy of the Metro_Entrances row from Honor to Override.

   

6. Click OK to return to the New Network Dataset wizard.
7. Click Next.

Elevation settings in a network dataset further define connectivity. To understand why, assume two edges have coincident endpoints in x and y space but have different elevations (one endpoint is higher than the other). Furthermore, assume their connectivity policy is set to Endpoint. If elevation is ignored, the edges connect. However, if elevation is considered, they won't connect.

There are two ways to model elevations: using true elevation values from geometry or using logical elevation values from elevation fields.

8. No elevation data exists for this dataset; therefore, click None.

   

9. Click Next.

   The wizard displays the attributes of the network dataset.

   

Removing an attribute

Network attributes are properties of the network that control navigation. Common examples are cost attributes that function as impedances over the network and restriction attributes that prohibit traversal in both directions or one direction, like one-way roads.

Network Analyst analyzes the source feature class (or classes) and looks for common fields like Meters, Minutes (FT_Minutes and TF_Minutes, one for each direction), and Oneway. If it finds these fields, it automatically creates the corresponding network attributes and assigns the respective fields to them. (This can be viewed by clicking Evaluators.)

Network Analyst automatically configures five attributes for the Paris streets data: Hierarchy, Meters, Minutes, Oneway, and Road Class.

Although you could leave the hierarchy attribute on the network dataset, this short set of steps demonstrates how to remove a network attribute by removing Hierarchy.

1. Click Hierarchy.
2. Click Remove.

   Now the network is left with four attributes.

Verifying and creating network attributes

One goal for this network dataset is to model both pedestrian times and drive times. When performing analyses on the network, this allows you to choose between the two time costs. For example, you can choose to answer a question such as, What's the quickest route from point A to point B for a pedestrian who can walk along streets and ride the metro? or What's the quickest route for someone who's driving a car? To accomplish this, you must set up two time-cost attributes (PedestrianTime and DriveTime) and a restriction attribute (DrivingAVehicle).

The Minutes attribute that Network Analyst automatically detected in the source data represents drive times, so you can change the name to something more appropriate.

1. Select the Minutes row, click Rename, type DriveTime, and press Enter.

   

Next, you will create the PedestrianTime attribute.
2. Click Add.

   The Add New Attribute dialog box opens.

3. Type PedestrianTime in the Name text box.
4. Set the Usage Type to Cost.
5. Change Units to Minutes.
6. Set the Data Type to Double.

   

7. Click OK.

   The Add New Attribute dialog box closes, and PedestrianTime is added to the list of attributes.

Next, you will create the DrivingAVehicle restriction attribute.
8. Click Add.

   The Add New Attribute dialog box opens.

9. Type DrivingAVehicle in the Name text box.
10. Set the Usage Type to Restriction.
11. Leave Restriction Usage set to Prohibited so that travel is never allowed on the restricted elements when the restriction attribute is used in an analysis.
12. Leave Use by Default checked.
13. Click OK.

    The Add New Attribute dialog box closes, and DrivingAVehicle is added to the list of attributes.

The three cost attributes—Meters, DriveTime, and PedestrianTime—and the new restriction attribute have yellow warning symbols that alert you to potential problems with the evaluators, which specify how the values of network attributes are calculated.

In the next four sections, you will configure the evaluators for each network attribute.

Configuring the Meters evaluator

You will set up various evaluators in this section and the following sections. The Meters evaluator calculates the distance cost for edges in the network; that is, it determines how long the edge is.

1. Select Meters, and click Evaluators.

   

   The Evaluators dialog box opens. Here you can view and edit the evaluator type and its value for each source in the network. You can see that junction and turn sources always have one associated evaluator, but edge sources have two: one for each direction of travel (the from-to and to-from directions).

Network Analyst inspects all source feature classes and tries to automatically assign evaluators for the Meters attribute. In this case, it discovered that the Metro_Lines and Streets sources had a field named Meters, so it set up evaluators to pull values from those fields. The same length values are assigned to the from-to and to-from directions of the edge sources.

Network Analyst was unable to find fields for meters in the Transfer_Stations and Transfer_Street_Station sources. Hence, a warning symbol is present to indicate there is a potential problem.

2. While pressing the Shift key, click the Transfer_Stations From-To row and click the Transfer_Street_Station To-From row.

   The four rows with the warning symbols are selected.

3. Right-click any of the selected rows, and click Type > Field.

   

   The warning symbols change to red error symbols, which indicate an incomplete assignment of values for the field evaluator.

4. With the four rows still selected, right-click any one of them, and click Value > SHAPE_LENGTH.

   

   This assigns values from the SHAPE_LENGTH field in the selected source feature classes to the Meters attribute for their associated network edge elements.

5. Click Apply.

   The Meters network attribute is configured to get length values. For the network elements created from Metro_Lines, Streets, Transfer_Stations, and Transfer_Street_Station sources, the attribute values are respectively pulled from their Meters, METERS, Shape_Length, and SHAPE_LENGTH fields.

Configuring the DriveTime, Oneway, and DrivingAVehicle evaluators

Since automobiles should travel on streets and obey traffic laws, the evaluators for the various sources should be set up accordingly. They should also model appropriate speeds or driving times.

1. From the Attribute drop-down list, choose DriveTime.

   The DriveTime values for the Streets source have been populated automatically by Network Analyst; however, the other edge sources display warning symbols because they don't have values assigned. These sources need evaluators.

2. Make sure that all the rows with a warning symbol (Metro_Lines, Transfer_Stations, and Transfer_Street_Station) are selected.

   If they aren't selected, select them by clicking one row and pressing the Ctrl key while clicking the other rows.

3. Press the Ctrl key and click Metro_Stations to add it to the selection.
4. Right-click any one of the selected rows, and click Type > Constant.

   

   The same rows remain selected, and their evaluator type changes to Constant.

5. Again, right-click one of the selected rows, but this time click Value > Properties.

   The Constant Value input box appears.

6. Type -1, and press Enter.

   

   The values for all the selected rows change to -1.

   

7. Click Apply.
Network Analyst treats any elements that have a cost value of -1 as restricted. So whenever the DriveTime attribute is used as impedance in network analyses, these sources are not traversable. But the best way to model prohibited elements is with a restriction attribute, such as the DrivingAVehicle attribute, which you will configure next.
8. From the Attribute drop-down list at the top of the Evaluators dialog box, choose DrivingAVehicle.

   The Attribute Values frame now displays the evaluators for the DrivingAVehicle network attribute.

9. Press the Ctrl key and click all of the edge source rows: Metro_Lines, Transfer_Stations, and Transfer_Street_Station, for both directions of travel. Leave the two Streets rows and all the junction source rows unselected.
10. Right-click any one of the selected rows, and click Type > Constant.

    The same rows remain selected, and their evaluator type changes to Constant.

11. Again, right-click one of the selected rows, but this time click Value > Use Restriction.

    Travel on network elements created from the selected rows will be prohibited when using the restriction attribute, so use this restriction to help model the travel of a car, truck, or other motor vehicle.

The Oneway attribute is also a restriction attribute. It models the one-way traffic restrictions that drivers are required to follow. Later, when you perform an analysis using DriveTime as the cost, you should enable the Oneway restriction so the resulting routes respect one-way streets. Alternatively, when modeling the movement of a pedestrian, you shouldn't use the Oneway restriction, since pedestrians are free to walk in the direction they choose.
12. From the Attribute drop-down list at the top of the Evaluators dialog box, choose Oneway.

    The Attribute Values frame now displays the evaluators for the Oneway network attribute, which has automatically been assigned values for the Streets source.

    The sources related to the metro system don't need one-way restrictions.

13. Click either one of the Streets rows, and click the Evaluator Properties button .

    You can see the expression used to determine whether a street is one-way.

14. Click Cancel to return to the Evaluators dialog box.

Configuring the PedestrianTime evaluator

The PedestrianTime network attribute represents the time it takes a pedestrian to travel on the network. In this set of steps, you will assign appropriate travel times for a pedestrian who can ride the metro system or walk along streets.

1. From the Attribute drop-down list at the top of the Evaluators dialog box, choose PedestrianTime.

   The rows for the following sources should already be selected: Metro_Lines, Transfer_Stations, and Transfer_Street_Station.

2. Right-click one of the selected rows, and click Type > Field.
3. Again, right-click one of the selected rows, but this time click Value > TRANSITTIM.

   The TRANSITTIM fields store the time costs for a pedestrian to use the transit system. The streets also need pedestrian time values, but you calculate them differently.

   

4. Click the Streets From-To row to select it. Press the Ctrl key and click the Streets To-From row to select both rows.
5. Right-click one of the selected rows, and click Value > Properties.

   The Field Evaluators dialog box opens.

For the Streets source, the value of PedestrianTime is the walk time. Assuming a pedestrian can walk at 3 km/hour, walk time in minutes would be [Meters] * 60 / 3000 where [Meters] is the attribute containing the length of the edge in meters.
6. Double-click the METERS field to move it into the Value = text box and finish typing the expression as [METERS]* 60 / 3000 on the Field Evaluators dialog box, as shown below.
7. Click Verify to ensure that the expression is correct, and fix it if necessary.

   

8. Click OK to return to the Evaluators dialog box.

   

9. Click OK to return to the New Network Dataset wizard.
10. Click Next.

Configuring travel modes

The page with travel mode settings appears. A travel mode consists of a collection of network dataset settings that define actions that are allowed on the network and how the actions can be performed. By configuring one or more travel modes on a network dataset, you can simplify workflows later. At analysis time, you can choose the mode you want to use instead of setting many different properties. If you perform many analyses for a specific travel mode or vehicle, it may be worthwhile to set up a travel mode. See the travel modes topic if you are interested in learning more about how they work and where they can be used.

You will set up a travel mode to model pedestrians.

1. In Travel Mode, type Pedestrian Time, and press Enter.
2. Set Type to Walk.
3. Set Impedance to PedestrianTime (Minutes).
4. Set Time Attribute to PedestrianTime (Minutes).
5. Set Distance Attribute to Meters (Meters).
6. Ensure that U-Turns at Junctions is set to Allowed.
7. Pedestrians can go where vehicles are prohibited on this network, and they can walk either way on a one-way street. Under Restrictions, uncheck DrivingAVehicle and Oneway.
You can set up another travel mode to represent car travel if you want.
8. Click Next.

Configuring directions

When routes are calculated on your network dataset, you have the ability to produce driving directions to accompany the results. A network dataset is required to have at least one edge source with a text attribute (for street name information) and a distance attribute to show how far it will be before the next relevant maneuver is required.

1. Click Yes to set up directions.
2. Click Directions.

   The Network Directions Properties dialog box opens.

Now you will specify the fields used to report directions for network analysis results.

3. On the General tab, click the Network Source drop-down list, and choose Streets.

   

4. In the Street Name Fields list, click Primary to select it.
5. Click in the Name column, and choose FULL NAME.

   

6. Click OK to return to the New Network Dataset wizard.
7. Click Next.
8. Check Build Service Area Index.

   Building the network dataset in the next section of this tutorial exercise will take longer than it would without the index, but generating service areas on the network dataset will be faster. See the optimizations topic to learn more.

9. Click Next.

   A summary of all the settings is displayed for your review.

Creating and building the network dataset

After setting up how you want the network dataset to function, you need to create and build it. The creation process is quick and essentially creates a container for the logical network.

1. Click Finish.

   A progress bar opens showing you that Network Analyst is creating the network dataset.

   

Once the network is created, the system asks if you want to build it. The build process determines which network elements are connected and populates the attributes of the network dataset. You must build the network before you can perform any network analysis on it.

2. Click Yes.

   The Build Network Dataset progress bar opens; it will disappear when the build process is finished.

   

   The new network dataset, ParisMultimodal_ND, is added to ArcCatalog along with the system junctions feature class, ParisMultimodal_ND_Junctions.

3. Preview the network dataset by clicking its name and clicking the Preview tab.
4. Close ArcCatalog.