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.

Contains all Basic Mobility Messages (BMMs) collected during the Advanced Messaging Concept Development (AMCD) field testing program. While there is no specific standard in existence that addresses the content of a BMM, the descriptive definitions of the variables were derived from the J2735 standard where applicable. All BMMs are generated by OBUs and ultimately received by the VCC Cloud server.

Contains all Basic Mobility Control Message (BMCMs) generated during the Advanced Messaging Concept Development (AMCD) field testing program. While there is no specific standard in existence that addresses the content of a BMCM, the following format was derived to control the configuration and content of BMMs requested from the vehicle. All BMCMs are generated by the VCC Cloud server and transmitted to OBU clients through either a DSRC or cellular communications channel.

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 files in this data environment were produced using the Vehicle Awareness Device (VAD) installed on one test vehicle over a two month period. The VAD installed in the test car is identical to the VADs installed in over 2800 vehicles participating in the Safety Pilot Model Demonstration conducted from August 2012 through August 2013 by the National Highway Traffic Safety Administration (NHTSA) in Ann Arbor, Michigan. 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.

This dataset contains raw Signal Phasing and Timing (SPaT), MAP, and Basic Safety Messages (BSM) data from the "Feasibility Study and Assessment of Communications Approaches for Real-Time Traffic Signal Applications" project in the hexadecimal string and pcap formats. The project characterizes and assesses the feasibility of SPaT messages for infrastructure-based safety applications by comparing messages received through cellular networks with those received through Dedicated Short Range Communication (DSRC). This dataset contains the raw research data collected for the project. The project's final report and supporting dataset can be found at the National Transportation Library and is linked in the references section of this dataset.

This dataset contains V2X data collected from the Utah Connected Vehicle Data Ecosystem Program. We have submitted sample MAP messages in J2735 standards from 3 intersections in Orem, UT.

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.

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.

This dataset contains V2X data collected from the Utah Connected Vehicle Data Ecosystem Program. We have submitted 7 days of deduplicated Basic Safety Messages (BSMs) 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.