During the 2014 ITS World Congress a demonstration of the connected vehicle infrastructure in the City of Detroit was conducted. The test site included approximately 14 intersections around Detroit’s COBO convention center and involved 9 equipped vehicles.Intersection Situation Data (ISD) data set communicates MAP and signal phase and timing (SPaT) information. MAP information communicates an intersection’s location (latitude and longitude), elevation, and geometric features such as approaches and lane configuration. SPaT data communicates the (current) state of the intersection’s signal indication(s). The data is composed of discrete Row Groups. A Row Group is a collection of (approximately 3-4) consecutive rows with common attribute. NOTE: All Extra Files are attached in 2014 ITS World Congress Connected Vehicle Test Bed Demonstration Vehicle Situation Data

During the 2014 ITS World Congress a demonstration of the connected vehicle infrastructure in the City of Detroit was conducted. The test site included approximately 14 intersections around Detroit’s COBO convention center and involved 9 equipped vehicles.Intersection Situation Data (ISD) data set communicates MAP and signal phase and timing (SPaT) information. MAP information communicates an intersection’s location (latitude and longitude), elevation, and geometric features such as approaches and lane configuration. SPaT data communicates the (current) state of the intersection’s signal indication(s). The data is composed of discrete Row Groups. A Row Group is a collection of (approximately 3-4) consecutive rows with common attribute. NOTE: All Extra Files are attached in 2014 ITS World Congress Connected Vehicle Test Bed Demonstration Vehicle Situation Data

During the 2014 ITS World Congress a demonstration of the connected vehicle infrastructure in the City of Detroit was conducted. The test site included approximately 14 intersections around Detroit’s COBO convention center and involved 9 equipped vehicles.Intersection Situation Data (ISD) data set communicates MAP and signal phase and timing (SPaT) information. MAP information communicates an intersection’s location (latitude and longitude), elevation, and geometric features such as approaches and lane configuration. SPaT data communicates the (current) state of the intersection’s signal indication(s). The data is composed of discrete Row Groups. A Row Group is a collection of (approximately 3-4) consecutive rows with common attribute. NOTE: All Extra Files are attached in 2014 ITS World Congress Connected Vehicle Test Bed Demonstration Vehicle Situation Data

During the 2014 ITS World Congress a demonstration of the connected vehicle infrastructure in the City of Detroit was conducted. The test site included approximately 14 intersections around Detroit’s COBO convention center and involved 9 equipped vehicles. Traveler Situation Data (TSD) was obtained from the data warehouse, and not the data clearinghouse. Only 19 messages were obtained from our query as the current mode of operation of the Test Bed is that the warehouse only contains a few static messages, which are meant to serve as a proxy for future operation in which query submissions will only return message(s) relevant to the context in which the query was submitted. The messages that returned per a query submission communicates a pertinent advisor message which is in part contextualized by location and content. NOTE: All Extra Files are attached in 2014 ITS World Congress Connected Vehicle Test Bed Demonstration Vehicle Situation Data

During the 2014 ITS World Congress a demonstration of the connected vehicle infrastructure in the City of Detroit was conducted. The test site included approximately 14 intersections around Detroit’s COBO convention center and involved 9 equipped vehicles. Traveler Situation Data (TSD) was obtained from the data warehouse, and not the data clearinghouse. Only 19 messages were obtained from our query as the current mode of operation of the Test Bed is that the warehouse only contains a few static messages, which are meant to serve as a proxy for future operation in which query submissions will only return message(s) relevant to the context in which the query was submitted. The messages that returned per a query submission communicates a pertinent advisor message which is in part contextualized by location and content. NOTE: All Extra Files are attached in 2014 ITS World Congress Connected Vehicle Test Bed Demonstration Vehicle Situation Data

