Facebook
TwitterApache License, v2.0https://www.apache.org/licenses/LICENSE-2.0
License information was derived automatically
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.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
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.
Facebook
Twitterhttps://creativecommons.org/publicdomain/zero/1.0/https://creativecommons.org/publicdomain/zero/1.0/
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.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
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.
Facebook
TwitterOpen Government Licence - Canada 2.0https://open.canada.ca/en/open-government-licence-canada
License information was derived automatically
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 a section of traffic à la carte with a click (the file links are displayed in the descriptive table that is displayed when clicking): • Historical aggregated data (PDF) • Annual reports for permanent sites (PDF and Excel) • Hourly data (hourly average per weekday per month) (Excel) • 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).**
Facebook
TwitterThe 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.
Facebook
TwitterThis 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.
Facebook
TwitterDaily utilization metrics for data.lacity.org and geohub.lacity.org. Updated monthly
Facebook
TwitterIntroduction: Traffic congestion remains a significant challenge in urban environments, and optimizing traffic signals plays a crucial role in easing traffic flow. This dataset is designed to aid researchers and developers working on intelligent traffic management systems. It provides comprehensive data collected from three different sources, each offering unique insights into vehicle detection and traffic patterns. Dataset's collection strategy: Kaggle Data Collection 1.Source: Curated datasets from Kaggle, including well-known vehicle detection collections. 2.Content: Contains images and labels of vehicles such as cars, buses, and bikes. 3.Purpose: Provides standardized data for baseline testing and model comparisons. 4.Format: Images in JPEG format with associated YOLO compatible label files (.txt). Link: https://www.kaggle.com/datasets/tubasiddiqui/toy-cars-annotated-on-yolo-format
Custom Data Collection 1.Source: Synthetic and toy vehicle images created in controlled conditions. 2.Content: Features miniature models of cars, buses, and motorcycles. 3.Purpose: Ensures a controlled environment for initial model training and testing, simulating various lighting and angle conditions. 4.Format: JPEG images with YOLO annotation files. Real-Environment Data (Skardu City) 1.Source: Collected from various locations in Skardu city. 2.Content: Real-world images capturing vehicles in diverse scenarios, including intersections, narrow streets, and busy roads. 3.Purpose: Provides data reflecting real traffic conditions, environmental variations, and vehicle diversity, crucial for training robust models. 4.Format: High-resolution JPEG images with detailed annotation files.
Potential Applications Traffic Signal Optimization: Train machine learning models to adjust traffic signals dynamically based on real-time vehicle detection. Autonomous Vehicle Navigation: Use real-world data to enhance the perception systems of self-driving cars. Traffic Flow Analysis: Analyze congestion patterns and develop predictive models for traffic management. Smart City Initiatives: Develop solutions to improve urban mobility and reduce traffic-related issues. How to Use the Dataset 1.Download: interested user can download the dataset from this platform. 2.Training: Use the YOLO compatible images and labels to train object detection models. 3.Testing and Validation: Validate your models on real-world data to assess performance under varying conditions. Acknowledgments We thank the team involved in data collection across Skardu city and the community contributions from Kaggle. This dataset aims to facilitate advancements in smart traffic systems and support innovative solutions for traffic management. Contribute Feedback and contributions are welcome! Let's collaborate to improve and expand this dataset for future research and practical applications.
Facebook
TwitterFeature 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.
Facebook
Twitterhttps://data.gov.sg/open-data-licencehttps://data.gov.sg/open-data-licence
Dataset from Land Transport Authority. For more information, visit https://data.gov.sg/datasets/d_3136f317a1f282a33fe7a2f6a907c047/view
Facebook
Twitterhttps://creativecommons.org/publicdomain/zero/1.0/https://creativecommons.org/publicdomain/zero/1.0/
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.
Facebook
Twitterhttps://opendata.victoria.ca/pages/open-data-licencehttps://opendata.victoria.ca/pages/open-data-licence
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.
Facebook
TwitterCC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
## Overview
Yolov8 Traffic is a dataset for object detection tasks - it contains Car Truck Bus Motobike Bike annotations for 1,502 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 [Public Domain license](https://creativecommons.org/licenses/Public Domain).
Facebook
TwitterAttribution-NonCommercial-ShareAlike 4.0 (CC BY-NC-SA 4.0)https://creativecommons.org/licenses/by-nc-sa/4.0/
License information was derived automatically
elcome to the cutting-edge world of traffic prediction! This Kaggle dataset is a goldmine for data enthusiasts, machine learning aficionados, and urban planning visionaries. In this treasure trove of information, you'll find a comprehensive collection of real-world traffic data meticulously curated for your analytical prowess.
Unravel the complexities of urban mobility as you delve into diverse parameters such as historical traffic patterns, weather conditions, special events, and more. Whether you're a seasoned data scientist or a curious novice, this dataset offers a unique opportunity to fine-tune your predictive models and contribute to the future of transportation efficiency.
Harness the power of data to foresee traffic bottlenecks, optimize city planning, and revolutionize the way we navigate our urban landscapes. Join the community of innovators working towards a seamlessly connected and intelligently managed transportation ecosystem. The road to the future starts here—take the wheel and drive progress with the Traffic Prediction Dataset on Kaggle!
Facebook
TwitterAttribution-NonCommercial-NoDerivs 4.0 (CC BY-NC-ND 4.0)https://creativecommons.org/licenses/by-nc-nd/4.0/
License information was derived automatically
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.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Congestion Roads Saturation Traffic Transportation Volumes dgitransport flow transport
Facebook
TwitterNew York City Department of Transportation (NYC DOT) uses Automated Traffic Recorders (ATR) to collect traffic sample volume counts at bridge crossings and roadways.These counts do not cover the entire year, and the number of days counted per location may vary from year to year.
Facebook
TwitterTraffic volumes; measured and calculated amounts of vehicle traffic that travel the sections of road.
Facebook
TwitterApache License, v2.0https://www.apache.org/licenses/LICENSE-2.0
License information was derived automatically
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.