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: 06/14/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

Description

This dataset contains hourly data on the traffic volume for westbound I-94, a major interstate highway in the US that connects Minneapolis and St Paul, Minnesota. The data was collected by the Minnesota Department of Transportation (MnDOT) from 2012 to 2018 at a station roughly midway between the two cities.

Key Features

• holiday: a categorical variable that indicates whether the date is a US national holiday or a regional holiday (such as the Minnesota State Fair).
• temp: a numeric variable that shows the average temperature in kelvin.
• rain_1h: a numeric variable that shows the amount of rain in mm that occurred in the hour.
• snow_1h: a numeric variable that shows the amount of snow in mm that occurred in the hour.
• clouds_all: a numeric variable that shows the percentage of cloud cover.
• weather_main: a categorical variable that gives a short textual description of the current weather (such as Clear, Clouds, Rain, etc.).
• weather_description: a categorical variable that gives a longer textual description of the current weather (such as light rain, overcast clouds, etc.).
• date_time: a datetime variable that shows the hour of the data collected in local CST time.
• traffic_volume: a numeric variable that shows the hourly I-94 reported westbound traffic volume.

Potential Use Cases

The dataset can be used for regression tasks to predict the traffic volume based on the weather and holiday features. It can also be used for exploratory data analysis to understand the patterns and trends of traffic volume over time and across different conditions.

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.

TERMS OF USE 1. Restriction on the use of Material on this websiteUsage and/or downloading this data indicates Your acceptance of the terms and conditions below.The data here controlled and operated by the Corporation of the County of Lennox and Addington (referred to the “County” herein) and is protected by copyright. No part of the information herein may be sold, copied, distributed, or transmitted in any form without the prior written consent of the County. All rights reserved. Copyright 2018 by the Corporation of the County of Lennox and Addington.2. DisclaimerThe County makes no representation, warranty or guarantee as to the content, accuracy, currency or completeness of any of the information provided on this website. The County explicitly disclaims any representations, warranties and guarantees, including, without limitation, the implied warranties of merchantability and fitness for a particular purpose.3. Limitation of LiabilityThe County is not responsible for any special, indirect, incidental or consequential damages that may arise from the use of or the inability to use, any web pages and/or the materials contained on the web page whether the materials are provided by the County or by a third party. Without limiting the generality of the foregoing, the County assumes no responsibility whatsoever for: any errors omissions, or inaccuracies in the information provided, regardless of how caused; or any decision made or action taken or not taken by the reader or other third party in reliance upon any information or data furnished on any web page.The Data is provided "as is" without warranty or any representation of accuracy, timeliness or completeness. The burden for determining accuracy, completeness, timeliness, merchantability and fitness for or the appropriateness for use rests solely on the requester. Lennox and Addington County makes no warranties, express or implied, as to the use of the Data. There are no implied warranties of merchantability or fitness for a particular purpose. The requester acknowledges and accepts the limitations of the Data, including the fact that the Data is dynamic and is in a constant state of maintenance, corrections and update.

Road Safety Statistics releases [missing hyperlink]

Data download tool [missing hyperlink] for bespoke breakdowns of our data.

These files provide detailed road safety data about the circumstances of personal injury road accidents in GB from 1979, the types of vehicles involved and the consequential casualties. The statistics relate only to personal injury accidents on public roads that are reported to the police, and subsequently recorded, using the STATS19 accident reporting form.

There has been an increasing demand for more up to date information on reported road accidents to be made available to the public, stakeholders and researchers. As a result, the Department for Transport made a dataset covering accidents for the first and second quarters of 2018 in Great Britain available for the first time on data.gov.uk. The data released was an un-validated subset and has been superseded by the full accident dataset for 2018, released after validation for the full year.

All the data variables are coded rather than containing textual strings. The lookup tables are available in the "Additional resources" section towards the bottom of the table.

Please note that the 2015 data were revised on the 29th September 2016. Accident, Vehicle and Casualty data for 2005 - 2009 are available in the time series files under 2014. Data for 1979 - 2004 are available as a single download under 2004 below.

Also includes: Results of breath-test screening data from recently introduced digital breath testing devices, as provided by Police Authorities in England and Wales Results of blood alcohol levels (milligrams / 100 millilitres of blood) provided by matching coroners’ data (provided by Coroners in England and Wales and by Procurators Fiscal in Scotland) with fatality data from the STATS19 police data of road accidents in Great Britain. For cases when the Blood Alcohol Levels for a fatality are "unknown" are a consequence of an unsuccessful match between the two data sets.

Daily data showing weekday adjusted busyness indices using traffic camera data to monitor flows of cars, pedestrians, cyclists, buses and commercial vehicles for selected cities and regions of the UK. These are official statistics in development. Source: Transport for London, Transport for Greater Manchester

