The dataset represents synthetic traffic data for a certain location over a one-year period. It includes information about the traffic volume, weather conditions, and special events that may affect traffic.

Features:

Timestamp: The date and time of the observation.Weather: The weather condition at the time of the observation (e.g., Clear, Cloudy, Rain, Snow).

Events: A binary variable indicating whether there was a special event affecting traffic at the time of the observation (True or False).

Traffic Volume: The volume of traffic at the location at the time of the observation.

The dataset is intended for use in analyzing traffic patterns and trends, as well as for developing and testing models related to traffic prediction and management.

This dataset is designed for urban traffic flow prediction and includes temporal, spatial, and categorical features essential for analyzing traffic patterns.

Key Features: Timestamp: Records the exact date and time in 15-minute intervals, enabling the modeling of temporal dependencies. Location: Identifies the traffic sensor locations (e.g., Sensor_01, Sensor_02), capturing spatial variability. Vehicle_Count: Represents the number of vehicles detected by sensors during each interval. Vehicle_Speed: Measures the average speed of vehicles in km/h, indicating traffic conditions. Congestion_Level: An ordinal variable representing traffic congestion on a scale (e.g., 0 for no congestion, 5 for high congestion). Peak_Off_Peak: Categorical data distinguishing between peak and off-peak hours for better contextual analysis. Target_Vehicle_Count: The predicted vehicle count for the subsequent time interval, serving as the target variable for predictive modeling. Data Overview: Rows: 200 Columns: 7 Temporal Coverage: 2 days and 15 minutes intervals, providing high-resolution data for short-term prediction.

This dataset contains the San Francisco Traffic dataset used by Lai et al. (2017). It contains 862 hourly time series showing the road occupancy rates on the San Francisco Bay area freeways from 2015 to 2016.

a packet sniffer software

NYCDOT's Traffic Management Center (TMC) maintains a map of traffic speed detectors throughout the City. The speed detector themselves belong to various city and state agencies. The Traffic Speeds Map is available on the DOT's website. This data feed contains 'real-time' traffic information from locations where NYCDOT picks up sensor feeds within the five boroughs, mostly on major arterials and highways. NYCDOT uses this information for emergency response and management.

Here's the link to the original dataset.

In Bangladesh, people are sadly not very much concerned about traffic rules. This study focuses on traffic flow patterns at two junctions in Dhaka, Shapla Chattar and Notre Dame College. Footover bridges at both junctions were used to collect video data, which captured single-lane and double-lane traffic situations involving different types of vehicles and also pedestrians crossing. The dataset comprises approximately 5774 images extracted from the videos, taken at five different time periods on a weekday. This dataset provides a unique view on traffic situations in Dhaka, Bangladesh, by presenting unstructured traffic environments at two busy consecutive junctions. Monitoring vehicle fitness, examining pedestrian behavior, and measuring vehicle flow are all possible applications. Researchers can use different machine learning techniques in these areas.

Daily utilization metrics for data.lacity.org and geohub.lacity.org. Updated monthly

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 dataset contains the current estimated speed for about 1250 segments covering 300 miles of arterial roads. For a more detailed description, please go to https://tas.chicago.gov, click the About button at the bottom of the page, and then the MAP LAYERS tab. The Chicago Traffic Tracker estimates traffic congestion on Chicago’s arterial streets (nonfreeway streets) in real-time by continuously monitoring and analyzing GPS traces received from Chicago Transit Authority (CTA) buses. Two types of congestion estimates are produced every ten minutes: 1) by Traffic Segments and 2) by Traffic Regions or Zones. Congestion estimate by traffic segments gives the observed speed typically for one-half mile of a street in one direction of traffic. Traffic Segment level congestion is available for about 300 miles of principal arterials. Congestion by Traffic Region gives the average traffic condition for all arterial street segments within a region. A traffic region is comprised of two or three community areas with comparable traffic patterns. 29 regions are created to cover the entire city (except O’Hare airport area). This dataset contains the current estimated speed for about 1250 segments covering 300 miles of arterial roads. There is much volatility in traffic segment speed. However, the congestion estimates for the traffic regions remain consistent for relatively longer period. Most volatility in arterial speed comes from the very nature of the arterials themselves. Due to a myriad of factors, including but not limited to frequent intersections, traffic signals, transit movements, availability of alternative routes, crashes, short length of the segments, etc. speed on individual arterial segments can fluctuate from heavily congested to no congestion and back in a few minutes. The segment speed and traffic region congestion estimates together may give a better understanding of the actual traffic conditions.