During the 2014 ITS World Congress a demonstration of the connected vehicle infrastructure in the City of Detroit was conducted. The test site included approximately 14 intersections around Detroit’s COBO convention center and involved 9 equipped vehicles. The Vehicle Situation Data (VSD) data set includes a series of data files that recorded vehicle situational data that were generated by an equipped vehicle. During the ITS World Congress, VSDs were encoded with one of two schemas. The dataset contains decoded data using both 2.0 and 2.1 ASN.1 schemas.

During the 2014 ITS World Congress a demonstration of the connected vehicle infrastructure in the City of Detroit was conducted. The test site included approximately 14 intersections around Detroit’s COBO convention center and involved 9 equipped vehicles. The Vehicle Situation Data (VSD) data set includes a series of data files that recorded vehicle situational data that were generated by an equipped vehicle. During the ITS World Congress, VSDs were encoded with one of two schemas. The dataset contains decoded data using both 2.0 and 2.1 ASN.1 schemas.

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

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

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. This data set contains real-time volume, speed and loop occupancy data that were collected from WSDOT’s simulated roadway sensors every 20 seconds and aggregated according to user defined procedures and threshold by the Infrastructure Traffic Sensor System (TSS) Data Aggregator software.

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. This data set contains real-time volume, speed and loop occupancy data that were collected from WSDOT’s simulated roadway sensors every 20 seconds and aggregated according to user defined procedures and threshold by the Infrastructure Traffic Sensor System (TSS) Data Aggregator software.

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. This data set contains queue warning messages that were recommended by the INFLO Q-WARN algorithm and sent by the traffic management center to vehicles to warn drivers upstream of the queue. The objective of queue warning is to provide a vehicle operator sufficient warning of impending queue backup in order to brake safely, change lanes, or modify route such that secondary collisions can be minimized or even eliminated.

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. This data set contains queue warning messages that were recommended by the INFLO Q-WARN algorithm and sent by the traffic management center to vehicles to warn drivers upstream of the queue. The objective of queue warning is to provide a vehicle operator sufficient warning of impending queue backup in order to brake safely, change lanes, or modify route such that secondary collisions can be minimized or even eliminated.

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. This data set contains speed harmonization messages that were recommended by the INFLO SPD-HARM algorithm and sent by the traffic management center to the connected vehicles, which provided drivers with the suggested speed while driving on the segment of I-5 that was included in the test. The objective of speed harmonization is to dynamically adjust and coordinate maximum appropriate vehicle speeds in response to downstream congestion, incidents, and weather or road conditions in order to maximize traffic throughput and reduce crashes.

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. This data set contains speed harmonization messages that were recommended by the INFLO SPD-HARM algorithm and sent by the traffic management center to the connected vehicles, which provided drivers with the suggested speed while driving on the segment of I-5 that was included in the test. The objective of speed harmonization is to dynamically adjust and coordinate maximum appropriate vehicle speeds in response to downstream congestion, incidents, and weather or road conditions in order to maximize traffic throughput and reduce crashes.

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

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 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. The GPS data set catalogs the vehicle operation data of the test vehicles that used for the MMITSS field testing. The data contains the performance and operation details of vehicles. This file contains a number of fields detailing elements such as vehicle position and speed, fidelity measures of GPS-based data elements, and vehicle operation data. NOTE: All extra attachments are located in Multi-Modal Intelligent Traffic Signal Systems Basic Safety Message

Data 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. The GPS data set catalogs the vehicle operation data of the test vehicles that used for the MMITSS field testing. The data contains the performance and operation details of vehicles. This file contains a number of fields detailing elements such as vehicle position and speed, fidelity measures of GPS-based data elements, and vehicle operation data. NOTE: All extra attachments are located in Multi-Modal Intelligent Traffic Signal Systems Basic Safety Message

Data 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.The Signal Plans for Roadside Equipment (RSE) data contains the basics of a Signal Phase and Timing (SPAT) message. This data includes SPAT message and the timestamp of the SPAT message. The data also provides the signal phase and timing information for one or more movements at an intersection.

