Content

Average Daily Traffic (ADT) counts are analogous to a census count of vehicles on city streets. These counts provide a close approximation to the actual number of vehicles passing through a given location on an average weekday. Since it is not possible to count every vehicle on every city street, sample counts are taken along larger streets to get an estimate of traffic on half-mile or one-mile street segments. ADT counts are used by city planners, transportation engineers, real-estate developers, marketers and many others for myriad planning and operational purposes. Data Owner: Transportation. Time Period: 2006. Frequency: A citywide count is taken approximately every 10 years. A limited number of traffic counts will be taken and added to the list periodically. Related Applications: Traffic Information Interactive Map (http://webapps.cityofchicago.org/traffic/).

Context

This is a dataset hosted by the City of Chicago. The city has an open data platform found here and they update their information according the amount of data that is brought in. Explore the City of Chicago using Kaggle and all of the data sources available through the City of Chicago organization page!

• Update Frequency: This dataset is updated annually.

Acknowledgements

This dataset is maintained using Socrata's API and Kaggle's API. Socrata has assisted countless organizations with hosting their open data and has been an integral part of the process of bringing more data to the public.

Cover photo by Denys Nevozhai on Unsplash
Unsplash Images are distributed under a unique Unsplash License.

This hosted feature layer has been published in RI State Plane Feet NAD 83.This data set was created for the Rhode Island Dept. of Transportation. This data set contains locations for the 24 hour average daily traffic counts on state maintained roads with information containing the station number, the segment of roadway the count was taken on, the city the count location is in and the actual 24 hour average counts for each location.This data set contains the annual 24 Hour Average Daily Traffic Count Locations on State maintained roads in Rhode Island for 2001.

Annual average daily traffic is the total volume for the year divided by 365 days. The traffic count year is from October 1st through September 30th. Very few locations in California are actually counted continuously. Traffic Counting is generally performed by electronic counting instruments moved from location throughout the State in a program of continuous traffic count sampling. The resulting counts are adjusted to an estimate of annual average daily traffic by compensating for seasonal influence, weekly variation and other variables which may be present. Annual ADT is necessary for presenting a statewide picture of traffic flow, evaluating traffic trends, computing accident rates. planning and designing highways and other purposes.Traffic Census Program Page

Esri ArcGIS Online (AGOL) Hosted Feature Layer for accessing the MDOT SHA Annual Average Daily Traffic (AADT) data product.MDOT SHA Annual Average Daily Traffic (AADT) data consists of linear & point geometric features which represent the geographic locations & segments of roadway throughout the State of Maryland that include traffic volume information. Traffic volume information is produced from traffic counts used to calculate annual average daily traffic (AADT), annual average weekday traffic (AAWDT), AADT based on vehicle class (current year only) for roadways throughout the State. Ten (10) years of historic AADT & AAWDT traffic volume metrics are also available for each geographic location or segment of roadway throughout the State, where applicable.Annual Average Daily Traffic (AADT) data is collected from over 8700 program count stations and 84 ATRs, located throughout Maryland. The quality control feature of the system allow data edit checks and validation for data from the 91 permanent, continuous automatic traffic recorders (ATRs) and short-term traffic counts. Program count data is collected in both directions (inventory & non-inventory) at regular locations on either a three (3) year or six (6) year cycle depending on the type of roadway. Growth factors are applied to counts which were not taken during the current year and the counts are factored based on the past yearly growth of an associated ATR. Counters are placed for 48 hours on a Monday or Tuesday and are picked up that Thursday or Friday, respectively. The ATR and toll count data is collected on a continuous basis. Toll station data is provided by the Maryland Transportation Authority (MDTA). A special numeric code was added to the AADT numbers, starting in 2006, to identify the years when the count was actually taken. The last digit represents the number of years prior to the actual count. Where “0” represents the current year when data was collected (in 2020), “1” represents the count taken in 2019, “2” represents the count taken in 2018, “3” represents the count taken in 2017 and so forth.Annual Average Daily Traffic (AADT) data is a strategic resource for the Federal Highway Administration (FHWA), the Maryland Department of Transportation (MDOT), the Maryland Department of Transportation State Highway Administration (MDOT SHA), as well as many other Federal, State & local government agencies. The data is essential in the planning, design and operation of the statewide road system and the development & implementation of State highway improvement & safety programs. The MDOT SHA Traffic Monitoring System (TMS) is a product of the ISTEA Act of 1991, which required a traffic data program to effectively & efficiently meet MDOT SHA’s long-term traffic data monitoring & reporting requirements.Annual Average Daily Traffic (AADT) data is updated & published on an annual basis for the prior year. This data is for the year 2023.View the most current AADT data in the MDOT SHA Annual Average Daily Traffic (AADT) LocatorFor more AADT data information, contact MDOT SHA OPPE Traffic Monitoring System (TMS) Unit:Email: TMS@mdot.maryland.govFor more general information, contact MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

Average Annual Daily Traffic data for use with GIS mapping software, databases, and web applications are from Caliper Corporation and contain data on the total volume of vehicle traffic on a highway or road for a year divided by 365 days.

The census count of vehicles on city streets is normally reported in the form of Average Daily Traffic (ADT) counts. These counts provide a good estimate for the actual number of vehicles on an average weekday at select street segments. Specific block segments are selected for a count because they are deemed as representative of a larger segment on the same roadway. ADT counts are used by transportation engineers, economists, real estate agents, planners, and others professionals for planning and operational analysis. The frequency for each count varies depending on City staff’s needs for analysis in any given area. This report covers the counts taken in our City during the past 12 years approximately.

This data set features a hyperlink to the New York State Department of Transportation’s (NYSDOT) Traffic Data (TD) Viewer web page, which includes a link to the Traffic Data interactive map. The Traffic Data Viewer is a geospatially based Geographic Information System (GIS) application for displaying data contained in the roadway inventory database. The interactive map has five viewable data categories or ‘layers’. The five layers include: Average Daily Traffic (ADT); Continuous Counts; Short Counts; Bridges; and Grade Crossings throughout New York State.

The FDOT Annual Average Daily Traffic feature class provides spatial information on Annual Average Daily Traffic section breaks for the state of Florida. In addition, it provides affiliated traffic information like KFCTR, DFCTR and TFCTR among others. This dataset is maintained by the Transportation Data & Analytics office (TDA). The source spatial data for this hosted feature layer was created on: 07/12/2025.Download Data: Enter Guest as Username to download the source shapefile from here: https://ftp.fdot.gov/file/d/FTP/FDOT/co/planning/transtat/gis/shapefiles/aadt.zip

Traffic volume of Roadway Blocks. The dataset contains traffic volume data, created as part of the District of Columbia, Department of Transportation (DDOT) Roads and Highways database. A database provided by the District of Columbia, Department of Transportation identified traffic volume. Count data is collected (both direction) at pre-selected locations on Highway Performance Monitoring System (HPMS) Sections on a three-year cycle. These counts are converted to Annual Average Daily Traffic (AADT).

This is a MD iMAP hosted service layer. Find more information at http://imap.maryland.gov. Traffic monitoring data is a strategic resource for SHA and Maryland's Department of Transportation. The data is essential in the planning - design and operation of the statewide road system and the development and implementation of state highway improvement and safety programs. TMS is a product of the ISTEA Act of 1991 - which required a traffic data program to effectively and efficiently meet SHA's long-term traffic data monitoring and reporting requirements. The quality control feature of the system allow data edit checks and validation for data from the 84 permanent - continuous automatic traffic recorders (ATRs) and short-term traffic counts.The Maryland Traffic Volume Maps depict the Annual Average Daily Traffic (AADT) at various locations on Maryland's roadways by county. Traffic Volume data is collected from over 8700 program count stations and 84 ATRs - located throughout Maryland. To date - four (4) ATRs have been removed from the ATR Program. Program count data is collected (both directions) at regular locations on either a three (3) year or six (6) year cycle depending on type of roadway. Growth Factors are applied to counts which were not taken during the current year and the counts are factored based on the past yearly growth of an associated ATR. Counters are placed for 48 hours on a Monday or Tuesday and are picked up that Thursday or Friday - respectively. The ATR and toll count data is collected on a continuous basis. Toll station data is provided by the Maryland Transportation Authority. A special numeric code was added to the AADT numbers - starting in 2006 - to identify the years when the count was actually taken. The last digit represents the number of years prior to the actual count. Where '0' represents the current year when data was collected (in 2014) - '1' represents the count taken in 2013 - '2' represents the count taken in 2012 - '3' represents the count taken in 2011 and so forth. Last Updated: Feature Service Layer Link: https://mdgeodata.md.gov/imap/rest/services/Transportation/MD_AnnualAverageDailyTraffic/FeatureServer ADDITIONAL LICENSE TERMS: The Spatial Data and the information therein (collectively "the Data") is provided "as is" without warranty of any kind either expressed implied or statutory. The user assumes the entire risk as to quality and performance of the Data. No guarantee of accuracy is granted nor is any responsibility for reliance thereon assumed. In no event shall the State of Maryland be liable for direct indirect incidental consequential or special damages of any kind. The State of Maryland does not accept liability for any damages or misrepresentation caused by inaccuracies in the Data or as a result to changes to the Data nor is there responsibility assumed to maintain the Data in any manner or form. The Data can be freely distributed as long as the metadata entry is not modified or deleted. Any data derived from the Data must acknowledge the State of Maryland in the metadata.

AADT represents current (most recent) Annual Average Daily Traffic on sampled road systems. This information is displayed using the Traffic Count Locations Active feature class as of the annual HPMS freeze in January. Historical AADT is found in another table. Please note that updates to this dataset are on an annual basis, therefore the data may not match ground conditions or may not be available for new roadways. Resource Contact: Christy Prentice, Traffic Forecasting & Analysis (TFA), http://www.dot.state.mn.us/tda/contacts.html#TFA

Check other metadata records in this package for more information on Annual Average Daily Traffic Locations Information.


Link to ESRI Feature Service:

Annual Average Daily Traffic Locations in Minnesota: Annual Average Daily Traffic Locations

Important Note: This item is in mature support as of June 2023 and will be retired in December 2025.This map shows traffic counts in the United States, collected through 2022 in a multiscale map. Traffic counts are widely used for site selection by real estate firms and franchises. Traffic counts are also used by departments of transportation for highway funding. This map is best viewed at large scales where you can click on each point to access up to five different traffic counts over time. At medium to small scales, comparisons along major roads are possible. The Business Basemap has been added to provide context at medium and small scales. It shows the location of businesses in the United States and helps to understand where and why traffic counts are collected and used. The pop-up is configured to display the following information:The most recent traffic countThe street name where the count was collectedThey type of count that was taken. See the methodology document for definitions of count types such as AADT - Average Annual Daily Traffic. Traffic Counts seasonally adjusted to represent the average day of the year. AADT counts represent counts taken Sunday—Saturday.A graph displaying up to five traffic counts taken at the same location over time. Permitted use of this data is covered in the DATA section of the Esri Master Agreement (E204CW) and these supplemental terms.

A collection of historic traffic count data and guidelines for how to collect new data for Massachusetts Department of Transportation (MassDOT) projects.

Feature layer containing authoritative traffic count points for Sioux Falls, South Dakota.The traffic counts listed are 24-hour, weekday, two-directional counts. Traffic counts are normally collected during the summer months, but may be taken any season, as weather permits. The traffic counts are factored by the day of the week as well as by the month of the year to become an Average Annual Daily Total (AADT). Traffic volumes (i.e. count data) can fluctuate depending on the month, week, day of collection; the weather, type of road surface, nearby construction, etc. All of the historical data should be averaged to reflect the "normal" traffic count. More specific count data (time, date, hourly volume) can be obtained from the Sioux Falls Engineering Division at 367-8601.

Annualized, Hourly and Classification count data for the TPB modeled region. Data are collected from state DOTs and processed by TPB staff.Layers IncludedAnnualized Traffic Volumes Historic AADT by Count Station This database contains the Annual Average Daily Traffic (AADT) estimates reported at permanent and short term counting stations in the TPB modeled region. Please note: Interstates in Virginia are typically represented by two stations (one in each direction) while Interstates in the other states are represented by one station. Therefore, the AADT estimates displayed for the stations on Virginia Intestates will be around half of the total for the directional roadway. The AADT estimates for recent years in this file are based on counts taken at the actual count station locations that are indicated by the station points. The AADT estimates for earlier years are based on volumes reported along roadway segments that the station points currently represent. Specific data sources for each state are listed below:District of ColumbiaAADT estimates since 2006 are based on counts taken at the station locations in the file for purpose of Federal HPMS reporting.AADT estimates prior to 2006 are based on Traffic Volume maps produced by DDOT (Formerly DC DPW).MarylandAADT estimates since 2000 are based on counts taken at the station locations in the file and reported by MD SHA.AADT estimates prior to 2000 are based on volumes reported by MD SHA in the Highway Location Reference documents and matched to links in the COG/TPB highway network. The volumes are shown at the count locations that currently represent those network links.VirginiaAADT estimates since 1997 are based on counts taken at the station locations in the file and reported by VDOT.AADT estimates prior to 1997 are based on volumes reported by VDOT in the Average Daily Traffic Volumes documents and matched to links in the COG/TPB highway network. The volumes are shown at the count locations that currently represent those network links.West VirginiaAADT estimates since 1999 are based on counts taken at the station locations in the file and reported by WV DOT.Traffic Counts by Network LinkThis layer was created by assigning the state DOT traffic counting station locations to their corresponding COG/TPB network links. Facility names and route numbers were added to the network. AADT Average Annual Daily Traffic (2010 - 2021), AAWDT Average Annual Weekday Daily Traffic (2010 - 2021) and Count Type (2010 - 2021) are included as well as Count Year (last year the link was counted). Count Type denotes the source of the count. Please note: for bi-directional roads, the AADT and AAWDT values for each location were divided in two and assigned to both network links that represent the Anode-Bnode direction and the Bnode-Anode direction. Therefore, in most cases the AADT/AAWDT values associated with an individual link in this network will be half of the AADT/AAWDT values reported at the associated individual count station point. Traffic Counts by External StationThis layer was created by placing points where major facilities cross the TPB Modeled Area boundary. In some cases, the external station represents more than one facility. The facility field indicates which road or roads the station represents. AADT and AAWDT estimates at external stations are provided for 2007 through 2023. Each external station is assigned to a state DOT traffic counting station(s). An effort was made to assign stations or combinations of stations that would come closest to measuring the traffic volume on each facility as it enters/exits the region. In some cases, these volumes are measured just inside the modeled area; in other cases, the volumes are measured just outside the modeled area. The external stations around the Baltimore Beltway are exceptions to this rule. These stations all measure the traffic just south of the Baltimore Beltway in order lessen the influence of traffic specific to Baltimore. AADT Average Annual Daily Traffic (2007 – 2023) and AAWDT Average Annual Weekday Daily Traffic (2007 – 2023) are included. Count Type denotes when the location was last counted. West Virginia does not report AAWDT, so the AADT values were increased by 5% to arrive at AAWDT estimates in West Virginia.

HCAADT represents current (most recent) Heavy Commercial Annual Average Daily Traffic on sampled road systems. This information is displayed using the Traffic Count Locs Active feature class as of the annual HPMS freeze in January. Historical HCAADT is found in another table. Please note that updates to this dataset are on an annual basis, therefore the data may not match ground conditions or may not be available for new roadways. Resource Contact: John Hackett, Traffic Forecasting & Analysis (TFA), http://www.dot.state.mn.us/tda/contacts.html#TFA

Check other metadata records in this package for more information on Heavy Commercial Annual Average Daily Traffic Locations Information.


Link to ESRI Feature Service:

Heavy Commercial Annual Average Daily Traffic Locations in Minnesota: Heavy Commercial Annual Average Daily Traffic Locations

Annual Average Daily Traffic (AADT) is an estimate of the average daily traffic along a defined segment of roadway. This value is calculated from short term counts taken along the same section which are then factored to produce the estimate of AADT. Because of this process, the most recent AADT for any given roadway will always be for the previous year. Data is available for all New York State Routes and roads that are part of the Federal Aid System.

The New Jersey Department of Transportation collects traffic data at over 4300 station locations along all Interstate, U.S. , N.J. and County Routes throughout the State of New Jersey. This map represents the estimated Annual Average Daily Traffic (AADT) values based on the most current station data available. The AADT Flow layer data is displayed in six (6) groups, five (5) representing graduated AADT ranges and one (1) representing no station data. The traffic information is used for planning, design, maintenance and general administration of the roadway systems.