AndreaBozzo/ceres-open-data-index huggingface dataset:
Rail Equipment Accident/Incident Data (Form 54) Subset – Unique Train Accidents (Not at Grade Crossings)

October 2025 - Dataset View and OData/API Connection Change Notice - Please Read: https://data.transportation.gov/stories/s/6kdh-gsgx Rail equipment accidents/incidents, collisions, derailments, fires, explosions, acts of God, or other events involving the operation of railroad on-track equipment (standing or moving) and causing reportable damages greater than the reporting threshold for the year in which the accident/incident occurred, must be reported by railroads to the FRA on Form FRA 6180.54 - Rail Equipment Accident/Incident. Please note that this dataset displays unique train accidents. When an accident involves multiple railroads, each railroad must report its data. As a result, there can be multiple records for one accident. This dataset has been modified to pull and display one record for each accident. Highway-rail crossing incidents have also been removed from this dataset because they are not considered train accidents. To see the full dataset with all reports with all data for all accidents, please visit https://data.transportation.gov/Railroads/Rail-Equipment-Accident-Incident-Data/85tf-25kj. The data dictionary can be found here: https://datahub.transportation.gov/api/views/byy5-w977/files/ac84a1c8-56d4-4a21-85c2-3a33080ab720?download=true&filename=Form54_Data_Dictionary.xlsx. For information on how to filter and export data, please visit: https://data.transportation.gov/stories/s/Download-Export-and-Print-User-Guide/s8hj-vns8/. To view the data release schedule, please visit: https://data.transportation.gov/stories/s/Data-Release-Schedule/qfc9-tapk/.
Rail Equipment Accident/Incident Data (Form 54)

Rail equipment accidents/incidents, collisions, derailments, fires, explosions, acts of God, or other events involving the operation of railroad on-track equipment (standing or moving) and causing reportable damages greater than the reporting threshold for the year in which the accident/incident occurred, must be reported by railroads to the FRA on Form FRA 6180.54 - Rail Equipment Accident/Incident. This 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-54-Source-Table/aqxq-n5hy. The data dictionary can be found here: https://data.transportation.gov/api/views/85tf-25kj/files/729e3c9c-7dff-429d-9ac0-8f35a0762aa2?download=true&filename=Form54_Data_Dictionary.xlsx For information on how to filter and export data, please visit: https://data.transportation.gov/stories/s/Download-Export-and-Print-User-Guide/s8hj-vns8/. To view the data release schedule, please visit: https://data.transportation.gov/stories/s/Data-Release-Schedule/qfc9-tapk/.
NYC CV Pilot IE Processed Data

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.
Non-Major Safety and Security Events (FRA Commuter Rail Only)

Counts of Non-Major Safety and Security Events are reported to the National Transit Database on a monthly basis, by transit agency and transit mode. These include minor fires on transit property requiring suppression, transit worker assaults not involving transport for medical attention, and other safety events that are not reportable as Major Events because a Major Event reporting threshold is not met (see Safety and Security Events dataset for a list of Major Events). This file includes event data reported to the National Transit Database (NTD) for Commuter Rail (CR) and Alaska Railroad (AR) modes, as well as Heavy Rail (HR) service reported for Port Authority Trans Hudson (NTD ID: 20098), Hybrid Rail (YR) service for the Tri-County Metropolitan Transportation District of Oregon (NTD ID: 00008), Hybrid Rail (YR) service for Denton County Transportation Authority (NTD ID: 60101), and Hybrid Rail (YR) service for Capital Metropolitan Transportation Authority (NTD ID: 60048). Because these services fall under the safety oversight of the Federal Railroad Administration, the agencies are not required to report Safety Events (e.g., collisions, derailments, etc.) to the Federal Transit Administration through the NTD. Security events occurring on transit-owned property for these entities are reported to NTD, but excluded from other files to preserve the integrity of those datasets. They are presented in this file for completeness and should be considered by any user attempting to understand the scope and scale of reportable Security Events reported by public transit operators.
Non-Major Safety and Security Events