Data 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.The Signal Plans for Roadside Equipment (RSE) data contains the basics of a Signal Phase and Timing (SPAT) message. This data includes SPAT message and the timestamp of the SPAT message. The data also provides the signal phase and timing information for one or more movements at an intersection.

Data 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. The Vehicle Trajectories file is populated with basic safety messages received from equipped vehicle within the communication range of an Roadside Equipment (RSEs). The data also contains elements that communicate additional details about the vehicle that is used for vehicle safety applications, and elements that communicate specific items of a vehicle‘s status that are used in data event snapshots which are gathered and periodically reported to an RSEs. These data are transmitted at a rate of 10 Hz. NOTE: All extra attachments are located in Multi-Modal Intelligent Traffic Signal Systems Basic Safety Message

Data 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. The Vehicle Trajectories file is populated with basic safety messages received from equipped vehicle within the communication range of an Roadside Equipment (RSEs). The data also contains elements that communicate additional details about the vehicle that is used for vehicle safety applications, and elements that communicate specific items of a vehicle‘s status that are used in data event snapshots which are gathered and periodically reported to an RSEs. These data are transmitted at a rate of 10 Hz. NOTE: All extra attachments are located in Multi-Modal Intelligent Traffic Signal Systems Basic Safety Message

This is the EVENT data captured from the New York City CV Pilot project that was processed by the independent evaluators at Volpe. Additional data collected and data dictionary are in the attachments. Each EVENT record documents the details of one application warning that occurred on an Aftermarket Safety Device (ASD) in an equipped host vehicle and includes CV messages from a defined recording time both before and after the warning was generated by the host ASD. Messages in the recording time window include the Basic Safety Messages (BSM) of the host vehicle that received the warning, as well as other BSMs received from the warning target equipped vehicle (for V2V applications) or other nearby equipped vehicles. Depending on the application warning type, MAP messages, Signal Phase and Timing (SPaT) messages, and Traveler Information Messages (TIM) that were heard by the host vehicle may also be included in the event record.

This is the EVENT data captured from the New York City CV Pilot project that was processed by the independent evaluators at Volpe. Additional data collected and data dictionary are in the attachments. Each EVENT record documents the details of one application warning that occurred on an Aftermarket Safety Device (ASD) in an equipped host vehicle and includes CV messages from a defined recording time both before and after the warning was generated by the host ASD. Messages in the recording time window include the Basic Safety Messages (BSM) of the host vehicle that received the warning, as well as other BSMs received from the warning target equipped vehicle (for V2V applications) or other nearby equipped vehicles. Depending on the application warning type, MAP messages, Signal Phase and Timing (SPaT) messages, and Traveler Information Messages (TIM) that were heard by the host vehicle may also be included in the event record.

This dataset contains a one-month sample of flattened EVENT data records from the New York City (NYC) Connected Vehicle (CV) Pilot that have undergone obfuscation of precise time and location details as well as other vehicle identifiers. The full unflattened event data from NYC CV pilot can be found in the ITS Sandbox. Each EVENT record documents the details of one application warning that occurred on an Aftermarket Safety Device (ASD) in an equipped host vehicle and includes CV messages from a defined recording time both before and after the warning was generated by the host ASD. Messages in the recording time window include the Basic Safety Messages (BSM) of the host vehicle that received the warning, as well as other BSMs received from the warning target equipped vehicle (for V2V applications) or other nearby equipped vehicles. Depending on the application warning type, MAP messages, Signal Phase and Timing (SPaT) messages, and Traveler Information Messages (TIM) that were heard by the host vehicle may also be included in the event record.

