This layer contains traffic statistics collected or obtained by the Transportation Monitoring Unit and developed and analyzed by the Traffic Analysis section of the Technology & Innovation Division at the Utah Department of Transportation. These statistics are intended for transportation management, private businesses, and public use. The traffic information is used in planning, programming, highway design, maintenance, traffic control, and general administration of highway systems.The traffic information contained represents the Annual Average Daily Traffic (AADT) on road sections of State Highway and Federal-Aided roads. These statistics are developed by the Traffic Analysis section through the use of the following count site types:1. Continuous Count Stations (CCS) provided by the Utah Department of Transportation. A statewide system of permanent vehicle count stations that collect volume, vehicle classification (length), and speed, 24 hours per day, 365 days per year.2. Short-term counts administered by the Utah Department of Transportation, each traffic section is generally counted about every 3 years for a duration of 48 hours, and seasonally factored using factors created by CCS stations.AADT represents traffic for both directions of travel. The routes are sectioned according to:a. Major intersectionsb. Sections where traffic volumes show a significant difference in AADT. Generally 20% under 5,000 AADT to 5% for over 50,000 AADT.Truck Statistics are available for State routes only. Single-Unit Truck (FHWA Vehicle Axle Classifications 4-7), and Combination Unit Trucks (FHWA UDOT Open Data Portal Vehicle Axle Classifications 8-13). The values are represented by a percentage of the AADT reported for the same year.Example: A roadway with 1000 AADT has 0.1500 SUTRK reported, is 15% of the AADT are Single-Unit Trucks (or 150 SUTRK AADT).For AADT reported as Rounded, reports and maps use the AASHTO recommendation as follows:AADT = 0 - 999: Round to the nearest 10thAADT = 1,000 - 9,999: Round to the nearest 100thAADT >= 10,000: Round to the nearest 1000thNOTE: If a statistical calculation is needed to be applied to the AADT, (such as when calculating Vehicle Miles Traveled), it is not recommended to use rounded AADT’s. Unrounded AADT’s and truck percentages for are available at UDOT's Open Data Portal for download.This service is specially configured for use with UDOT's Open Data Portal. Please see the Data Assessment Form for more information. To download either the Rounded or Unrounded AADT for this data please visit the and download the available Shapefile and CSV's.

