This dataset contains V2X data collected from the Utah Connected Vehicle Data Ecosystem Program. We have submitted 7 days of Signal Phase and Timing Messages (SPaT) in J2735 standards from 3 intersections in Orem, UT. This includes: (1) vehicles equipped with OBUs (Onboard Units) for real-time V2X (Vehicle-to-Everything) data transmission and reception, (2) road-side units (RSUs) capable of capturing, transmitting, and processing data from the transportation environment, and (3) a secure, scalable cloud platform for aggregating, analyzing, and visualizing transportation data.

The Trajectory Conversion Algorithm Version 2.3 (TCA) is designed to test different strategies for producing, transmitting, and storing Connected Vehicle information. The TCA uses vehicle trajectory data, roadside equipment (RSE) location information, cellular region information and strategy information to emulate the messages connected vehicles would produce. This data set contains common data sets generated by the TCA using the BSM and PDM at 100% market penetration for two simulated traffic networks, an arterial network (Van Ness Avenue in San Francisco, CA) and a freeway network (the interchange of I-270 and I-44 in St. Louis, MO). This legacy dataset was created before data.transportation.gov and is only currently available via the attached file(s). Please contact the dataset owner if there is a need for users to work with this data using the data.transportation.gov analysis features (online viewing, API, graphing, etc.) and the USDOT will consider modifying the dataset to fully integrate in data.transportation.gov.

Contains all Basic Safety Messages (BSMs) collected during the Advanced Messaging Concept Development (AMCD) field testing program. For this project, all of the Part I BSM message fields were populated. Additional data fields were also added to the row to identify sender, time of communication, mode of communication, etc., allowing the consumer of this data set to accurately track messages through the system. All BSMs are generated by OBUs and ultimately received by the VCC Cloud server.

The data attached and/or displayed were collected during the Multi-Modal Intelligent Transportation Signal Systems (MMITSS) study. MMITSS is a next-generation traffic signal system that seeks to provide a comprehensive traffic information framework to service all modes of transportation. A BSM is one of the messages belonging to the Society of Automotive Engineers (SAE) J2735 Standard. This standard is geared toward supporting the interoperability of DSRC applications through the use of a standardized message set and its data frames and data elements. A BSM, which is at times referred to as a “heartbeat” message, is a frequently transmitted message (usually at approximately 10Hz) that is meant to increase a vehicle’s situational awareness. These messages are intended to be used for a variety of applications to exchange safety data regarding a vehicle’s state. A typical BSM contains up to two parts. Part I, the binary large object (blob), is included in every BSM. It contains the fundamental data elements that describe a vehicle’s position (latitude, longitude, elevation) and motion (heading, speed, acceleration). Part II of a BSM contains optional data that is transmitted when required or in response to an event. Typically Part II contains data that serves as an extension of vehicle safety information (path history, path prediction, event flags) and data pertaining to the status of a vehicle’s components, such as lights, wipers, and brakes. NOTE: All extra attachments are located in Multi-Modal Intelligent Traffic Signal Systems Basic Safety Messages such as MAP, Detectors, and Simulation results

This data were collected during the Safety Pilot Model Deployment (SPMD). The data sets that these entities will provide include basic safety messages (BSM), vehicle trajectories, and various driver-vehicle interaction data, as well as contextual data that describes the circumstances under which the Model Deployment data was collected. Large portion of the data contained in this environment is obtained from on board vehicle devices and roadside units. This legacy dataset was created before data.transportation.gov and is only currently available via the attached file(s). Please contact the dataset owner if there is a need for users to work with this data using the data.transportation.gov analysis features (online viewing, API, graphing, etc.) and the USDOT will consider modifying the dataset to fully integrate in data.transportation.gov.

Contains all PDCMs generated during the AMCD field testing program. The PDCM is a control message sent from the server to OBUs to customize a request for Probe Vehicle Data (PVD) from the receiving OBU. All PDCMs are generated by the VCC Cloud server and transmitted to OBU clients through either a DSRC or cellular communications channel.

울산광역시 승용차요일제 RFID 시스템 메세지관리에 대한 데이터입니다. 인자값설명, 안내구분코드, 메세지유형코드의 내용을 포함합니다.

ITS JPO's Connected Vehicle Pilot Deployment Program integrates connected vehicle research concepts into practical and effective elements to enhance existing operational capabilities. Data were collected throughout each pilot to facilitate independent evaluations of the use of connected vehicle technology on real roadways. To encourage additional study and reuse of these data, ITS DataHub has partnered with each pilot site to make sanitized and anonymized tabular and non-tabular data from these projects available to the public. This article gives you a brief overview of what each pilot focused on and what types of CV Pilot data and tools are available on ITS DataHub.

The data elements contained in this data environment were collected during the Prototype Operational Data Environment (P-ODE) formal data collection period. The Prototype Operational Data Environment (P-ODE) is a system that receives data from multiple sources in real-time, is capable of performing validation, integration, and sanitization checks, transforms the data into a consistent format, and makes the data available to applications as well as stores the data in ITS JPO data system. This data environment contains speed, volume, occupancy, travel time, and incident data collected along I-66 in Northern Virginia between May 2016 and August 2016. The ASN.1 data set contains data records in their original binary form, while Detector and Incident data sets each contain records that have been converted to text format. This legacy dataset was created before data.transportation.gov and is only currently available via the attached file(s). Please contact the dataset owner if there is a need for users to work with this data using the data.transportation.gov analysis features (online viewing, API, graphing, etc.) and the USDOT will consider modifying the dataset to fully integrate in data.transportation.gov.

Contains all PVDs generated during the AMCD field testing program. The probe vehicle message is used to exchange status about a vehicle with other DSRC readers to allow the collection of information about a typical vehicle’s traveling behaviors along a segment of road. The exchanges of this message as well as the event which caused the collection of various elements defined in the messages are in Annex B of the SAE J2735 standard.