This dataset contains a one-month sample of flattened EVENT data records from the New York City (NYC) Connected Vehicle (CV) Pilot that have undergone obfuscation of precise time and location details as well as other vehicle identifiers. The full unflattened event data from NYC CV pilot can be found in the ITS Sandbox. Each EVENT record documents the details of one application warning that occurred on an Aftermarket Safety Device (ASD) in an equipped host vehicle and includes CV messages from a defined recording time both before and after the warning was generated by the host ASD. Messages in the recording time window include the Basic Safety Messages (BSM) of the host vehicle that received the warning, as well as other BSMs received from the warning target equipped vehicle (for V2V applications) or other nearby equipped vehicles. Depending on the application warning type, MAP messages, Signal Phase and Timing (SPaT) messages, and Traveler Information Messages (TIM) that were heard by the host vehicle may also be included in the event record.

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.

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.

The Tampa CV Pilot generates data from the interaction between vehicles and between vehicles and infrastructure. This dataset consists of Signal Phasing and Timing Message (SPaT) Messages transmitted by road-side units (RSU) located throughout the Tampa CV Pilot Study area. The full set of raw, SPaT data from Tampa CV Pilot can be found in the ITS Sandbox. The data fields follow SAE J2735 data frames (Section 6) and structure (Section 7). This dataset holds a flattened sample of the SPaT data from Tampa CV Pilot. A column of random numbers (randomNum) was added to allow for random sampling of data points within Socrata.

The Tampa CV Pilot generates data from the interaction between vehicles and between vehicles and infrastructure. This dataset consists of Signal Phasing and Timing Message (SPaT) Messages transmitted by road-side units (RSU) located throughout the Tampa CV Pilot Study area. The full set of raw, SPaT data from Tampa CV Pilot can be found in the ITS Sandbox. The data fields follow SAE J2735 data frames (Section 6) and structure (Section 7). This dataset holds a flattened sample of the SPaT data from Tampa CV Pilot. A column of random numbers (randomNum) was added to allow for random sampling of data points within Socrata.

The Tampa CV Pilot generates data from the interaction between vehicles and between vehicles and infrastructure. This dataset consists of Signal Phasing and Timing Message (SPaT) Messages transmitted by road-side units (RSU) located throughout the Tampa CV Pilot Study area. The full set of raw, SPaT data from Tampa CV Pilot can be found in the ITS Sandbox. The data fields follow SAE J2735 data frames (Section 6) and structure (Section 7). This dataset holds a flattened sample of the SPaT data from Tampa CV Pilot. A column of random numbers (randomNum) was added to allow for random sampling of data points within Socrata.

The Tampa CV Pilot generates data from the interaction between vehicles and between vehicles and infrastructure. This dataset consists of Traveler Information Messages (TIMs) transmitted by road-side units (RSU) located throughout the Tampa CV Pilot Study area. The full set of raw, TIM data from Tampa CV Pilot can be found in the ITS Sandbox. The data fields follow a SAE J2735 TIM message structure to convey important traffic information to onboard units (OBU) of equipped vehicles. Refer to SAE J2735 Section 5.16 Message: MSG_TravelerInformation Message (TIM). This dataset holds a flattened sample of the TIM data from Tampa CV Pilot. Three additional fields were added to this Socrata dataset during ETL: a geo column (travelerdataframe_msgId_position) to allow for mapping of the geocoded TIM data within Socrata, a random number column (randomNum) to allow for random sampling of data points within Socrata, and a time of day generated column (metadata_generatedAt_timeOfDay) to allow for filtering of data by generated time.

The Tampa CV Pilot generates data from the interaction between vehicles and between vehicles and infrastructure. This dataset consists of Traveler Information Messages (TIMs) transmitted by road-side units (RSU) located throughout the Tampa CV Pilot Study area. The full set of raw, TIM data from Tampa CV Pilot can be found in the ITS Sandbox. The data fields follow a SAE J2735 TIM message structure to convey important traffic information to onboard units (OBU) of equipped vehicles. Refer to SAE J2735 Section 5.16 Message: MSG_TravelerInformation Message (TIM). This dataset holds a flattened sample of the TIM data from Tampa CV Pilot. Three additional fields were added to this Socrata dataset during ETL: a geo column (travelerdataframe_msgId_position) to allow for mapping of the geocoded TIM data within Socrata, a random number column (randomNum) to allow for random sampling of data points within Socrata, and a time of day generated column (metadata_generatedAt_timeOfDay) to allow for filtering of data by generated time.