The City of Toronto's Transportation Services Division collects short-term traffic count data across the City on an ad-hoc basis to support a variety of safety initiatives and projects. The data available in this repository are a full collection of Speed, Volume and Classification Counts conducted across the City since 1993. The two most common types of short-term traffic counts are Turning Movement Counts and Speed / Volume / Classification Counts. Turning Movement Count data, comprised of motor vehicle, bicycle and pedestrian movements through intersections, can be found here. Speed / Volume / Classification Counts are collected using pneumatic rubber tubes installed across the roadway. This dataset is a critical input into transportation safety initiatives, infrastructure design and program design such as speed limit changes, signal coordination studies, traffic calming and complete street designs. Each Speed / Volume / Classification Count is comprised of motor vehicle count data collected over a continuous 24-hour to 168-hour period (1-7 days), at a single location. A handful of non-standard 2-week counts are also included. Some key notes about these counts include: Not all counts have complete speed and classification data. These data are provided for locations and dates only where they exist. Raw data are recorded in 15-minute intervals. Raw data are recorded separately for each direction of traffic movement. Some data are only available for one direction, even if the street is two-way. Within each 15 minute interval, speed data are aggregated into approximately 5 km/h increments. Within each 15 minute interval, classification data are aggregated into vehicle type bins by the number of axles, according to the FHWA classification system attached below. The following files showing different views of the data are available: Data Dictionary (svc_data_dictionary.xlsx): Provides a detailed definition of every data field in all files. Summary Data (svc_summary_data): Provides metadata about every Speed / Volume / Classification Count available, including information about the count location and count date, as well as summary data about each count (total vehicle volumes, average daily volumes, a.m. and p.m. peak hour volumes, average / 85 percentile / 95 percentile speeds, where available, and heavy vehicle percentage, where available). Most Recent Count Data (svc_most_recent_summary_data): Provides metadata about the most recent Speed / Volume / Classification Count data available at each location for which a count exists, including information about the count location and count date, as well as the summary data provided in the “Summary Data” file (see above). Raw Data: Raw data is available in 15-minute intervals, and is distributed into one of three different file types based on the count type: volume-only, speed and volume, or classification and volume. If you’re looking for 15-minute data for a specific count, identify the count type and count date, then download the raw data file associated with the count type and period. If you’re looking for volume data for all count types, you will need to download and aggregate all three file types for a given period. Volume Raw Data (svc_raw_data_volume_yyyy_yyyy): These files—grouped by 5-10 year interval—provide volume data in 15-minute intervals, for each direction separately. You will find the raw data for volume-only counts (ATR_VOLUME) here. Speed and Volume Raw Data (svc_raw_data_speed_yyyy_yyyy): These files—grouped by 5-10 year interval—provide volume data aggregated into speed bins in approximately 5 km/h increments. Speed data are not available for all counts. You will find the raw data for speed and volume counts (ATR_SPEED_VOLUME) here. Classification and Volume Raw Data (svc_raw_data_classification_yyyy_yyyy): These files—grouped by 5-10 year interval—provide volume data aggregated into vehicle type bins by the number of axles, according to the FHWA classification system. Classification data are not available for all counts. You will find the raw data for classification and volume counts (VEHICLE_CLASS) here. FHWA Classification Reference (fhwa_classification.png): Provides a reference for the FHWA classification system. This dataset references the City of Toronto's Street Centreline dataset, Intersection File dataset and Street Traffic Signal dataset.

Download the data on road traffic accidents in Germany. These are data from road accident statistics. This is based on the accident reports from the police departments.

Traffic count data downloaded from GDOT public map here: https://gdottrafficdata.drakewell.com/publicmultinodemap.aspRetrieved Annual Statistics Reports: "All Station AADT and Truck Percent Statistics." Mapped by Lat/Long field.Retrieved and rehosted for staff use and overlay on city maps on 12/14/2018."The Georgia Department of Transportation’s Traffic Analysis and Data Application (TADA!) website presents data collected from the Georgia Traffic Monitoring Program located on the public roads in Georgia. The Website uses a dynamic mapping interface to allow the User to access data from the map as well as in a variety of report, graph, and data export formats."

The real_time data shows the collection of real-time traffic volumes and observed travel speeds on a selected set of roadways in the state. The real_time data is the most recent two days (maximum) of traffic volumes and traffic speeds collected from the time traffic monitors are activated and shown in the most recent 2-day intervals until the activated monitors are turned off. Therefore a single station on the map will have a number of records tied to it showing the traffic volume and speed changes for that roadway section over a two day interval. Real-time polling is activated for a hurricane or other emergencies in Florida. This dataset is maintained by the Transportation Data & Analytics office (TDA). This hosted feature layer was updated on: 06-08-2025 23:35:03.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/special_projects/real_time/real_time.zip

