Create Network Dataset ArcGIS Pro: Step-by-Step Guide

Quick Navigation / Table of Contents

1. Core Concepts: How Network Datasets Model Transportation
2. Step 1: Prepare Street Centerline Geometry and Topology
3. Step 2: Set Up a Geodatabase Feature Dataset
4. Step 3: Step-by-Step Guide to Create Network Dataset ArcGIS Pro Workflows
5. Step 4: Build, Validate, and Test Routing Solvers
6. Pro Tip: Modeling Overpasses and Underpasses with Elevation Fields
7. Frequently Asked Questions (FAQ)
8. Conclusion & Lab Summary

1. Fundamentals of Network Analysis in ArcGIS Pro

+-------------------------------------------------------------------------+
|                       RAW STREET CENTERLINE LINES                       |
|           Polylines with Speed Limits, Length, & One-Way Fields         |
+------------------------------------+------------------------------------+
                                     |
                                     v
                  +-------------------------------------+
                  |      GEODATABASE FEATURE DATASET    |
                  | Enforces Spatial Reference & Rules  |
                  +------------------+------------------+
                                     |
                                     v
                  +-------------------------------------+
                  |       CREATE NETWORK DATASET        |
                  |  Defines Edges, Junctions, & Turns  |
                  +------------------+------------------+
                                     |
            +------------------------+------------------------+
            |                                                 |
            v                                                 v
  [ Cost Attributes ]       [ Restrictions ]         [ Evaluators & Travel Modes ]
  Drive Time (Minutes)      One-Way Streets          Car, Truck, Walking
  Distance (Meters)         Height/Weight Limits     Impedance Calculations

Key Components of a Routing Network

• Edges: Line features representing travel paths (e.g., street segments, highway links, footpaths).
• Junctions: Point features connecting edges and facilitating transfer between paths (e.g., street intersections).
• Turns: Optional feature classes that store directional delay rules or illegal turn restrictions (e.g., “No Left Turn between 7 AM and 9 AM”).
• Impedance (Cost): The resistance or metric consumed when traversing network elements (e.g., distance in meters or travel time in minutes).

2. Step 1: Prepare Street Centerline Geometry and Topology

Essential Line Preparation Checks

1. 1. Split at Intersections: Street polylines must be split at every point where vehicles can transition from one street to another. If two crossing lines do not share a vertex or endpoint at their intersection, the network solver treats them as an overpass/underpass with no connection.
   2. Eliminate Multipart Features: Network edges must be single-part line features. Run the Multipart To Singlepart tool (Data Management Tools > Features) to ensure every segment is an independent feature.
   3. Clean Up Geometry Overshoots & Dangles: Ensure dead-end streets end cleanly and connecting roads touch precisely without overshoot or undershoot gaps. Use snapping during editing to maintain geometry precision.
   4. Required Attribute Fields: Verify your attribute table contains necessary fields for routing calculations:
      • Length Field: Segment distance in meters or feet (Shape_Length or custom field).
      • Speed Limit Field: Numeric speed limit (Speed_MPH or Speed_KPH).
      • Drive Time Fields: Double fields calculated from distance and speed: DriveTime_FT (From-To direction) and DriveTime_TF (To-From direction).
      • One-Way Direction Field: Text field indicating flow restrictions (e.g., FT = One Way From-To, TF = One Way To-From, B = Both directions allowed, N = No traffic allowed).

3. Step 2: Set Up a Feature Dataset in a File Geodatabase

Creating the Feature Dataset Container

1. Open the Catalog Pane (View > Catalog Pane).
2. Expand your project directory, right-click your File Geodatabase, and select New > Feature Dataset.
3. Name your feature dataset (e.g., Transportation_Network).
4. Coordinate System Selection: Assign a local Projected Coordinate System (PCS) (e.g., State Plane or UTM Zone). Do not use unprojected WGS84 lat/long degrees, as linear distance metrics and cost evaluators require projected meters or feet.
5. Import your prepared street centerline feature class into this new Feature Dataset using Feature Class To Geodatabase or by dragging the layer in.

<=”carousel-container”>

Step 1: Launch the Create Network Dataset Tool

