- API
NTD Monthly Module Data Set - September 2015 Raw Data
datahub.transportation.gov | Last Updated 2024-03-05T00:50:48.000ZData collected monthly from urbanized area transit systems. The Monthly module includes a limited set of key indicators reported by transit properties. Data is reported on a monthly basis, by mode and type of service, for a calendar year. The four data items included are: Unlinked Passenger Trips, Vehicle Revenue Miles, Vehicle Revenue Hours, and Vehicles Operated in Maximum Service (Peak Vehicles). Monthly data are reported by mode and type of service.
- API
Crossing Inventory Data (Form 71) - Historical
datahub.transportation.gov | Last Updated 2024-06-15T18:18:31.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
Pipeline Accident/Incident Reports - Natural Gas Distribution Incident Data - March 2004 to December 2009 (ZIP)
datahub.transportation.gov | Last Updated 2024-06-03T23:51:21.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
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-06-16T11:14:57.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
Intelligent Transportation Systems (ITS) Costs
datahub.transportation.gov | Last Updated 2024-05-21T14:32:07.000ZThe Intelligent Transportation Systems Joint Program Office (ITS JPO) of the U.S. Department of Transportation (U.S. DOT) established the ITS Costs Database as a national resource for transportation professionals to go to in order to obtain cost estimates for ITS deployments. The purpose of the ITS Costs Database is to support informed decision-making by transportation leaders. The ITS Costs Database contains estimates of ITS costs that can be used for developing project cost estimates during the planning process or preliminary design phase, and for policy studies and cost-benefit analyses. Both non-recurring (capital) and recurring (operating and maintenance) costs are provided where possible. Two types of cost data are available: unit costs and system cost summaries. System cost summaries are the costs of an ITS project or portion of an ITS project such as the cost of expanding a statewide road weather information system or the detailed costs for a signal interconnect project. Each entry describes the background of the project, the ITS technologies deployed, and presents the costs and what the costs covered. A breakout of components and costs is provided for most summaries depending on the information available. Both capital costs and annual O&M costs are presented whenever possible. Unit costs are the costs associated with an individual ITS element, such as a video camera for traffic surveillance or a dynamic message sign. A range of costs (e.g., $500 - $1,000) is presented for the capital cost and annual operations and maintenance (O&M) cost of each element as well as an estimate of the length in years of its usable life. Unit costs are available in two formats: unadjusted and adjusted. Unadjusted costs are presented as the original value along with the dollar year.
- API
Basic Safety Message Data Emulator
datahub.transportation.gov | Last Updated 2024-05-20T17:39:15.000ZThe 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.
- API
NTD Monthly Module Data Set - September 2015 Adjusted Data
datahub.transportation.gov | Last Updated 2024-03-05T00:55:28.000ZData collected monthly from urbanized area transit systems. The Monthly module includes a limited set of key indicators reported by transit properties. Data is reported on a monthly basis, by mode and type of service, for a calendar year. The four data items included are: Unlinked Passenger Trips, Vehicle Revenue Miles, Vehicle Revenue Hours, and Vehicles Operated in Maximum Service (Peak Vehicles). Monthly data are reported by mode and type of service.