Traffic congestion and related problems are a common concern in urban areas. Understanding traffic patterns and analyzing data can provide valuable insights for transportation planning, infrastructure development, and congestion management.

What exactly is this dataset and how was it created? it is a valuable resource for studying traffic conditions as it contains information collected by a computer vision model. The model detects four classes of vehicles: cars, bikes, buses, and trucks. The dataset is stored in a CSV file and includes additional columns such as time in hours, date, days of the week, and counts for each vehicle type (CarCount, BikeCount, BusCount, TruckCount). The "Total" column represents the total count of all vehicle types detected within a 15-minute duration.

The dataset is updated every 15 minutes, providing a comprehensive view of traffic patterns over the course of one month. Additionally, the dataset includes a column indicating the traffic situation categorized into four classes: 1-Heavy, 2-High, 3-Normal, and 4-Low. This information can help assess the severity of congestion and monitor traffic conditions at different times and days of the week.

In what cases can it be useful? The dataset is useful in transportation planning, congestion management, and traffic flow analysis. It helps understand vehicle demand, identify congested areas, and inform infrastructure improvements. The dataset enables targeted interventions like signal optimizations and lane adjustments. It allows researchers to study traffic patterns by hour, day, or specific dates and explore correlations with external factors. It supports transportation research on vehicle relationships and traffic behavior. Urban planners can assess traffic impact for zoning and infrastructure decisions. Overall, the dataset empowers stakeholders to make data-driven decisions, enhance urban mobility, and create efficient and sustainable cities.

Is there a new update? Yes, in the next update, the dataset will be expanded to include the speed of the cars. Additionally, the data will not be limited to a single route; instead, it will encompass a traffic intersection. This expansion aims to provide a more comprehensive understanding of traffic dynamics and enable better analysis and decision-making for traffic management. The inclusion of speed data will offer insights into the flow and efficiency of vehicles, further enhancing the dataset's value for transportation planning and congestion management efforts.

Thanks

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.

You can also access an API version of this dataset.

TMS

(traffic monitoring system) daily-updated traffic counts API

Important note: due to the size of this dataset, you won't be able to open it fully in Excel. Use notepad / R / any software package which can open more than a million rows.

Data reuse caveats: as per license.

Data quality

statement: please read the accompanying user manual, explaining:

how

 this data is collected identification 

 of count stations traffic 

 monitoring technology monitoring 

 hierarchy and conventions typical 

 survey specification data 

 calculation TMS 

 operation. 

Traffic

monitoring for state highways: user manual

[PDF 465 KB]

The data is at daily granularity. However, the actual update

frequency of the data depends on the contract the site falls within. For telemetry

sites it's once a week on a Wednesday. Some regional sites are fortnightly, and

some monthly or quarterly. Some are only 4 weeks a year, with timing depending

on contractors’ programme of work.

Data quality caveats: you must use this data in

conjunction with the user manual and the following caveats.

The

 road sensors used in data collection are subject to both technical errors and 

 environmental interference.Data 

 is compiled from a variety of sources. Accuracy may vary and the data 

 should only be used as a guide.As 

 not all road sections are monitored, a direct calculation of Vehicle 

 Kilometres Travelled (VKT) for a region is not possible.Data 

 is sourced from Waka Kotahi New Zealand Transport Agency TMS data.For 

 sites that use dual loops classification is by length. Vehicles with a length of less than 5.5m are 

 classed as light vehicles. Vehicles over 11m long are classed as heavy 

 vehicles. Vehicles between 5.5 and 11m are split 50:50 into light and 

 heavy.In September 2022, the National Telemetry contract was handed to a new contractor. During the handover process, due to some missing documents and aged technology, 40 of the 96 national telemetry traffic count sites went offline. Current contractor has continued to upload data from all active sites and have gradually worked to bring most offline sites back online. Please note and account for possible gaps in data from National Telemetry Sites. 

