Live traffic

Available with Network Analyst license.

This help topic provides information on how live traffic works. For an overview of traffic, see What is traffic data.

Live traffic attribute properties

The Live Traffic tab displays the properties that can be configured on a network dataset that supports live traffic.

Live Traffic tab


To create a working live-traffic network dataset, the following are required:

  • Access to a live traffic feed.
  • Historical traffic data must be set up on the network dataset.
  • A Streets-TMC table, which must be stored in the same geodatabase as the network dataset you are working with.
  • A time-zone table, which must be stored in the same geodatabase as the network dataset you are working with. A time zone network attribute is created to get information from this table.

    Learn more about configuring the time zone attribute

Live traffic workflow

The network dataset reads live traffic speeds from dynamic traffic format (DTF) files and relates the speeds to edges using traffic message channel (TMC) codes. TMC codes are standard unique identifiers that are supported by various organizations, including traffic data providers. The following graphic and the text below illustrate and describe this process:

Generalized live traffic
  1. The network dataset queries an edge for the current travel time. This occurs when a network analysis layer is being solved or when traffic is being drawn on a map.

  2. The identifying source feature information (source feature class, source feature, and from-to and to-from positions) is used to look up one or more TMC values. The lookup is performed with the information that was in the Streets-TMC Table at the time of the last network build. The Streets-TMC Table relates streets to TMC codes.


    The red box around the Streets-TMC Join Table in the diagram is there to highlight an oversimplification of the diagram. A network dataset doesn't directly reference the join table during the query process; that would be too slow. Instead, the information in the join table is built into the network dataset and referenced internally for faster processing. Consequently, any changes you make to the Streets-TMC table won't be incorporated into the network until it is rebuilt.

  3. The network dataset looks for a DTF file, which is a binary file designed for network datasets, and reads the travel speed information. On the Live Traffic tab, you can specify the folder where the downloaded DTF files reside by clicking the browse button for the Folder option; or use the Service option to use the live traffic feeds from ArcGIS Online or an Enterprise Portal which has a proxy to ArcGIS Online.

    Each DTF file is marked with a valid time range and contains TMCs and their corresponding travel speeds for the given time span. The network dataset opens a DTF file only if the time and date for which the edge is being queried is within the DTF file's valid time range. In many cases, multiple DTF files have valid time ranges that are within the queried time. This can occur when live traffic includes traffic predictions of a given depth, for example, for the next 12 hours. If multiple, valid files exist for the queried time, the file that was created immediately before the queried time is opened.


    Only one DTF file is opened per solve. That is, if multiple, valid files exist, only one is used throughout the duration of that solve process. Whenever the solver queries an edge for a time and date that is outside the file's time range, it attempts to retrieve the travel time from historical traffic tables instead.

  4. Once the DTF file is opened, the TMC and its associated travel speeds are combined with the length of the queried edge to determine the actual travel time.

    If a valid TMC value or DTF file can't be found, the network dataset falls back to historical traffic to retrieve the travel time. If historical travel times don't exist, it falls back to either a weekend- or weekday-specific network cost attribute, depending on the day of the week for which the edge is being queried. This fallback sequence is set out in the edge traffic evaluators of the traffic-based cost attribute.

Streets-TMC table

The Streets-TMC table furnishes the information needed to relate edges to speed values that are stored in DTF files. Typically, this table is provided by a data vendor along with street data.

The table below lists the required fields of a Streets-TMC table, an example field name, the allowed data types, and a short description.


The Network Analyst tutorial data, which is available on, includes a San Diego network dataset with a Streets-TMC table for your reference. After downloading and extracting the data, you can find the SanDiego geodatabase at \Network Analyst\Tutorial\SanDiego.gdb.

FieldField name exampleData typeDescription

Edge feature class identifier


You must name this field EdgeFCID.

Long integer

Identifies the feature class that stores the street feature.

Edge feature identifier


You must name this field EdgeFID.