Counts of Non-Major Safety and Security Events are reported to the National Transit Database on a monthly basis, by transit agency and transit mode. These include minor fires on transit property requiring suppression, transit worker assaults not involving transport for medical attention, and other safety events that are not reportable as Major Events because a Major Event reporting threshold is not met (see Safety and Security Events dataset for a list of Major Events). In this file you will find the number of occurrences or safety incidents per month and the number of injuries in Safety Events (Safety/Security = SAF) where an individual was immediately transported away from the scene for medical attention due to those occurrences. There will be one entry for any transit mode/location with at least one occurrence for the given month. The file also contains Transit Worker Assaults which did not immediately transport away from the scene for 2023-present, as well as other Security Events (Safety/Security = SEC) reported historically but no longer collected by FTA. Note that an assault involving transport away from the scene for medical attention meets the Injury threshold and is not counted in this dataset. Agencies are not required to provide details for these events, and any description provided is omitted. The description can be available upon request. Update 5/6/24: FTA has updated its validation procedure for Non-Major S&S events to allow for inclusion in the data publication sooner in certain cases. This month, users of this dataset may notice a larger increase in S&S events than normal for certain records in 2023-2024 (only years for which data collection and validation is presently ongoing) compared to prior releases. This was done to allow for a more timely release of validated data.
NHCCI

The National Highway Construction Cost Index (NHCCI) is a price index that can be used both to track price changes associated with highway construction costs, and to convert current dollar expenditures on highway construction to real or constant dollar expenditures. This dataset contains the quarterly NHCCI estimates as well as the Seasonally Adjusted NHCCI and Component Contributions to Changes in NHCCI. Visit https://www.fhwa.dot.gov/policy/otps/nhcci/ for more information regarding the NHCCI.
Next Generation Simulation (NGSIM) Vehicle Trajectories and Supporting Data

Click “Export” on the right to download the vehicle trajectory data. The associated metadata and additional data can be downloaded below under "Attachments". Researchers for the Next Generation Simulation (NGSIM) program collected detailed vehicle trajectory data on southbound US 101 and Lankershim Boulevard in Los Angeles, CA, eastbound I-80 in Emeryville, CA and Peachtree Street in Atlanta, Georgia. Data was collected through a network of synchronized digital video cameras. NGVIDEO, a customized software application developed for the NGSIM program, transcribed the vehicle trajectory data from the video. This vehicle trajectory data provided the precise location of each vehicle within the study area every one-tenth of a second, resulting in detailed lane positions and locations relative to other vehicles. Click the "Show More" button below to find additional contextual data and metadata for this dataset. For site-specific NGSIM video file datasets, please see the following: - NGSIM I-80 Videos: https://data.transportation.gov/Automobiles/Next-Generation-Simulation-NGSIM-Program-I-80-Vide/2577-gpny - NGSIM US-101 Videos: https://data.transportation.gov/Automobiles/Next-Generation-Simulation-NGSIM-Program-US-101-Vi/4qzi-thur - NGSIM Lankershim Boulevard Videos: https://data.transportation.gov/Automobiles/Next-Generation-Simulation-NGSIM-Program-Lankershi/uv3e-y54k - NGSIM Peachtree Street Videos: https://data.transportation.gov/Automobiles/Next-Generation-Simulation-NGSIM-Program-Peachtree/mupt-aksf
New York City CV Pilot EVENT Data One Month Sample

This 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 requested from the [ITS DataHub Sandbox]. 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.
North Carolina Department of Transportation (NCDOT) Work Zone Data Exchange (WZDx)

This dataset provides archived information on work zones in the state of North Carolina in a tabular format. The ITS JPO has collections from 23 states including North Carolina covering various parts of the time period from 10/2019 to 08/2024 depending on when the feed was active. The data is split into two archive files, the raw data contains the collection of .json or .geojson files exactly as they were on the individual state’s WZDx feed at the time of collection. The processed data is organized by work zone, so that as information about the work zone changed through feed updates they would be collected in a single file for that work zone. To request access fill out the form [here].
Multi-Modal Intelligent Traffic Signal Systems Vehicle Trajectories for Roadside Equipment

Data were collected during the Multi-Modal Intelligent Transportation Signal Systems (MMITSS) study. MMITSS is a next-generation traffic signal system that seeks to provide a comprehensive traffic information framework to service all modes of transportation. The Vehicle Trajectories file is populated with basic safety messages received from equipped vehicle within the communication range of an Roadside Equipment (RSEs). The data also contains elements that communicate additional details about the vehicle that is used for vehicle safety applications, and elements that communicate specific items of a vehicle‘s status that are used in data event snapshots which are gathered and periodically reported to an RSEs. These data are transmitted at a rate of 10 Hz. NOTE: All extra attachments are located in Multi-Modal Intelligent Traffic Signal Systems Basic Safety Message
Multi-Modal Intelligent Traffic Signal Systems Signal Plans for Roadside Equipment

