The purpose of the data environment is to provide multi-modal data and contextual information (weather and incidents) that can be used to research and develop Intelligent Transportation System applications. This data set contains the following data for the two months of September and October 2011 in Pasadena, California: Highway network data, Demand data, Sample mobile sightings provided for a two-hour period, provided by AirSage (see note 1 below), Network performance data (measured and forecast), Work zone data, Weather data, and Changeable message sign data. 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.

Statistics on speeding rates and exceedance of speed limit along selected street segments throughout San Francisco. The dataset was prepared as part of the SF Indicators project and covers from 2004 through 2009. http://www.sfindicatorproject.org/indicators/view/49

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program.The freeway data consists of two months of data (Sept 15 2011 through Nov 15 2011) from dual-loop detectors deployed in the main line and on-ramps of a Portland-area freeway. The section of I-205 NB covered by this test data set is 10.09 miles long and the section of I-205 SB covered by this test data set is 12.01 miles long The data includes: flow, occupancy, and speed.

This set of data files is one of the four test data sets acquired by the USDOT Data Capture and Management program. It contains the following data for the six months from May 1 2011 to October 31 2011: -Raw and cleaned data for traffic detectors deployed by Washington Department of Transportation (WSDOT) along I-5 in Seattle. Data includes 20-second raw reports. -Incident response records from the WSDOT's Washington Incident Tracking System (WITS). -A record of all messages and travel times posted on WSDOT's Active Traffic -Management signs and conventional variable message signs on I-5. -Loop detector volume and occupancy data from arterials parallel to I-5, estimated travel times on arterials derived from Automatic License Plate Reader (ALPR) data, and arterial signal timing plans. -Scheduled and actual bus arrival times from King County Metro buses and Sound Transit buses. -Incidents on I-5 during the six month period -Seattle weather data for the six month period -A dataset of GPS breadcrumb data from commercial trucks described in the documentation is not available to the public because of data ownership and privacy issues. 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. Note: All extras are attached in Seattle Freeway Travel Times https://data.transportation.gov/Automobiles/Seattle-Freeway-Travel-Times/9v5g-t8u8

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.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program. This is the primary loop detector data table. It contains one-minute volume, occupancy, and data quality flags for the arterial loop detector data.

The ATDM Trajectory Validation project developed a validation framework and a trajectory computational engine to compare and validate simulated and observed vehicle trajectories and dynamics. The field data were used to demonstrate how on-site instrumented vehicle data can be used to validate simulated vehicle dynamics using the validation framework. The vehicle trajectory data were collected in a separate task of the Active Transportation Demand Management (ATDM) Trajectory Level Validation project. The primary project objective was to develop a methodology to validate simulated vehicle dynamics at the trajectory level. Microscopic and macroscopic performance measures were calculated from the trajectory data and used in a number of validation tests related to safety, vehicle limits, driver comfort levels, and traffic flow

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 Federal Motor Carrier Safety Administration's (FMCSA) Safety Management System (SMS) is an automated data system used by FMCSA to monitor motor carrier on-road safety performance. FMCSA analyzes safety performance by grouping carrier data in the SMS into seven Behavioral Analysis and Safety Improvement Categories (BASICs) which are, in turn, used to identify potential safety problems with individual carriers and determine when an enforcement intervention might be appropriate.

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.