Long integer

Identifies the street feature.

Edge from position


You must name this field EdgeFrmPos.


Works in conjunction with EdgeToPos to identify a direction of travel or side of the street. Zero indicates the beginning of the line feature as defined by its digitized direction. One indicates the opposite end.

For example, an EdgeFrmPos value of 0 and an EdgeToPos value of 1 identifies travel in the digitized direction of the line feature. The TMC value listed in the same record represents that side of the street only.

Any decimal values specify a position along the digitized direction of the feature, which allows the Dissolve Network tool to maintain the proper TMC values for streets after edges have been dissolved together.

Edge to position


You must name this field EdgeToPos.


Works in conjunction with EdgeFrmPos to identify a direction of travel or side of the street.

TMC code



The TMC code representing the associated road segment.

Traffic feed type

You can select the source of live traffic to be used in your analysis by choosing one of the following options:

  • None—Live traffic is not used during the analysis.
  • Service—Choose this option to access the traffic data service from ArcGIS Online or from your ArcGIS Enterprise portal configured to use this service. Access to this service is restricted to use with the ArcGIS StreetMap Premium dataset and requires the Live Traffic extension for your ArcGIS Online Organization. In the Portal drop-down list, you will find all managed portals. Each portal has an icon next to it indicating a status.
    • Green—The portal can obtain and return the live traffic helper service URLs and has no traffic feed authorization-related problems.
    • Yellow—The network dataset has previously been updated to use a service. The organization of the signed in user at that time was authorized to use traffic feeds. However the organization of the currently signed on user is not authorized at this time to use traffic feeds on this portal.

      The following are examples:

      • The organization of the currently signed on user is not authorized for traffic. The signed on user might have been for a different organization of the portal that is authorized. Or alternatively could be the same organization but they are no longer authorized for traffic feed service.
      • The portal was previously set up, but the user is not currently signed on to the portal so it can not be used as an authorization portal for traffic feed.

    • Red—The portal is not currently authorized for traffic feeds and cannot be chosen for authorization.

      The following are examples:

      • The portal is not licensed to use live traffic.
      • The portal is on an enterprise server, and the helper services to proxy to ArcGIS Online have not been set up.

    Once the authorization portal has been set up, the network dataset will store the portal URL.
  • Folder—Choose this option to identify the folder where DTF files are downloaded. The path to the folder can be a local file system path or a Universal Naming Convention (UNC) path.

Modify live traffic

Follow the steps below to modify a network's live traffic settings:

  1. Open the Network Dataset Properties dialog box.
  2. Click Traffic.

    Two tabs, Historical Traffic and Live Traffic, appear. However, if the network dataset you're using was not configured to support traffic at the time it was created, these tabs will not be available.

  3. Click the Live Traffic tab.
  4. From the Streets-TMC Table drop-down list, choose the Streets-TMC table.

    If your geodatabase does not have a valid Streets-TMC table candidate, the drop-down list will be empty.

    DTF files created from traffic feeds store travel-speed information by TMC code. The Streets-TMC table relates TMC codes to street segments or subsections of street segments so that travel speeds can be linked ultimately to network edges. The Streets-TMC table is often included with network data acquired from a data vendor.

    Learn more about the schema and attributes of a Streets-TMC table

  5. From the TMC drop-down list, choose the field in the Streets-TMC table that contains TMC codes.
  6. Depending on the source you want to use for live traffic feeds, select from the following options: Service or Folder.

    The path to the folder can be a local file system path or a Universal Naming Convention (UNC) path.


    The Traffic Data utility service can be configured with your enterprise portal from the ArcGIS Online pane in your organization settings. Enable the Traffic Data option and provide the credentials of a named user from your ArcGIS Online organization. Your ArcGIS Online organization should also have the live traffic extension. If your ArcGIS Online organization does not have live traffic extension, contact customer service (in the United States) or your local Esri distributor (outside the United States).