Statewide Traffic Volume Historic and Forecast Historic traffic volume observations, future traffic volume forecasts, and adjustment factors -- are summarized using Utah's roadway planning summary segments -- for the Wasatch Front Regional Council metropolitan planning organization travel model area. This dataset can be viewed in an interactive map at: https://wfrc.org/traffic-volume-map/. This dataset provides segment level traffic volume data (historic estimates and future forecasts) within the state of Utah. Wasatch Front Regional Council (WFRC) metropolitan planning organization's travel model boundaries (including Salt Lake, Davis, western Weber, and southern Box Elder counties' urbanized areas). Future forecasts have been developed with the support of the Wasatch Front Travel Demand Model (v8.3.1) in conjunction with the adopted 2019 Regional Transportation Plan (RTP). This dataset was first released May 5th, 2020 (check the RELEASE field/column attribute for most recent update date). MAG travel model boundaries include the urbanized areas of Utah County. Cache travel model boundaries include Cache County. Dixie travel model boundaries include Washington County. Also contained within this dataset are adjustment factors, developed as part of a statewide effort led by UDOT, that can be used to scale the Average Annual Daily Traffic (AADT) volumes estimates and forecasts to provide more time-period specific volumes for a time period subsets (e.g. weekdays, weekends, specific months, seasons, maximum month, etc). Contact and additional information is available from https://wfrc.org/models-and-forecasting or through email contact to analytics@wfrc.org.UPDATE 12/31/2021: Highland Drive revised forecasts for SEGIDs 2082_009.0, 2082_009.6, 2082_011.5, 0152_002.5, 0152_002.8. Field names and descriptions are as follows: RELEASE (version of dataset) SEGID (Segment ID, combination of Route_ID and BMP) ROUTE_ID (Route Identification, <1000 for Interstate/State Routes, >1,000 for Federal Aid Routes) BMP (Begin Milepost, or milepost of beginning of segment) EMP (End Milepost, or milepost of ending of segment) FULLNAME (name of segment) CO_FIPS (County Federal Information Processing Standard, unique code for each county) CO_NAME (Name of county) X (Centroid of Segment, UTM Zone 12N) Y (Y Centroid of Segment, UTM Zone 12N) DISTANCE (length of segment in miles) F2050...F2024 (forecast AADT volumes for model years per 2019 RTP) CH17TO50...CH17TO19 (change in AADT volumes between model years) FNOTES (forecast notes, typically when drop or large increase in volumes) MOREINFO (url to more general information on models and forecasts) WFRC_FLG (flag value used internally by WFRC) AADT2017...AADT1981 (AADT estimates for a given year from UDOT) SUTRK2017 (Single-Unit, Box Type Truck percentage for 2017) CUTRK2017 (Combo-Unit, Semi Type Truck percentage for 2017) DOWFACFC (Day-of-Week Factor Functional Class) DOWFACAT (Day-of-Week Factor Area Type) FAC_MON...FAC_SUN (Day-of-Week factors for given days) FAC_WDAVG (Average Weekday Factor Monday-Thursday, multiply AADT by factor to get AWDT, divide AWDT by factor to get AADT) FAC_WEAVG (Average Weekend Factor Friday-Sunday) FAC_WEMAX (Max Weekend Factor Friday-Sunday) SSNGRP (Seasonal Factor Group) SSNVOLCLS (Seasonal Factor Volume Class) SSNATGROUP (Seasonal Factor Area Type Group) FAC_JAN...FAC_DEC (Month Factors, multiply AADT or AWDT get month ADT or AWDT) FAC_WIN (Winter Factor, December-February) FAC_SPR (Spring Factor, March-May) FAC_SUM (Summer Factor, June-August) FAC_FAL (Fall Factor, September-November) FAC_MAXMO (Month in which Maximum Month Factor is found) FAC_MAX (Maximum Month Factor)

The map shows the volume of daily traffic over each road segment in Utah, and a measure of safety for those road segments. The map demonstrates the use of smart mapping on two key attributes in a traffic safety database: daily traffic volume, and Safety Index. "The Safety Index offers a statewide comparison of UDOT roadways, taking into account the different traffic patterns and volumes experienced in urban and rural areas. The Safety Index is a combination of four, equally weighted safety analysis sub-scores: Crash Rate Score, Severe Crash Rate Score, Crashes per Mile Score, Severe Crashes per Mile Score. The Safety Index is reported on a 0 to 10 scale, with 10 representing the worst conditions. The data reflect crashes from 2011 through 2013. For more information please see the Data Assessment Form. To download this data please visit UDOT's Open Data Site." -- Utah Department of TransportationThe Safety Index represents factors that transportation experts consider when prioritizing changes to the roads.The original map was the inspiration for this map. See its full explanation here.

Statewide traffic signal locations.This layer is manually updated and is refreshed annually.For questions regarding this data, please contact UDOT Traffic Signal Operations.

Important Dataset Update 6/24/2020:Summit and Wasatch Counties updated.Important Dataset Update 6/12/2020:MAG area updated.Important Dataset Update 7/15/2019: This dataset now includes projections for all populated statewide traffic analysis zones (TAZs). Projections within the Wasatch Front urban area ( SUBAREAID = 1) were produced with using the Real Estate Market Model as described below. Socioeconomic forecasts produced for Cache MPO (Cache County, SUBAREAID = 2), Dixie MPO (Washington County, SUBAREAID = 3), Summit County (SUBAREAID = 4), and UDOT (other areas of the state, SUBAREAID = 0) all adhere to the University of Utah Gardner Policy Institute's county-level projection controls, but other modeling methods are used to arrive at the TAZ-level forecasts for these areas.As with any dataset that presents projections into the future, it is important to have a full understanding of the data before using it. Before using this data, you are strongly encouraged to read the metadata description below and direct any questions or feedback about this data to analytics@wfrc.org. Every four years, the Wasatch Front’s two metropolitan planning organizations (MPOs), Wasatch Front Regional Council (WFRC) and Mountainland Association of Governments (MAG), collaborate to update a set of annual small area -- traffic analysis zone and ‘city area’, see descriptions below) -- population and employment projections for the Salt Lake City-West Valley City (WFRC), Ogden-Layton (WFRC), and Provo-Orem (MAG) urbanized areas. These projections are primarily developed for the purpose of informing long-range transportation infrastructure and services planning done as part of the 4 year Regional Transportation Plan update cycle, as well as Utah’s Unified Transportation Plan, 2019-2050. Accordingly, the foundation for these projections is largely data describing existing conditions for a 2015 base year, the first year of the latest RTP process. The projections are included in the official travel models, which are publicly released at the conclusion of the RTP process. As these projections may be a valuable input to other analyses, this dataset is made available at http://data.wfrc.org/search?q=projections as a public service for informational purposes only. It is solely the responsibility of the end user to determine the appropriate use of this dataset for other purposes. Wasatch Front Real Estate Market Model (REMM) ProjectionsWFRC and MAG have developed a spatial statistical model using the UrbanSim modeling platform to assist in producing these annual projections. This model is called the Real Estate Market Model, or REMM for short. REMM is used for the urban portion of Weber, Davis, Salt Lake, and Utah counties. REMM relies on extensive inputs to simulate future development activity across the greater urbanized region. Key inputs to REMM include:Demographic data from the decennial census;County-level population and employment projections -- used as REMM control totals -- are produced by the University of Utah’s Kem C. Gardner Policy Institute (GPI) funded by the Utah State Legislature;Current employment locational patterns derived from the Utah Department of Workforce Services; Land use visioning exercises and feedback, especially in regard to planned urban and local center development, with city and county elected officials and staff;Current land use and valuation GIS-based parcel data stewarded by County Assessors;Traffic patterns and transit service from the regional Travel Demand Model that together form the landscape of regional accessibility to workplaces and other destinations; andCalibration of model variables to balance the fit of current conditions and dynamics at the county and regional level.‘Traffic Analysis Zone’ ProjectionsThe annual projections are forecasted for each of the Wasatch Front’s 2,800+ Traffic Analysis Zone (TAZ) geographic units. TAZ boundaries are set along roads, streams, and other physical features and average about 600 acres (0.94 square miles). TAZ sizes vary, with some TAZs in the densest areas representing only a single city block (25 acres). ‘City Area’ ProjectionsThe TAZ-level output from the model is also available for ‘city areas’ that sum the projections for the TAZ geographies that roughly align with each city’s current boundary. As TAZs do not align perfectly with current city boundaries, the ‘city area’ summaries are not projections specific to a current or future city boundary, but the ‘city area’ summaries may be suitable surrogates or starting points upon which to base city-specific projections.Summary Variables in the DatasetsAnnual projection counts are available for the following variables (please read Key Exclusions note below):DemographicsHousehold Population Count (excludes persons living in group quarters)Household Count (excludes group quarters)EmploymentTypical Job Count (includes job types that exhibit typical commuting and other travel/vehicle use patterns)Retail Job Count (retail, food service, hotels, etc)Office Job Count (office, health care, government, education, etc)Industrial Job Count (manufacturing, wholesale, transport, etc)Non-Typical Job Count* (includes agriculture, construction, mining, and home-based jobs) This can be calculated by subtracting Typical Job Count from All Employment Count.All Employment Count* (all jobs, this sums jobs from typical and non-typical sectors).* These variable includes REMM’s attempt to estimate construction jobs in areas that experience new and re-development activity. Areas may see short-term fluctuations in Non-Typical and All Employment counts due to the temporary location of construction jobs.Population and employment projections for the Wasatch Front area can be combined with those developed by Dixie MPO (St. George area), Cache MPO (Logan area), and the Utah Department of Transportation (for the remainder of the state) into one database for use in the Utah Statewide Travel Model (USTM). While projections for the areas outside of the Wasatch Front use different forecasting methods, they contain the same summary-level population and employment projections making similar TAZ and ‘City Area’ data available statewide. WFRC plans, in the near future, to add additional areas to these projections datasets by including the projections from the USTM model.Key Exclusions from TAZ and ‘City Area’ ProjectionsAs the primary purpose for the development of these population and employment projections is to model future travel in the region, REMM-based projections do not include population or households that reside in group quarters (prisons, senior centers, dormitories, etc), as residents of these facilities typically have a very low impact on regional travel. USTM-based projections also excludes group quarter populations. Group quarters population estimates are available at the county-level from GPI and at various sub-county geographies from the Census Bureau.

Graph and download economic data for All Employees: Truck Transportation in Salt Lake City, UT (MSA) (SMU49416204348400001A) from 1990 to 2024 about Salt Lake City, UT, trucks, transportation, employment, and USA.

Graph and download economic data for All Employees: Transportation and Utilities: Truck Transportation in Salt Lake City-Murray, UT (MSA) (SMU49416204348400001SA) from Jan 1990 to May 2025 about Salt Lake City, UT, trucks, transportation, employment, and USA.

All Employees: Transportation and Utilities: Truck Transportation in Salt Lake City, UT (MSA) was 11.08220 Thous. of Persons in April of 2025, according to the United States Federal Reserve. Historically, All Employees: Transportation and Utilities: Truck Transportation in Salt Lake City, UT (MSA) reached a record high of 12.67676 in May of 2019 and a record low of 7.19244 in May of 1990. Trading Economics provides the current actual value, an historical data chart and related indicators for All Employees: Transportation and Utilities: Truck Transportation in Salt Lake City, UT (MSA) - last updated from the United States Federal Reserve on June of 2025.

Vector polygon map data of mile markers from the State of Utah containing 5758 features.

Mile marker GIS data consists of points along a linear feature, such as roads or railways. They serve as reference points to measure distances along these features. Mile markers are often labeled with numbers indicating their distance from a starting point, such as a highway's origin or a railway station.

These markers are invaluable for navigation, route planning, emergency response, and data collection. For example, they help drivers and emergency services identify their location precisely on a road. In transportation planning, mile markers aid in analyzing traffic patterns, determining optimal routes, and estimating travel times. Additionally, they facilitate maintenance activities by providing clear reference points for inspecting and repairing infrastructure.

This data is available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.

Traffic analysis zones (TAZs) are special-purpose geographic entities delineated by state and local transportation officials for tabulating traffic related data from the decennial census, especially journey-to-work and place-of-work statistics. A TAZ usually consists of one or more census blocks, block groups, or census tracts. For Census 2000 TAZs are defined within county. Each TAZ is identified by a 6-character alphanumeric census code that is unique within county or statistically equivalent entity. A code of ZZZZZZ indicates a portion of a county where no TAZs were defined. The U.S. Census Bureau first provided data for TAZs in the 1980 census, when it identified them as 'traffic zones.' For the 1990 census, the TAZs were defined within Census Transportation Planning Package (CTPP) areas. TAZs were not shown in any 1990 Census TIGER extracts. The U.S. Census Bureau subsequently inserted the TAZs into the Census TIGER database and began extracting them starting with the 1994 TIGER/Line files. The Census 2000 TAZ program was conducted on behalf of the Federal Highway Administration, Department of Transportation, which offered participation to the Metropolitan Planning Organizations (MPOs) and the Departments of Transportation (DOTs) in the 50 states and the District of Columbia. The following states did not have a participating MPO or State DOT for the Census 2000 TAZ Program: Delaware, Hawaii, Montana.

Traffic Accidents SLC 2013

Traffic Accidents Salt Lake City 2012

This map contains traffic statistics collected by the Transportation Monitoring Unit and developed and analyzed by the Traffic Analysis Section of the Program Development Division of the Utah Department of Transportation. These statistics are intended for use by transportation management, business, and the public. The traffic information is used in planning, programming, highway design, maintenance, traffic control and general administration of highway systems. The traffic information contained in this map is Annual Average Daily Traffic (AADT) on road sections of the State Highways or Local

HPMS compiles data on highway network extent, use, condition, and performance. The system consists of a geospatially-enabled database that is used to generate reports and provides tools for data analysis. Information from HPMS is used by many stakeholders across the US DOT, the Administration, Congress, and the transportation community.

Traffic signals within St Lucie County Florida

This layer contains Utah highways and their associated degree of access control for a given segment of road per the Highway Performance Monitoring System Field Manual (HPMS). Full Access ControlPreference given to through traffic movements by providing interchanges with selected public roads, and by prohibiting crossing at-grade and direct driveway connections (i.e., limited access to the facility). Partial Access ControlPreference given to through traffic movement. In addition to interchanges, there may be some crossings at-grade with public roads, but, direct private driveway connections have been minimized through the use of frontage roads or other local access restrictions. Control of curb cuts is not access control. No Access ControlNo degree of access control exists (i.e., full access to the facility is permitted).

The National Bridge Inventory (NBI) is a database, compiled by the Federal Highway Administration, with information on all bridges and tunnels in the United States that have roads passing above or below.

Salt Lake City - Transportation Permits

Graph and download economic data for Gross Domestic Product: Transportation and Warehousing (48-49) in Utah (UTTRANSWARENGSP) from 1997 to 2024 about warehousing, UT, transportation, GSP, private industries, private, industry, GDP, and USA.

This data depicts the Utah State Routes speed limits as polylines. This data includes 'N' for divided highways only. The 'P' direction is used to depict the speed in both directions on all non-divided routes. This data was developed by the Division of Traffic and Safety using the 2021 Mandli sign inventory data. This data is current as of September 2021. Speed limit data changes frequently; therefore, this data should be used as an approximation only. If you have questions please contact Jonathan Harman at jharman@utah.gov or Clancy Black at clancyblack@utah.gov. This data is updated every two years when new sign asset data is available. UDOT Traffic and Safety is working on plans to provide a more up to date dataset. This data does not have an update cycle and does not include the variable speed limit data along I-80.