Data were collected during the Multi-Modal Intelligent Transportation Signal Systems (MMITSS) study. MMITSS is a next-generation traffic signal system that seeks to provide a comprehensive traffic information framework to service all modes of transportation.The Signal Plans for Roadside Equipment (RSE) data contains the basics of a Signal Phase and Timing (SPAT) message. This data includes SPAT message and the timestamp of the SPAT message. The data also provides the signal phase and timing information for one or more movements at an intersection.
Multi-Modal Intelligent Traffic Signal Systems GPS

Data were collected during the Multi-Modal Intelligent Transportation Signal Systems (MMITSS) study. MMITSS is a next-generation traffic signal system that seeks to provide a comprehensive traffic information framework to service all modes of transportation. The GPS data set catalogs the vehicle operation data of the test vehicles that used for the MMITSS field testing. The data contains the performance and operation details of vehicles. This file contains a number of fields detailing elements such as vehicle position and speed, fidelity measures of GPS-based data elements, and vehicle operation data. NOTE: All extra attachments are located in Multi-Modal Intelligent Traffic Signal Systems Basic Safety Message
Multi-Modal Intelligent Traffic Signal Systems Basic Safety Message

The data attached and/or displayed were collected during the Multi-Modal Intelligent Transportation Signal Systems (MMITSS) study. MMITSS is a next-generation traffic signal system that seeks to provide a comprehensive traffic information framework to service all modes of transportation. A BSM is one of the messages belonging to the Society of Automotive Engineers (SAE) J2735 Standard. This standard is geared toward supporting the interoperability of DSRC applications through the use of a standardized message set and its data frames and data elements. A BSM, which is at times referred to as a “heartbeat” message, is a frequently transmitted message (usually at approximately 10Hz) that is meant to increase a vehicle’s situational awareness. These messages are intended to be used for a variety of applications to exchange safety data regarding a vehicle’s state. A typical BSM contains up to two parts. Part I, the binary large object (blob), is included in every BSM. It contains the fundamental data elements that describe a vehicle’s position (latitude, longitude, elevation) and motion (heading, speed, acceleration). Part II of a BSM contains optional data that is transmitted when required or in response to an event. Typically Part II contains data that serves as an extension of vehicle safety information (path history, path prediction, event flags) and data pertaining to the status of a vehicle’s components, such as lights, wipers, and brakes. NOTE: All extra attachments are located in Multi-Modal Intelligent Traffic Signal Systems Basic Safety Messages such as MAP, Detectors, and Simulation results
Motus RevokeSuspend – All With History

*This is an All With History dataset*. Information on carrier/broker/freight forwarder authorities that have been suspended or revoked by FMCSA. The dataset includes the DOT number and docket number of the entity, the type of authority suspension/revocation, and the reason. Note: DOCKET_NUMBER and USDOT_NUMBER can have duplicates in this file, since this file will show each suspension/revocation that occurred per OA, which could change multiple times. Please refer attached data dictionary for additional details.
Motus RevokeSuspend

*This is a Daily Difference dataset*. Information on carrier/broker/freight forwarder authorities that have been suspended or revoked by FMCSA. The dataset includes the DOT number and docket number of the entity, the type of authority suspension/revocation, and the reason. Note: DOCKET_NUMBER and USDOT_NUMBER can have duplicates in this file, since this file will show each suspension/revocation that occurred per OA, which could change multiple times. Please refer attached data dictionary for additional details.
Motus Insur - All With History

*This is an All With History dataset*. Records for carrier/broker/freight forwarder active or pending individual insurance policies. The records are linked to the entities by docket numbers included in the dataset. The dataset contains information on the insurance policy, including insurance company name, policy number and type of insurance. Entities can hold multiple insurance policies, so there may be multiple records associated with a particular entity. Please refer attached data dictionary for additional details.
Motus InsHist - All With History

*This is an All With History dataset*. This dataset contains information on a carrier’s/broker’s/freight forwarder’s previous insurance policy(ies). This dataset contains the DOT number and docket number of the entity. Additionally, it contains the cancellation method (cancelled, replaced, name change, transferred), the type of policy, the policy number, and the effective and cancellation dates of the policy. Note: all insurance information is related to the insurance policy either being cancelled, being replaced, or prior to a name change. It is not the subsequent (if applicable) policy. Please refer attached data dictionary for additional details.
Motus InsHist

*This is a Daily Difference dataset*. This dataset contains information on a carrier’s/broker’s/freight forwarder’s previous insurance policy(ies). This dataset contains the DOT number and docket number of the entity. Additionally, it contains the cancellation method (cancelled, replaced, name change, transferred), the type of policy, the policy number, and the effective and cancellation dates of the policy. Note: all insurance information is related to the insurance policy either being cancelled, being replaced, or prior to a name change. It is not the subsequent (if applicable) policy. Please refer attached data dictionary for additional details.
Motus Carrier - All With History

