- API
Pipeline Accident/Incident Reports - Natural Gas Transmission & Gathering Incident Data - 1970 to mid 1984 (ZIP)
datahub.transportation.gov | Last Updated 2018-12-19T00:12:16.000ZOperator Submission - Incident/Accident report data submitted to PHMSA by pipeline operators. Pipeline operators are required to submit incident reports within 30 days of a pipeline accident or incident. The key information that is collected contains; in-depth location information, facility and operating information, and cause of the accident and incident. Specific information includes the time and location of the incident, number of any injuries and/or fatalities, commodity spilled/gas released, causes of failure and evacuation procedures. Data sets are by following system types: 1) GD-Incident : Incident Report for Gas Distribution System, 2) GTGG-Incident: Incident Report for Natural and Other Gas Transmission and Gathering Systems, 3) HL-Incident: Accident Report for Hazardous Liquid Pipeline Systems, and 4) LNG-Incident: Incident Report for Liquefied Natural Gas (LNG) Facilities.
- API
Pipeline Accident/Incident Reports - Natural Gas Transmission & Gathering Incident Data - January 2010 to present (ZIP)
datahub.transportation.gov | Last Updated 2018-12-19T00:12:20.000ZOperator Submission - Incident/Accident report data submitted to PHMSA by pipeline operators. Pipeline operators are required to submit incident reports within 30 days of a pipeline accident or incident. The key information that is collected contains; in-depth location information, facility and operating information, and cause of the accident and incident. Specific information includes the time and location of the incident, number of any injuries and/or fatalities, commodity spilled/gas released, causes of failure and evacuation procedures. Data sets are by following system types: 1) GD-Incident : Incident Report for Gas Distribution System, 2) GTGG-Incident: Incident Report for Natural and Other Gas Transmission and Gathering Systems, 3) HL-Incident: Accident Report for Hazardous Liquid Pipeline Systems, and 4) LNG-Incident: Incident Report for Liquefied Natural Gas (LNG) Facilities.
- API
Pipeline Accident/Incident Reports
datahub.transportation.gov | Last Updated 2018-12-19T00:12:17.000ZOperator Submission - Incident/Accident report data submitted to PHMSA by pipeline operators. Pipeline operators are required to submit incident reports within 30 days of a pipeline accident or incident. The key information that is collected contains; in-depth location information, facility and operating information, and cause of the accident and incident. Specific information includes the time and location of the incident, number of any injuries and/or fatalities, commodity spilled/gas released, causes of failure and evacuation procedures. Data sets are by following system types: 1) GD-Incident : Incident Report for Gas Distribution System, 2) GTGG-Incident: Incident Report for Natural and Other Gas Transmission and Gathering Systems, 3) HL-Incident: Accident Report for Hazardous Liquid Pipeline Systems, and 4) LNG-Incident: Incident Report for Liquefied Natural Gas (LNG) Facilities.
- API
Pipeline Accident/Incident Reports - Hazardous Liquid Accident Data - January 2002 to December 2009 (ZIP)
datahub.transportation.gov | Last Updated 2018-12-19T00:12:16.000ZOperator Submission - Incident/Accident report data submitted to PHMSA by pipeline operators. Pipeline operators are required to submit incident reports within 30 days of a pipeline accident or incident. The key information that is collected contains; in-depth location information, facility and operating information, and cause of the accident and incident. Specific information includes the time and location of the incident, number of any injuries and/or fatalities, commodity spilled/gas released, causes of failure and evacuation procedures. Data sets are by following system types: 1) GD-Incident : Incident Report for Gas Distribution System, 2) GTGG-Incident: Incident Report for Natural and Other Gas Transmission and Gathering Systems, 3) HL-Incident: Accident Report for Hazardous Liquid Pipeline Systems, and 4) LNG-Incident: Incident Report for Liquefied Natural Gas (LNG) Facilities.
- API
Pipeline Accident/Incident Reports - Hazardous Liquid Accident Data - January 2010 to present (ZIP)
datahub.transportation.gov | Last Updated 2018-12-19T00:12:16.000ZOperator Submission - Incident/Accident report data submitted to PHMSA by pipeline operators. Pipeline operators are required to submit incident reports within 30 days of a pipeline accident or incident. The key information that is collected contains; in-depth location information, facility and operating information, and cause of the accident and incident. Specific information includes the time and location of the incident, number of any injuries and/or fatalities, commodity spilled/gas released, causes of failure and evacuation procedures. Data sets are by following system types: 1) GD-Incident : Incident Report for Gas Distribution System, 2) GTGG-Incident: Incident Report for Natural and Other Gas Transmission and Gathering Systems, 3) HL-Incident: Accident Report for Hazardous Liquid Pipeline Systems, and 4) LNG-Incident: Incident Report for Liquefied Natural Gas (LNG) Facilities.
- API
Pipeline Accident/Incident Reports - Natural Gas Distribution Incident Data - March 2004 to December 2009 (ZIP)
datahub.transportation.gov | Last Updated 2018-12-19T00:12:16.000ZOperator Submission - Incident/Accident report data submitted to PHMSA by pipeline operators. Pipeline operators are required to submit incident reports within 30 days of a pipeline accident or incident. The key information that is collected contains; in-depth location information, facility and operating information, and cause of the accident and incident. Specific information includes the time and location of the incident, number of any injuries and/or fatalities, commodity spilled/gas released, causes of failure and evacuation procedures. Data sets are by following system types: 1) GD-Incident : Incident Report for Gas Distribution System, 2) GTGG-Incident: Incident Report for Natural and Other Gas Transmission and Gathering Systems, 3) HL-Incident: Accident Report for Hazardous Liquid Pipeline Systems, and 4) LNG-Incident: Incident Report for Liquefied Natural Gas (LNG) Facilities.
- API
Crossing Inventory Data (Form 71) - Historical
datahub.transportation.gov | Last Updated 2024-05-14T18:24:14.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
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.