The NZTA Vehicle

Classification Relationships diagram below shows the length classification (typically dual loops) and axle classification (typically pneumatic tube counts),

and how these map to the Monetised benefits and costs manual, table A37,

page 254.

Monetised benefits and costs manual [PDF 9 MB]

For the full TMS

classification schema see Appendix A of the traffic counting manual vehicle

classification scheme (NZTA 2011), below.

Traffic monitoring for state highways: user manual [PDF 465 KB]

State highway traffic monitoring (map)

State highway traffic monitoring sites

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.

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.

Dataset Overview

This dataset provides detailed information on website traffic, including page views, session duration, bounce rate, traffic source, time spent on page, previous visits, and conversion rate.

Dataset Description

• Page Views: The number of pages viewed during a session.
• Session Duration: The total duration of the session in minutes.
• Bounce Rate: The percentage of visitors who navigate away from the site after viewing only one page.
• Traffic Source: The origin of the traffic (e.g., Organic, Social, Paid).
• Time on Page: The amount of time spent on the specific page.
• Previous Visits: The number of previous visits by the same visitor.
• Conversion Rate: The percentage of visitors who completed a desired action (e.g., making a purchase).

Data Summary

• Total Records: 2000
• Total Features: 7

Key Features

1. Page Views: This feature indicates the engagement level of the visitors by showing how many pages they visit during their session.
2. Session Duration: This feature measures the length of time a visitor stays on the website, which can indicate the quality of the content.
3. Bounce Rate: A critical metric for understanding user behavior. A high bounce rate may indicate that visitors are not finding what they are looking for.
4. Traffic Source: Understanding where your traffic comes from can help in optimizing marketing strategies.
5. Time on Page: This helps in analyzing which pages are retaining visitors' attention the most.
6. Previous Visits: This can be used to analyze the loyalty of visitors and the effectiveness of retention strategies.
7. Conversion Rate: The ultimate metric for measuring the effectiveness of the website in achieving its goals.

Usage

This dataset can be used for various analyses such as:

• Identifying key drivers of engagement and conversion.
• Analyzing the effectiveness of different traffic sources.
• Understanding user behavior patterns and optimizing the website accordingly.
• Improving marketing strategies based on traffic source performance.
• Enhancing user experience by analyzing time spent on different pages.

Acknowledgments

This dataset was generated for educational purposes and is not from a real website. It serves as a tool for learning data analysis and machine learning techniques.

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.

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.

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.

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.

Mini Traffic Detection dataset comprises 8 classes with 30 instances each, divided into 70% for training and 30% for validation. Primarily designed for computer vision tasks, it focuses on traffic object detection. It's an excellent choice for transfer learning with Detectron2 for custom object detection and segmentation projects. The dataset includes classes such as bicycle, bus, car, motorcycle, person, traffic_light, truck, and stop_sign.

Location of traffic counters in York. *Please note that the data published within this dataset is a live API link to CYC's GIS server. Any changes made to the master copy of the data will be immediately reflected in the resources of this dataset.The date shown in the "Last Updated" field of each GIS resource reflects when the data was first published.

Here are a few use cases for this project:

1. Smart Traffic Management: The "traffic" computer vision model can be used in intelligent traffic management to detect and categorize various traffic participants. It would help in real-time traffic control by adjusting traffic light patterns based on the density and types of vehicles on the road.

2. Autonomous Vehicles Navigation: Self-driving cars or drones could benefit from this model by identifying and classifying different elements in their path such as other cars, people, buses, 2-wheelers, etc. This would enhance their ability for safe and efficient navigation.

3. Pedestrian Safety: This model can be utilized in pedestrians' mobile applications to alert them about incoming vehicles such as trucks, vans, autos, buses, or 2-wheelers while they are crossing the road or walking on the pavement.

4. Security Surveillance Systems: In commercial or residential zones, the model could assist in accurately identifying and logging vehicle types or detecting anomalies like a person in a vehicle-restricted area, potentially enhancing security measures.

