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.

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.

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.

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.

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.

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.

Data is from the small-scale demonstration of the Intelligent Network Flow Optimization (INFLO) Prototype System and applications in Seattle, Washington. Connected vehicle systems were deployed in 21 vehicles in a scripted driving scenario circuiting this I-5 corridor northbound and southbound during morning rush hour. Basic Safety Messages (BSM) sent by connected vehicles (CVs) through either the cellular network or Dedicated Short Range Communication (DSRC) when the vehicle is in the range of Roadside Units (RSU). These messages were received by the traffic management center (TMC).

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

Florida DOT (FDOT) installed Vehicle Awareness Devices (VADs) on a set of Lynx transit buses as part of a demonstration for the ITS World Congress held in Orlando in October 2011. These VADs recorded vehicle data during the World Congress and continue to operate after the World Congress. Periodically the VADs are removed from the vehicles and the data files are retrieved. FHWA Has confirmed that the data do not contain identification of individual transit operators or any other forms for Personally Identifiable Information (PII). 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.