- API
AMS Pasadena Main Data
datahub.transportation.gov | Last Updated 2024-05-20T17:46:07.000ZThe data in this data environment was collected from the Pasadena, California testbed, namely I-210, SR 134, and nearby arterials. The source of these data is from the Caltrans – Performance Measurement System (PeMS). Speed data from this dataset were used to derive the freeway travel time. There are three separate text files with one for each operational condition.
- API
Intelligent Network Flow Optimization Prototype Traffic Management Entity-Based Queue Warning
datahub.transportation.gov | Last Updated 2024-05-21T14:29:49.000ZData 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.
- API
Enhancing Microsimulation Models for Improved Work Zone Planning: Car-Following Data from Western Massachusetts (Runs)
datahub.transportation.gov | Last Updated 2024-05-01T01:04:19.000ZThe data describe freeway car-following behavior (such as velocity, acceleration, and relative position) for the car-following instances observed during 6 data collection runs, collected using an Instrumented Research Vehicle (IRV) along freeways and arterials in western Massachusetts in the summer of 2016 to better understand work zone driver behaviors. The USDOT Volpe National Transportation Systems Center (Volpe Center) identified, isolated, and classified individual car following instances from within the raw datasets (classification parameters included roadway type, level of congestion, and speed limit), then processed, refined, and cleaned the dataset. This table contains metadata about each data collection run. See also the instances table (https://datahub.transportation.gov/Automobiles/Enhancing-Microsimulation-Models-for-Improved-Work/74ug-57tr) and radar table (https://datahub.transportation.gov/Automobiles/Enhancing-Microsimulation-Models-for-Improved-Work/4qbx-egtn).
- API
Intelligent Network Flow Optimization Prototype Basic Safety Messages
datahub.transportation.gov | Last Updated 2024-05-20T17:28:15.000ZData 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).
- API
Advanced Messaging Concept Development: Probe Vehicle Data
datahub.transportation.gov | Last Updated 2024-05-13T17:15:09.000ZContains 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.
- API
Advanced Messaging Concept Development: Probe Data Control Message
datahub.transportation.gov | Last Updated 2024-05-13T17:16:55.000ZContains 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.