5. Retail & Marketing Research: Stores selling vehicle-related products or services might use this model to monitor the types of vehicles in their parking lots as a form of market research. This data could help them tailor their products, services, or marketing strategies accordingly.

Tomtom Traffic Api
This dataset falls under the category Individual Transport Traffic Control Systems.
It contains the following data: Traffic flow and Traffic incident on road
This dataset was scouted on 2022-02-05 as part of a data sourcing project conducted by TUMI. License information might be outdated: Check original source for current licensing. The data can be accessed using the following URL / API Endpoint: https://developer.tomtom.com/traffic-api/documentation/product-information/introduction

This is a traffic dataset which contains balance size of encrypted malicious and legitimate traffic for encrypted malicious traffic detection. The dataset is a secondary csv feature data which is composed of five public traffic datasets. Our dataset is composed based on three criteria: The first criterion is to combine widely considered public datasets which contain both encrypted malicious and legitimate traffic in existing works, such as the Malwares Capture Facility Project dataset and the CICIDS-2017 dataset. The second criterion is to ensure the data balance, i.e., balance of malicious and legitimate network traffic and similar size of network traffic contributed by each individual dataset. Thus, approximate proportions of malicious and legitimate traffic from each selected public dataset are extracted by using random sampling. We also ensured that there will be no traffic size from one selected public dataset that is much larger than other selected public datasets. The third criterion is that our dataset includes both conventional devices' and IoT devices' encrypted malicious and legitimate traffic, as these devices are increasingly being deployed and are working in the same environments such as offices, homes, and other smart city settings.

Based on the criteria, 5 public datasets are selected. After data pre-processing, details of each selected public dataset and the final composed dataset are shown in “Dataset Statistic Analysis Document”. The document summarized the malicious and legitimate traffic size we selected from each selected public dataset, proportions of selected traffic size from each selected public dataset with respect to the total traffic size of the composed dataset (% w.r.t the composed dataset), proportions of selected encrypted traffic size from each selected public dataset (% of selected public dataset), and total traffic size of the composed dataset. From the table, we are able to observe that each public dataset equally contributes to approximately 20% of the composed dataset, except for CICDS-2012 (due to its limited number of encrypted malicious traffic). This achieves a balance across individual datasets and reduces bias towards traffic belonging to any dataset during learning. We can also observe that the size of malicious and legitimate traffic are almost the same, thus achieving class balance. The datasets now made available were prepared aiming at encrypted malicious traffic detection. Since the dataset is used for machine learning model training, a sample of train and test sets are also provided. The train and test datasets are separated based on 1:4 and stratification is applied during data split. Such datasets can be used directly for machine or deep learning model training based on selected features.

This table provides the traffic studies in hourly bins and some statistics. The SDOT Traffic Counts group runs studies across the city to collect traffic volumes. Most studies are done with pneumatic tubes, but some come from video systems as well. Use the field study_id to match it with other tables for more information.

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 dataset includes both raw and metadata from the Test Bed Lower Saxony in Braunschweig, Germany.

The raw data comprises trajectory data of traffic participants, along with current local weather data, and road condition data. The trajectory data is indexed by object ID and timestamps, including detailed information about the position, speed, acceleration, dimensions, and classification of each object. The weather data provide information on wind, sunlight, precipitation, visibility, and more. The road surface data provide information on surface temperature, water layer thickness, and more.

The metadata contains data extracted from the raw trajectory data, specifically traffic volume data, and 4 OpenSCENARIO files that represent the trajectory data using FollowTrajectoryActions.

For any questions regarding the dataset, please contact mailto:opendata-ts@dlr.de" href="mailto:opendata-ts@dlr.de" target="_blank" rel="noopener">opendata-ts@dlr.de. For citation, please refer to the publication available on TechRxiv.

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. 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.