Dataset from Land Transport Authority. For more information, visit https://data.gov.sg/datasets/d_3136f317a1f282a33fe7a2f6a907c047/view

Traffic Dataset - 500 Videos

Dataset comprises 500 videos of urban traffic captured by surveillance cameras, providing real-time traffic data enriched with bounding box annotations for vehicles and pedestrians. Designed for traffic monitoring and safety research, the dataset supports tasks like vehicle detection, traffic flow analysis, and accident prediction. By leveraging this dataset, researchers and engineers can advance real-time object detection, traffic surveillance systems… See the full description on the dataset page: https://huggingface.co/datasets/UniDataPro/real-time-traffic-video-dataset.

Explore our detailed website traffic dataset featuring key metrics like page views, session duration, bounce rate, traffic source, and conversion rates.

The Smart Mobility and Traffic Optimization Dataset integrates data from cyber-physical networks (CPNs) and social networks (SNs) to improve traffic management and smart mobility solutions. By combining real-time traffic patterns, vehicle telemetry, ride-sharing demand, public transport efficiency, social media sentiment, and environmental factors, this dataset provides a comprehensive foundation for optimizing urban mobility.

Designed to support machine learning models, the dataset enables accurate predictions of traffic congestion, mobility optimization, and smart city planning. It incorporates key metrics such as vehicle density, road occupancy, weather conditions, social media feedback, and emissions data to generate actionable insights.

Key Features: Traffic Data: Includes vehicle count, speed, road occupancy, and traffic light status, offering a granular view of real-time traffic conditions. Weather & Accidents: Integrates weather conditions and accident reports to assess their impact on congestion levels. Social Network Sentiment: Analyzes public opinions and complaints about mobility and congestion, extracted from social media platforms. Smart Mobility Factors: Examines ride-sharing demand, parking availability, and public transport delays, aiding in urban mobility planning. Environmental Impact: Monitors CO₂ emissions and pollution levels, ensuring eco-friendly traffic optimization. Target Variable: The dataset categorizes traffic congestion levels into three main groups: Low, Medium, or High, based on real-time traffic density, speed, and road occupancy.

This dataset is an essential resource for urban planners, smart city developers, and AI researchers, empowering them to create intelligent mobility solutions that reduce congestion, enhance efficiency, and improve overall urban sustainability.

Traffic Volume (24hr count). Data are updated as needed by the Transportation department (typically in the summer), and subsequently copied to VicMap and the Open Data Portal the following day.Traffic speed and volume data are collected at various locations around the city, from different locations each year, using a variety of technologies and manual counting. Counters are placed on streets and at intersections, typically for 24-hour periods. Targeted information is also collected during morning or afternoon peak period travel times and can also be done for several days at a time to capture variability on different days of the week. The City collects data year-round and in all types of weather (except for extreme events like snowstorms). The City also uses data from our agency partners like Victoria Police, the CRD or ICBC. Speed values recorded at each location represent the 85th percentile speed, which means 85% or less traffic travels at that speed. This is standard practice among municipalities to reduce anomalies due to excessively speedy or excessively slow drivers. Values recorded are based on the entire 24-hour period.The Traffic Volume dataset is linear. The lines can be symbolized using arrows and the "Direction" attribute. Where the direction value is "one", use an arrow symbol where the arrow is at the end of the line. Where the direction value is "both", use an arrow symbol where there are arrows at both ends of the line. Use the "Label" field to add labels. The label field indicates the traffic volume at each location, and the year the data was collected. So for example, “2108(05)” means 2108 vehicles were counted in the year 2005 at that location.Data are automatically copied to the Open Data Portal. The "Last Updated" date shown on our Open Data Portal refers to the last time the data schema was modified in the portal, or any changes were made to this description. We update our data through automated scripts which does not trigger the "last updated" date to change. Note: Attributes represent each field in a dataset, and some fields will contain information such as ID numbers. As a result some visualizations on the tabs on our Open Data page will not be relevant.