*This is an All With History dataset*. Records for all carriers/brokers/freight forwarders with active, inactive, or pending operating authorities. It includes the DOT number and docket number for the carrier/broker/freight forwarder, along with entity census, authority, and insurance data (e.g., types of authority, address, types of insurance on file, and amounts of insurance on file). Note: DOCKET_NUMBER and DOT_NUMBER can have duplicates in this file, since this file will show each OA per Docket Number and a single USDOT number can have multiple docket numbers. Also, the legacy registration system allowed multiple OAs per docket number, while Motus will assign a unique docket number to each OA and allows multiple OAs per USDOT number. Please refer attached data dictionary for additional details.
Motus Carrier

*This is a Daily Difference dataset*. Records for all carriers/brokers/freight forwarders with active, inactive, or pending operating authorities. It includes the DOT number and docket number for the carrier/broker/freight forwarder, along with entity census, authority, and insurance data (e.g., types of authority, address, types of insurance on file, and amounts of insurance on file). Note: DOCKET_NUMBER and DOT_NUMBER can have duplicates in this file, since this file will show each OA per Docket Number and a single USDOT number can have multiple docket numbers. Also, the legacy registration system allowed multiple OAs per docket number, while Motus will assign a unique docket number to each OA and allows multiple OAs per USDOT number. Please refer attached data dictionary for additional details.
Motus BOC3 - All With History

*This is an All With History dataset*. This dataset contains records for each Blanket Company (BOC-3 agent) hired by a carrier/broker/freight forwarder. Each entity must hire a BOC-3 agent to represent them in legal matters to obtain operating authority. In some cases, entities may act as their own BOC-3 agent. The records in the dataset contain the BOC-3 agent’s name and address. The dataset also contains the USDOT number and Docket number of the represented entity. Please refer attached data dictionary for additional details.
Motus BOC3

*This is a Daily Difference dataset*. This dataset contains records for each Blanket Company (BOC-3 agent) hired by a carrier/broker/freight forwarder. Each entity must hire a BOC-3 agent to represent them in legal matters to obtain operating authority. In some cases, entities may act as their own BOC-3 agent. The records in the dataset contain the BOC-3 agent’s name and address. The dataset also contains the USDOT number and Docket number of the represented entity. Please refer attached data dictionary for additional details.
Motus AuthHist - All With History

*This is an All With History dataset*. Records showing the history of each authority granted to a carrier/broker/freight forwarder, along with the dates of the original authority action (e.g., “Active”) and the final authority action (e.g., “Inactive”). The dataset contains the USDOT number and docket number of the entity that holds or held the authority. As there can be multiple authorities for a single entity, there may be multiple records for an entity. Please refer attached data dictionary for additional details.
Motus AuthHist

*This is a Daily Difference dataset*. Records showing the history of each authority granted to a carrier/broker/freight forwarder, along with the dates of the original authority action (e.g., “Active”) and the final authority action (e.g., “Inactive”). The dataset contains the USDOT number and docket number of the entity that holds or held the authority. As there can be multiple authorities for a single entity, there may be multiple records for an entity. Please refer attached data dictionary for additional details.
Monthly Modal Time Series

Modal Service data and Safety & Security (S&S) public transit time series data delineated by transit/agency/mode/year/month. Includes all Full Reporters--transit agencies operating modes with more than 30 vehicles in maximum service--to the National Transit Database (NTD). This dataset will be updated monthly. The monthly ridership data is released one month after the month in which the service is provided. Records with null monthly service data reflect late reporting. The S&S statistics provided include both Major and Non-Major Events where applicable. Events occurring in the past three months are excluded from the corresponding monthly ridership rows in this dataset while they undergo validation. This dataset is the only NTD publication in which all Major and Non-Major S&S data are presented without any adjustment for historical continuity.
Massachusetts Department of Transportation (MassDOT) Work Zone Data Exchange (WZDx) v3.1 Feed Sample

This dataset provides archived information on work zones in the state of Massachusetts in a tabular format. The ITS JPO has collections from 23 states including Massachusetts covering various parts of the time period from 10/2019 to 08/2024 depending on when the feed was active. The data is split into two archive files, the raw data contains the collection of .json or .geojson files exactly as they were on the individual state’s WZDx feed at the time of collection. The processed data is organized by work zone, so that as information about the work zone changed through feed updates they would be collected in a single file for that work zone. To request access fill out the form [here].