Traffic volumes data across Dublin City from the SCATS traffic management system. The Sydney Coordinated Adaptive Traffic System (SCATS) is an intelligent transportation system used to manage timing of signal phases at traffic signals. SCATS uses sensors at each traffic signal to detect vehicle presence in each lane and pedestrians waiting to cross at the local site. The vehicle sensors are generally inductive loops installed within the road. For SCATS junctions locations see: https://data.smartdublin.ie/dataset/traffic-signals-and-scats-sites-locations-dcc NB These are large data files. There would be too many rows for downloading with certain programmes such as Excel. Please choose a software package which can manage such large data files. 3 resources are provided: SCATS Traffic Volumes Data (Monthly) Contained in this report are traffic counts taken from the SCATS traffic detectors located at junctions. The primary function for these traffic detectors is for traffic signal control. Such devices can also count general traffic volumes at defined locations on approach to a junction. These devices are set at specific locations on approaches to the junction but may not be on all approaches to a junction. As there are multiple junctions on any one route, it could be expected that a vehicle would be counted multiple times as it progress along the route. Thus the traffic volume counts here are best used to represent trends in vehicle movement by selecting a specific junction on the route which best represents the overall traffic flows. Information provided: End Time: time that one hour count period finishes. Region: location of the detector site (e.g. North City, West City, etc). Site: this can be matched with the SCATS Sites file to show location Detector: the detectors/ sensors at each site are numbered Sum volume: total traffic volumes in preceding hour Avg volume: average traffic volumes per 5 minute interval in preceding hour All Dates Traffic Volumes Data This file contains daily totals of traffic flow at each site location. SCATS Site Location Data Contained in this report, the location data for the SCATS sites is provided. The meta data provided includes the following; Site id – This is a unique identifier for each junction on SCATS Site description( CAP) – Descriptive location of the junction containing street name(s) intersecting streets Site description (lower) - – Descriptive location of the junction containing street name(s) intersecting streets Region – The area of the city, adjoining local authority, region that the site is located LAT/LONG – Coordinates Disclaimer: the location files are regularly updated to represent the locations of SCATS sites under the control of Dublin City Council. However site accuracy is not absolute. Information for LAT/LONG and region may not be available for all sites contained. It is at the discretion of the user to link the files for analysis and to create further data. Furthermore, detector communication issues or faulty detectors could also result in an inaccurate result for a given period, so values should not be taken as absolute but can be used to indicate trends.

Road Traffic Volumes by Fuel Type, County of Ownership, Year of Registration, Type of Vehicle, Year and Statistic

View data using web pages

Download .px file (Software required)

The City of Perth traffic count provides information about the number of vehicles, speed of travel and peak travel numbers on particular roads within the Perth LGA (Local Government Area). Show full description

Road Traffic Volumes by Detailed Vehicle Type, Year and Statistic

View data using web pages

Download .px file (Software required)

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.

Road Traffic Volumes by Fuel Type, County of Ownership, Year of Registration, Type of Vehicle, Year and Statistic

View data using web pages

Download .px file (Software required)

Road Traffic Volumes by Month of Reg, Type of Vehicle, Year and Statistic

View data using web pages

Download .px file (Software required)

Road Safety Statistics releases and guidance about the data collection. Collision analysis tool for bespoke breakdowns of our data. STATS19 R package developed independently of DfT, offering an alternative way to access this data for those familiar with the R language. Latest data Provisional data for the first 6 months of 2024 published 28 November 2024. These are provisional un-validated data. Data included These files provide detailed road safety data about the circumstances of personal injury road collisions in Great Britain from 1979, the types of vehicles involved and the consequential casualties. The statistics relate only to personal injury collisions on public roads that are reported to the police, and subsequently recorded, using the STATS19 collision reporting form. This data contains all the non-sensitive fields that can be made public. Sensitive data fields, for example contributory factors data, can be requested by completing the sensitive data form and contacting the road safety statistics team at roadacc.stats@dft.gov.uk All the data variables are coded rather than containing textual strings. The lookup tables are available in the supporting documents section towards the bottom of the table. Data relating to the casualty and collision severity adjustment to account for changes in police reporting of severity is provided in separate files and can be joined using the appropriate record identifiers. Timing of data release Final annual data is released annually in late September following the publication of the annual reported road casualties Great Britain statistical publication. Individual years data is available for each of the last 5 years, with earlier years available as part of a single download. In addition, un-validated provisional mid-year data (covering January to June) is released at end November, to provide more up to date information Data revisions Except for the severity adjustments, data are not routinely revised those occasionally minor amendments to previous years can be made. Details of recent revisions are available, together with a request for any feedback on the approach to revising the data. The files published here represent the latest data.