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.

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

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

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.

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 Tampa CV Pilot generates data from the interaction between vehicles and between vehicles and infrastructure. This dataset consists of Basic Safety Messages (BSMs) generated by participant and public transportation vehicles onboard units (OBU) and transmitted to road-side units (RSU) located throughout the Tampa CV Pilot Study area. The full set of raw, BSM data from Tampa CV Pilot can be found in the ITS Sandbox. The data fields follow SAE J2735 and J2945/1 standards and adopted units of measure. This dataset holds a flattened sample of the BSM data from Tampa CV Pilot. An extra geo column (coreData_position) was added to this dataset to allow for mapping of the geocoded BSM data within Socrata, and a column of random numbers (randomNum) was added to allow for random sampling of data points within Socrata.

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.

This data set was acquired by the USDOT Data Capture and Management program. The purpose of the data set is to provide multi-modal data and contextual information (weather and incidents) that can be used to research and develop applications. Contains one full year (January – December 2010) of raw 30-second data for over 3,000 traffic detectors deployed along 1,250 lane miles of monitored roadway in San Diego. Cleaned and geographically referenced data for over 1,500 incidents and lane closures for the two sections of I-5 that experienced the greatest number of incidents during 2010. Complete trip (origin-to-destination) GPS “breadcrumbs” collected by ALK Techonologies, containing latitude/longitude, vehicle heading and speed data, and time for individual in-vehicles devices updated at 3-second intervals for over 10,000 trips taken during 2010. A digital map shape file containing ALK’s street-level network data for the San Diego Metropolitan area. And San Diego Weather data for 2010. 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 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 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.