Data Analytics

Data Analytics

Data Analytics Group

The Data Analytics section is a part of the Data and Information Group and is responsible for reporting, maintaining, collecting, analyzing and visualizations for data on roadways in Arizona. This section is also responsible for the Highway Performance Monitoring System (HPMS), the All Roads Linear Referenced Data (ARNOLD) and Data Supply Chain, Certified Public Miles (CPM), the State Highway Log and providing data for the Model Inventory Roadway Elements (MIRE) report submissions. The section also provides many different visualizations and documentation of this data in the form of Story Maps and Dashboards. The Data Analytics section is in partnership with the Geospatial Analysis Section who are the data owners and maintainers for all data sets used by the Data Analytics Section. Also under the Data and Information group is the Traffic Monitoring Section who we collaborate with regularly to assemble the traffic statistics for HPMS, as well as the Modeling and Forecasting Section.

 

Highway Performance Monitoring Systems (HPMS)

The Data Analytics section are the project leads for the HPMS Submission. HPMS is a report required to be submitted by all State DOT’s that details status, quality and mileage on a variety of data items on all roadways.

This program includes inventory on all of the Nation's public roads as certified by the States’ Governors annually. All items, like functional classification, pavement, and many more, are reported on regardless of road ownership. Also required for HPMS submission is the total public road mileage, which must be certified by the state DOT Director and the State Governor. This is referred to as Certified Public Miles and is the the sum of all public roads in the state that are, passable with a standard passenger car, not restricted by any gates or other barriers, publicly accessible, and includes BIA lands.

HPMS-Overview-Storymap
CPM-storymap
 

Centerline Unification

The Data Supply Chain is the data sharing mechanism that operates between all levels of government and private entities. This allows local agencies to share their data with the ADOT inorder to create a fully, spatially represented GIS all roads network. By creating, in partnership with Arizona State Lands and ADOA,  an easily accessible data sharing site called AZGeo Data Clearing House, the local agencies can provide their GIS data, which help ADOT to create and maintain the Linear Referencing System (LRS) for ARNOLD purposes. This is required by FHWA by each state to maintain a wholistic GIS network of all roads in the state.

Are you a local agency? Would you like a tutorial on the AZGeo “We Love Your Input” Change Request tool? Reach out to Sage Donaldson or  Lucas Murray to schedule a tutorial!

arnold-data-supply-chain

Functional Classification

The Functional Classification (FC) map, an official FHWA-approved map. For information about changing the functional classification of a roadway, please see the story maps below. To submit a Functional Classification Change request, go to the AZGeo We Love your input tool and create a ticket by November 30 annually in order for the change to included in the HPMS Report

If you have any questions or requests regarding functional Classification, please contact Sage DonaldsonLucas Murray, or James Meyer.

Federal Functional Classification

Federal-Functional-Classification-Rebalancing-Process-Storymap
AZGeo-Functional-Classification-Change-Request-Tool-Tutorial-Storymap

AZGeo Thumbnail

Ownership and CPM Validation

For information about validating the ownership or CPM of a roadway, please read the AZGeo Certified Public Mileage Validation Tool storymap. To submit an ownership or CPM validation request, open the AZGeo We Love Your Input Tool and submit a ticket, which will be reviewed by ADOT and our partner agencies. Please note that in order for the change to be included in the CPM submission to the Federal Highway Administration (FHWA) Highway Performance Monitoring System (HPMS) annual report, please submit your ticket no later than April 1.

 

AZGeo Certified Public Mileage Validation tool

 

AZGeo Thumbnail

 

Extent and Travel

The Extent and travel report is generated on a yearly basis from each HPMS submittal. This is a report that is generated from the HPMS mileage breakdown through the UPACS software.

This report is a breakdown of all mileage reported for HPMS purposes. These mileage classifications can be NHS, by city, or by urban/rural areas. Each of these categories are also broken down by functional classification and gives the total for each functional classifications.

Data Extent Coverate

Federal Functional Classification


State Highway System Log

Each year, the Data Analytics Section, in partnership with the Geospatial Analysis Section, produces a route-by-route highway inventory for all State Highway System facilities pertaining to the previous calendar year. This inventory documents various features, geometrics, projects and other information as they occur along the route. Updates to the Highway Log are principally derived from completed highway projects and any resolutions passed by the State Transportation Board.

Map

State Highway System Map

Access the State Highway System (SHS) Log website to view the SHS Log Dashboard and access related documents, including the SHS Log PDF Reports and Mileage Booklets

Traffic and HPMS

Traffic data reporting is integral to the Highway Performance Monitoring System (HPMS) Report. Coordination between various ADOT teams (i.e. Data Analytics, Geospatial Analysis, Modeling and Forecasting, and Traffic Monitoring) creates the chain of command for the Traffic data.

  • The Traffic Monitoring Team collects the traffic data on the roadway;
  • The Data Analytics and Geospatial Analysis Teams analyze the data;
  • The Modeling and Forecasting Team generates future average annual daily traffic (AADT) values; and
  • The Data Analytics Team reports the data.

For HPMS, gathering traffic count data from local agencies is extremely important in order to report traffic information statewide. To do this, local agencies are advised to load their traffic count data to the Traffic Data Management System (TDMS), also referred to as MS2. If you are from a local agency and would like guidance on uploading your agency’s traffic data to the TDMS, refer to the storymaps below or contact Sanja Katic-Juahar to request a tutorial.

For more information on Traffic Monitoring, visit the Traffic Monitoring webpage.

Guide to Using MS2

Pavement

As part of the HPMS report, ADOT must submit information on various road characteristics that includes the extent and condition of road pavement. This information is reported annually for interstates by April 15th and for other necessary roads by June 15th. More about the pavement reporting requirements for HPMS, an explanation about how the data are reported, links to previous pavement report cards, and a dashboard with the latest pavement conditions is available on the Pavement Condition Data Website.

Pavement Condition Data Website

Pavement Condition Data Website

 

Resources

To learn more about GIS or HPMS or for links to one of the many helpful maps, dashboards, or reports created by the MPD Data Analytics or GIS teams, refer to the links below.

GIS Instructional Storymaps

GIS Instructional Storymaps

 

HPMS Instructional Storymap

HPMS Instructional Storymaps

 

Additional Resources

Additional Resources (Maps, Dashboards and Reports)