IMP - Creating A Network Dataset
IMP - Creating A Network Dataset
1. Start ArcCatalog.
1. Click Customize > Extensions.
2. Check Network Analyst.
3. Click Close.
5. Click OK.
The feature classes the feature dataset contains are listed on the Contents tab of ArcCatalog.
8. Right-click the Transportation feature dataset and click New > Network Dataset.
Note:
To open the New Network Dataset wizard in a geodatabase, right-click the feature dataset that
contains the source feature classes (Streets, for example) and choose New > Network Dataset. For a
shapefile-based network dataset, right-click the Streets shapefile itself—not the workspace that
contains the shapefile—and choose New > Network Dataset.
The reason for the difference is that geodatabase networks allow you to use multiple sources that are
stored in the feature dataset to create a multimodal network, while shapefile-based network datasets
are only capable of handling a single source feature class.
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.
11. Click Next.
12. Check the Streets feature class to use it as a source for the network dataset.
13. Click Next.
17. Click Connectivity.
The Connectivity dialog box opens. Here you can set up the connectivity model for the network.
For this Streets feature class, all streets connect to each other at endpoints.
18. Make sure that the connectivity policy of Streets is set to End Point.
20. Click Next.
21. This dataset has elevation fields, so make sure that the Using Elevation Fields option is chosen.
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.
The Streets feature class has logical elevation values stored as integers in the F_ELEV and T_ELEV
fields. If two coincident endpoints have field elevation values of 1, for example, the edges connect.
However, if one endpoint has a value of 1, and the other coincident endpoint has a value of 0 (zero),
the edges don't connect. Network Analyst recognizes the field names in this dataset and automatically
maps them, as shown in the graphic below. (Only integer fields can serve as elevation fields.)
22. Click Next.
You can configure traffic data with this page of the wizard. Traffic data enables you to find the
quickest routes based on time and day of the week. For example, the quickest route from point A to
point B at 8:30 a.m. on Wednesday (during rush hour) could be different than the quickest route
between the same points at 1:00 p.m. on Sunday. Even if the path of the route is the same, the time it
takes to reach the destination could vary.
Note:
This dataset doesn't include the information necessary to configure live traffic data; however, the data
for exercise 10 does.
23. Click Next.
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 sets up eight attributes for this San Francisco data: Hierarchy, Meters,
Minutes, Oneway, RoadClass, TravelTime, WeekdayFallbackTravelTime, and
WeekendFallbackTravelTime. It also creates evaluators for the attributes.
24. Click the Meters row to select it, then click Evaluators to examine how the values of network
attributes are determined.
25. From the Attribute drop-down list, click each type of attribute, one at a time, and inspect the
evaluator types and values for the source feature classes.
In the next steps, you will add a new attribute to restrict movement over the turn elements created
from the RestrictedTurns feature class.
27. Click Add.
This setting prohibits the turn features from being traversed during an analysis.
Note that Use by Default is checked. This restriction is used by default when a new network analysis
layer is created. If you want to ignore the restriction when performing an analysis, you can disable it
31. Click OK.
The new attribute, RestrictedTurns, is added to the list of attributes. The blue circle with the D in the
middle indicates the attribute is enabled by default in new analyses.
33. Follow these substeps to set the type of evaluator for RestrictedTurns to Constant with a value of
Restricted:
The blue symbol is removed from the attribute. This means the hierarchy won't be used by default
when an analysis layer is created with this network dataset.
36. Click Next.
The page with travel mode settings appears. By configuring one or more travel modes on a network
dataset, you can choose a mode at analysis time and avoid setting various properties to model a car,
truck, pedestrian, or other travel mode. If you perform many analyses for a specific travel mode, 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.
37. Click Next.
Now you will specify the fields used to report directions for network analysis results.
40. On the General tab, make sure that the Name field for the Primary row automatically mapped
to NAME.
The NAME field contains the San Francisco street names, which are needed to help generate driving
directions.
42. Click Next.
Building the network dataset at the end 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.
44. Click Next.
45. 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.
46. Click Yes.
The Build Network Dataset progress bar opens; it will disappear when the build process is finished.
The new network dataset, Streets_ND, is added to ArcCatalog along with the system junctions feature
class, Streets_ND_Junctions.
47. Preview the network dataset by clicking its name and clicking the Preview tab.
Now you can add the network dataset to ArcMap and use it to create network analysis layers.