The Tampa CV Pilot generates data from the interaction between vehicles and between vehicles and infrastructure. This dataset consists of Traveler Information Messages (TIMs) transmitted by road-side units (RSU) located throughout the Tampa CV Pilot Study area. The full set of raw, TIM data from Tampa CV Pilot can be found in the ITS Sandbox. The data fields follow a SAE J2735 TIM message structure to convey important traffic information to onboard units (OBU) of equipped vehicles. Refer to SAE J2735 Section 5.16 Message: MSG_TravelerInformation Message (TIM). This dataset holds a flattened sample of the TIM data from Tampa CV Pilot. Three additional fields were added to this Socrata dataset during ETL: a geo column (travelerdataframe_msgId_position) to allow for mapping of the geocoded TIM data within Socrata, a random number column (randomNum) to allow for random sampling of data points within Socrata, and a time of day generated column (metadata_generatedAt_timeOfDay) to allow for filtering of data by generated time.

This dataset contains a sample of the broadcast Traveler Information Messages (TIM) being generated by the Wyoming Connected Vehicle (CV) Pilot. The full set of TIMs can be found in the ITS DataHub data sandbox. Revision Note: This dataset only contains TIM sample data prior to December 18, 2018. For the most recent sample of TIM data, please refer to the Schema Version 6 dataset or retrieve the data from the ITS DataHub data sandbox.

This dataset contains a sample of the broadcast Traveler Information Messages (TIM) being generated by the Wyoming Connected Vehicle (CV) Pilot. The full set of TIMs can be found in the ITS DataHub data sandbox. Revision Note: This dataset only contains TIM sample data prior to December 18, 2018. For the most recent sample of TIM data, please refer to the Schema Version 6 dataset or retrieve the data from the ITS DataHub data sandbox.

This dataset contains a sample of the broadcast Traveler Information Messages (TIM) being generated by the Wyoming Connected Vehicle (CV) Pilot. The full set of TIMs can be found in the ITS DataHub data sandbox. Revision Note: This dataset only contains TIM sample data prior to December 18, 2018. For the most recent sample of TIM data, please refer to the Schema Version 6 dataset or retrieve the data from the ITS DataHub data sandbox.

This dataset contains a sample of the broadcast Traveler Information Messages (TIM) being generated by the Wyoming Connected Vehicle (CV) Pilot. This dataset only contains SchemaVersion 6 TIM sample data from December 18, 2018 to present. It is updated hourly and will hold up to 3 million of the most recent TIM records. The Schema Version 6 data is described further here. For sample TIM data prior to December 18, 2018, please refer to the Schema Version 5 dataset. The full set of TIMs can be found in the ITS Sandbox.

This dataset contains a sample of the broadcast Traveler Information Messages (TIM) being generated by the Wyoming Connected Vehicle (CV) Pilot. This dataset only contains SchemaVersion 6 TIM sample data from December 18, 2018 to present. It is updated hourly and will hold up to 3 million of the most recent TIM records. The Schema Version 6 data is described further here. For sample TIM data prior to December 18, 2018, please refer to the Schema Version 5 dataset. The full set of TIMs can be found in the ITS Sandbox.

This dataset contains a sample of the broadcast Traveler Information Messages (TIM) being generated by the Wyoming Connected Vehicle (CV) Pilot. This dataset only contains SchemaVersion 6 TIM sample data from December 18, 2018 to present. It is updated hourly and will hold up to 3 million of the most recent TIM records. The Schema Version 6 data is described further here. For sample TIM data prior to December 18, 2018, please refer to the Schema Version 5 dataset. The full set of TIMs can be found in the ITS Sandbox.