- API
Gas Distribution, Gas Transmission & Gathering, LNG incidents and Hazardous Liquid Accident Data
datahub.transportation.gov | Last Updated 2024-07-24T18:56:57.000ZTitle 49 of the Code of Federal Regulations (49 CFR Parts 191, 195) requires pipeline operators to submit incident reports within 30 days of a pipeline incident or accident. The CFR defines accidents and incidents, as well as criteria for submitting reports to the Office of Pipeline Safety. Specific information includes the time and location of the incident(s), number of any injuries and/ or fatalities, commodity spilled/gas released, causes of failure and evacuation procedures. The reports are used for identifying long- and short-term trends at the national, state and operator-specific levels.
- API
Crossing Inventory Data (Form 71) - Historical
datahub.transportation.gov | Last Updated 2024-10-06T18:17:51.000ZThis dataset is in a user-friendly human-readable format. It contains the historical crossing inventory. To download the current inventory data, go here: https://data.transportation.gov/Railroads/Crossing-Inventory-Data-Form-71-Current/m2f8-22s6.
- API
AMS Pasadena Main Data
datahub.transportation.gov | Last Updated 2024-09-28T00:48:36.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
Tampa CV Pilot Traveler Information Message (TIM) Sample
datahub.transportation.gov | Last Updated 2024-05-01T01:04:33.000ZThe 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 <a href="http://usdot-its-cvpilot-publicdata.s3.amazonaws.com/index.html" target="_blank">ITS Sandbox</a>. 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.
- API
New York City CV Pilot EVENT Data One Month Sample
datahub.transportation.gov | Last Updated 2024-05-01T01:04:26.000ZThis 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 <a href="http://usdot-its-cvpilot-publicdata.s3.amazonaws.com/index.html" target="_blank" >ITS Sandbox</a>. 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.
- API
DOT Headquarters Closed Circuit Television -
datahub.transportation.gov | Last Updated 2018-12-19T00:13:39.000ZThis data set contains information closed circuit television camera locations, setups, and a 30-day archive of video captured by the cameras.
- API
Crossing Inventory Data (Form 71) - Current
datahub.transportation.gov | Last Updated 2024-10-06T11:22:55.000ZThis dataset is in a user-friendly human-readable format. It contains the current crossing inventory - one record for each crossing. To download historical data, go here: https://data.transportation.gov/Railroads/Crossing-Inventory-Data-Historical/vhwz-raag. To download the source dataset that contains raw data values, go here: https://data.transportation.gov/dataset/Crossing-Inventory-Source-Data-Form-71-Current/xp92-5xme.
- API
Injury/Illness Summary - Operational Data (Form 55)
datahub.transportation.gov | Last Updated 2024-10-05T05:19:00.000ZThis dataset is in a user-friendly human-readable format. To download the source dataset that contains raw data values, go here: https://data.transportation.gov/dataset/Form-55-Source-Table/unww-uhxd.
- API
Licensed Drivers, by state, gender, and age group
datahub.transportation.gov | Last Updated 2024-05-08T00:26:07.000ZLicensed driver data from Highway Statistics table DL-22, broken down by state, gender, and age group.
- API
National 9-1-1 Profile Database - National 9-1-1 Profile Database
datahub.transportation.gov | Last Updated 2024-05-01T01:04:43.000ZCollect and aggregate information from state level reporting entities that can be used to measure the progress of 9 1-1 authorities across the country in enhancing their existing operations and migrating to more advanced - Internet-Protocol-enabled emergency networks. The data will be maintained in a "National 9-1-1 Profile Database." One of the objectives of the National 9-1-1 Program is to develop, collect, and disseminate information concerning practices, procedures, and technology used in the implementation of E9 1 1 services and to support 9-1-1 Public Safety Answering Points (PSAPs) and related state and local public safety agencies for 9 1 1 deployment and operations. The National 9-1-1 profile database can be used to follow the progress of 9-1-1 authorities in enhancing their existing systems and implementing next-generation networks for more advanced systems.