- API
Crossing Inventory Data (Form 71) - Historical
datahub.transportation.gov | Last Updated 2024-10-08T18:18:34.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
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
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-09T11:26:46.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 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
Closed Enforcement Cases - Fiscal Year 2009
datahub.transportation.gov | Last Updated 2024-05-24T00:06:37.000ZContains data on civil penalties (fines) assessed by FMCSA against motor carriers, brokers and other entities.
- API
Closed Enforcement Cases - Fiscal Year 2005
datahub.transportation.gov | Last Updated 2024-05-24T00:06:37.000ZContains data on civil penalties (fines) assessed by FMCSA against motor carriers, brokers and other entities.
- API
Closed Enforcement Cases - Fiscal Year 2013
datahub.transportation.gov | Last Updated 2024-05-24T00:06:39.000ZContains data on civil penalties (fines) assessed by FMCSA against motor carriers, brokers and other entities.