1. In the Catalog Pane, right-click your Feature Dataset (Transportation_Network).
2. Select New > Network Dataset.
3. Name your network dataset (e.g., Streets_ND).
4. Select your street centerline feature class as the input source edge feature class.

Step 2: Configure Elevation and Connectivity Settings

1. Connectivity Policy: Choose End Point (routes transition only at line endpoints) or Any Vertex (routes transition anywhere lines touch). For properly split street centerlines, End Point is standard.
2. Elevation Model: Select Z-Coordinates if your lines contain 3D Z-values, or Elevation Fields if using F_ELEV and T_ELEV integer fields to control grade-separated intersections (e.g., bridges and tunnels).

Step 3: Configure Cost Attributes and Evaluators

1. Navigate to the Attributes configuration tab.
2. Add a new Cost Attribute named Meters (Units: Meters, Data Type: Double). Set evaluators to map directly to Shape_Length.
3. Add a new Cost Attribute named DriveTime (Units: Minutes, Data Type: Double).
4. Configure Evaluators for DriveTime:
   • Assign DriveTime_FT for the From-To edge direction.
   • Assign DriveTime_TF for the To-From edge direction.
5. Add a Restriction Attribute named Oneway:
   • Set evaluator type to Field Script / Expression.
   • Map the restriction to your Oneway text column so that FT restricts To-From travel, TF restricts From-To travel, and N blocks both directions.

Step 4: Define Travel Modes

1. Click the Travel Modes tab.
2. Create travel profiles tailored to your assignment scenarios:
   • Driving Time: Primary cost set to DriveTime (Minutes), restrictions applied to Oneway.
   • Driving Distance: Primary cost set to Meters, restrictions applied to Oneway.
   • Walking: Primary cost set to WalkingTime, ignoring Oneway restrictions (since pedestrians can walk both directions along streets).
3. Click Finish / Run to build the network schema.

Pro Tip: Grade-Separated Intersections with Elevation Fields

A common flaw in student network models is allowing illegal turns where an overpass bridge crosses over a highway. Because two lines cross in 2D space, the network solver might create an artificial junction unless elevation rules are defined.

To fix this, add two integer fields to your street centerline layer:

• F_ELEV (From-Node Elevation): 0 for ground level, 1 for elevated bridge.
• T_ELEV (To-Node Elevation): 0 for ground level, 1 for elevated bridge.

In the Network Dataset Properties wizard under Elevation Fields, set the From-elevation and To-elevation properties to these fields. Two crossing lines with different elevation values at the intersection point will not connect topologically, maintaining realistic overpass and underpass routing.

5. Step 4: Build, Validate, and Test Routing Solvers

Building the Network

1. In the Catalog Pane, right-click your newly created network dataset (Streets_ND).
2. Click Build Network.
3. Once completed, ArcGIS Pro generates system junction point layers (Streets_ND_Junctions) inside your Feature Dataset.

Testing with Network Analyst Solvers

1. 1. On the main top ribbon, click the Analysis tab.
   2. Click Network Analyst and select Route (or Service Area / Closest Facility).
   3. In the Network Analyst tab, set the Network Dataset target to your built Streets_ND.
   4. Open the Import Stops tool and add two or more location points on your map scene.
   5. Select your Travel Mode (e.g., Driving Time).
   6. Click Run. The Network Analyst extension calculates and draws the optimal route following one-way rules, turn restrictions, and speed limits.
   7. To explore shortest path algorithms further, check out our guide on Network Analysis Shortest Path Calculations

1. For official algorithm parameters, consult the Esri Network Analyst Documentation.

6. Frequently Asked Questions (FAQ)

Why does my network dataset require a File Geodatabase feature dataset?

How do I set up one-way street restrictions in my attribute table?

What is the difference between a geometric network and a network dataset?

7. Conclusion & Summary

• Always use a Projected Coordinate System (PCS) for your feature dataset.
• Ensure street centerlines are split at valid intersections and converted to single-part features.
• Map impedance evaluators (DriveTime, Distance) and directional restrictions (Oneway) accurately.
• Always execute Build Network after modifying source geometries or attribute parameters.