The main aim of this dataset is to enable detection of traffic congestion from surveillance cameras using one-stage object detectors. The dataset contains congested and uncongested traffic scenes with their respective labels. This dataset is collected from different surveillance cameras video footage. To prepare the dataset frames are extracted from video sources and resized to a dimension of 500 x 500 with .jpg image format. To Annotate, the image LabelImg software has used. The format of the label is .txt with the same name as the image. The dataset is mainly prepared for YOLO Models but it can be converted to other models format.

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.

Linear network representing the estimated traffic flows for roads and highways managed by the Ministry of Transport and Sustainable Mobility (MTMD). These flows are obtained using a statistical estimation method applied to data from more than 4,500 collection sites spread over the main roads of Quebec. It includes DJMA (annual average daily flow), DJME (summer average daily flow), DJME (summer average daily flow (June, July, August, September) and DJMH (average daily winter flow (December, January, February, March) as well as other traffic data. It is important to note that these values are calculated for total traffic directions. Interactive map: Some files are accessible by querying an à la carte traffic section with a click (the file links are displayed in the descriptive table that is displayed upon click): • Historical aggregate data (PDF) • Annual reports for permanent sites (PDF and Excel) • Hourly data (hourly average per weekday per month) (Excel) This third party metadata element was translated using an automated translation tool (Amazon Translate).

This dataset contains estimates of the average number of vehicles that used roads throughout the City of Detroit. Each record indicates the Annual Average Daily Traffic (AADT) and Commercial Annual Average Daily Traffic (CAADT) for a road segment, where the road segment is located, and other characteristics. This data is derived from Michigan Department of Transportation's (MDOT) Open Data Portal. SEMCOG was the source for speed limits and number of lanes.The primary measure, Annual Average Daily Traffic (AADT), is the estimated mean daily traffic volume for all types of vehicles. Commercial Annual Average Daily Traffic (CAADT) is the estimated mean daily traffic volume for commercial vehicles, a subset of vehicles included in the AADT. The Route ID is an identifier for each road in Detroit (e.g., Woodward Ave). Routes are divided into segments by features such as cross streets, and Location ID's are used to uniquely identify those segments. Along with traffic volume, each record also states the number of lanes, the posted speed limit, and the type of road (e.g., Trunkline or Ramp) based on the Federal Highway Administration (FHWA) functional classification system.According to MDOT's Traffic Monitoring Program a commercial vehicle would be anything Class 4 and up in the FHWA vehicle classification system. This includes vehicles such as buses, semi-trucks, and personal recreational vehicles (i.e., RVs or campers). Methods used to determine traffic volume vary by site, and may rely on continuous monitoring or estimates based on short-term studies. Approaches to vehicle classification similarly vary, depending on the equipment used at a site, and may consider factors such as vehicle weight and length between axles.For more information, please visit MDOT Traffic Monitoring Program.

Dataset Traffic

## Overview

Dataset Traffic is a dataset for object detection tasks - it contains Traffic annotations for 681 images.

## Getting Started

You can download this dataset for use within your own projects, or fork it into a workspace on Roboflow to create your own model.

  ## License

  This dataset is available under the [CC BY 4.0 license](https://creativecommons.org/licenses/CC BY 4.0).

Congestion Roads Saturation Traffic Transportation Volumes dgitransport flow transport