AndreaBozzo/ceres-open-data-index huggingface dataset:
Massachusetts Department of Transportation (MassDOT) Work Zone Data Exchange (WZDx) v2.0 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].
Maricopa County Regional Work Zone Data Exchange (WZDx) v3.0 Feed Sample

The WZDx Specification enables infrastructure owners and operators (IOOs) to make harmonized work zone data available for third party use. The intent is to make travel on public roads safer and more efficient through ubiquitous access to data on work zone activity. Specifically, the project aims to get data on work zones into vehicles to help automated driving systems (ADS) and human drivers navigate more safely. MCDOT leads the effort to aggregate and collect work zone data from the AZTech Regional Partners. The live feed is currently compliant with [WZDx specification version 3.0]. The ITS JPO has collections from 23 states including Arizona 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].
Maricopa County Regional Work Zone Data Exchange (WZDx) v1.1 Feed Sample

The WZDx Specification enables infrastructure owners and operators (IOOs) to make harmonized work zone data available for third party use. The intent is to make travel on public roads safer and more efficient through ubiquitous access to data on work zone activity. Specifically, the project aims to get data on work zones into vehicles to help automated driving systems (ADS) and human drivers navigate more safely. MCDOT leads the effort to aggregate and collect work zone data from the AZTech Regional Partners. A continuously updating archive of the WZDx feed data can be found at [ITS WorkZone Data Sandbox]. The live feed is currently compliant with [WZDx specification version 1.1].
Major Safety and Security Events

This is a list of all Major Safety and Security Events from January of 2014 to the most recently published data within the Federal Transit Administration's major event time series: https://www.transit.dot.gov/ntd/data-product/safety-security-major-only-time-series-data Monthly Safety and Security data are released to this dataset within three months of being submitted to the NTD. Generally, there will be at least 90-day lag between when the event occurs and when it is included in this data set. Following the 2023 reporting change, where transit agencies were required to provide additional detail when a transit worker was injured in an assault, we began capturing a transit worker assault flag in our database and publishing the flag in the Major Events file at data.transportation.gov. This flag is useful for creating summary counts of TWA since the reporting change. However, for events prior to the reporting change the values in this column were misleading. For data users unfamiliar with the change in reporting circa 2023, they may be under the impression that we did not collect transit worker assault data prior to 2023, or even that there were no transit worker assault events prior to 2023. Users previously had to filter on 4 different columns to derive pre-2023 transit worker assault events. We have now incorporated that filter logic into the production of the transit worker flag column. Filtering and summarizing using this column now produces counts that align with annual totals for transit worker assaults across all our files.
Intelligent Network Flow Optimization Prototype Traffic Management Entity-Based Speed Harmonization

Data 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 speed harmonization messages that were recommended by the INFLO SPD-HARM algorithm and sent by the traffic management center to the connected vehicles, which provided drivers with the suggested speed while driving on the segment of I-5 that was included in the test. The objective of speed harmonization is to dynamically adjust and coordinate maximum appropriate vehicle speeds in response to downstream congestion, incidents, and weather or road conditions in order to maximize traffic throughput and reduce crashes.
Intelligent Network Flow Optimization Prototype Traffic Management Entity-Based Queue Warning

Data 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.
Intelligent Network Flow Optimization Prototype Infrastructure Traffic Sensor System Data Aggregator

Data 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 real-time volume, speed and loop occupancy data that were collected from WSDOT’s simulated roadway sensors every 20 seconds and aggregated according to user defined procedures and threshold by the Infrastructure Traffic Sensor System (TSS) Data Aggregator software.
Intelligent Network Flow Optimization Prototype Basic Safety Messages

Data 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. Basic Safety Messages (BSM) sent by connected vehicles (CVs) through either the cellular network or Dedicated Short Range Communication (DSRC) when the vehicle is in the range of Roadside Units (RSU). These messages were received by the traffic management center (TMC).
Insur - 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. Note: This dataset was last refreshed on 05/14/2026 and will no longer be updated. See attached "FMCSA Operating Authority Data Dictionary_V2" for more information.
Wyoming CV Pilot Traveler Information Message Sample (Schema Version 6)

This dataset contains a sample of the broadcast Traveler Information Messages (TIM) being generated by the Wyoming Connected Vehicle (CV) Pilot. This dataset only contains SchemaVersion 6 TIM sample data from December 18, 2018 to present. It is updated hourly and will hold up to 3 million of the most recent TIM records. The Schema Version 6 data is described further [here]. For sample TIM data prior to December 18, 2018, please refer to the [Schema Version 5 dataset]. The full set of TIMs can be requested from the [ITS DataHub Sandbox].
Iowa 4.0 Work Zone Data Exchange Feed Example

This dataset provides archived lane closure occurrences within the Iowa Department of Transportation (IDOT) highway system in a tabular format. The ITS JPO has collections from 23 states including Iowa 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.
InsHist - 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. 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. Note: This dataset was last refreshed on 05/14/2026 and will no longer be updated. See attached "FMCSA Operating Authority Data Dictionary_V2" for more information.
Injury/Illness Summary - Operational Source Data (Form 55)

All railroads are required to submit their operational data for train miles, employee hours worked, yard switching miles, the number of passengers transported, and passenger miles monthly on Form FRA F 6180.55 Injury/Illness Summary [Operational Data]. This dataset is the source dataset and contains raw data values. It replaced the legacy data download (https://safetydata.fra.dot.gov/OfficeofSafety/publicsite/on_the_fly_download.aspx). To download data that contains data is a user-friendly human-readable format, please reference https://data.transportation.gov/Railroads/Injury-Illness-Summary-Operational-Data/m8i6-zdsy. The data dictionary can be found here: https://data.transportation.gov/api/views/unww-uhxd/files/fa3f4232-2794-45ed-8062-afae43a860fd?download=true&filename=rrsfile_EFFECTIVE_060111%20(1).pdf. 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/.
Injury/Illness Summary - Operational Data (Form 55)

All railroads are required to submit their operational data for train miles, employee hours worked, yard switching miles, the number of passengers transported, and passenger miles monthly on Form FRA F 6180.55 Injury/Illness Summary [Operational Data]. 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-55-Source-Table/unww-uhxd. The data dictionary can be found here: https://datahub.transportation.gov/api/views/m8i6-zdsy/files/9271e9d5-ff71-4b06-a050-2ba1765bca36?download=true&filename=Form55_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/.
Injury/Illness Summary - Casualty Source Data (Form 55A)

Casualties are reportable fatalities, injuries, or illnesses arising from the operation of a railroad. Casualties may be classified as either fatal or nonfatal. All casualty incidents are reported to the FRA on Form FRA F 6180.55a Injury/Illness Continuation Sheet. This dataset is the source dataset and contains raw data values. It replaced the legacy data download (https://safetydata.fra.dot.gov/OfficeofSafety/publicsite/on_the_fly_download.aspx). To download data that contains data in a user-friendly human-readable format, please reference https://data.transportation.gov/Railroads/Injury-Illness-Summary-Casualty-Data/rash-pd2d. The data dictionary can be found here: https://data.transportation.gov/api/views/kuvg-3uwp/files/8785fa80-4d47-449e-9ce7-887540a258e2?download=true&filename=casfile_EFFECTIVE_060111%20(7).pdf. 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/.
Injury/Illness Summary - Casualty Data (Form 55a)

Casualties are reportable fatalities, injuries, or illnesses arising from the operation of a railroad. Casualties may be classified as either fatal or nonfatal. All casualty incidents are reported to the FRA on Form FRA F 6180.55a Injury/Illness Continuation Sheet. 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/Form55a-Source-Table/kuvg-3uwp. The data dictionary can be found here: https://datahub.transportation.gov/api/views/rash-pd2d/files/26b34409-e658-4681-a55e-d9c03079c33c?download=true&filename=Form55a_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/.
BSM from UDOT and Panasonic Connected Vehicle Data Ecosystem Program

This dataset contains V2X data collected from the Utah Connected Vehicle Data Ecosystem Program. We have submitted 7 days of deduplicated Basic Safety Messages (BSMs) in J2735 standards from 3 intersections in Orem, UT.This includes: (1) vehicles equipped with OBUs (Onboard Units) for real-time V2X (Vehicle-to-Everything) data transmission and reception, (2) road-side units (RSUs) capable of capturing, transmitting, and processing data from the transportation environment, and (3) a secure, scalable cloud platform for aggregating, analyzing, and visualizing transportation data.
HPMS Spatial All Sections - 2024

A GeoJSON file with all spatial roadway data for all sections from the 2024 Highway Performance Monitoring System (HPMS) attached to the All Road Network of Linear Referenced Data (ARNOLD) network. This file was produced using what is known as the “Spatial Full Join” process in HPMS, which is a spatial dynamic segmentation of the HPMS data to create homogeneous roadway sections. To be included in the file, only one data item must be present on a section of road. See attached README file for more details.
HPMS Sample Mid-America 2018

This data represents HPMS Sample limits that correspond to the HPMS Section Data. This dataset contains expansion factors that are used to expand the attributes to State wide aggregation. More information regarding the Sample dataset is contained in the HPMS Field Manual. The Mid-America contains data for the following States: Illinois, Indiana, Iowa, Kansas, Michigan, Minnesota, Missouri, Nebraska, North Dakota, Oklahoma, South Dakota, Texas, and Wisconsin
Highway-Rail Grade Crossing Incident Data (Form 57)

All impacts between railroad on-track equipment and highway users at a highway-rail grade crossing are reported by railroads to the FRA on Form FRA F 6180.57 Highway-Rail Grade Crossing Accident/Incident Report. 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/Form57-Source-Table/icqf-xf4w. The data dictionary can be found here: https://data.transportation.gov/api/views/7wn6-i5b9/files/009f2989-72b7-486c-8a3b-539df5e3d9c8?download=true&filename=Form57_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/.
Highway-Rail Grade Crossing Accident/Incident Source Data (Form 57)

All impacts between railroad on-track equipment and highway users at a highway-rail grade crossing are reported by railroads to the FRA on Form FRA F 6180.57 Highway-Rail Grade Crossing Accident/Incident Report. This dataset is the source dataset and contains raw data values. It replaced the legacy data download (https://safetydata.fra.dot.gov/OfficeofSafety/publicsite/on_the_fly_download.aspx). To download data that contains data in a user-friendly human-readable format, please reference https://data.transportation.gov/Railroads/Highway-Rail-Grade-Crossing-Accident-Data/7wn6-i5b9. The data dictionary can be found here: https://datahub.transportation.gov/api/views/icqf-xf4w/files/531a212f-6b94-4403-9876-a6933a1469aa?download=true&filename=gxirfile_EFFECTIVE_060111%20(24).pdf. 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/.
Highway Performance Monitoring System (HPMS)

The Federal Highway Administration (FHWA) has been receiving Highway inventory, usage, condition and performance data from State Departments of Transportation (DOT) since 1978 to support the program mission of the FHWA. Specifically, HPMS consists of detailed road segment data (63 Attributes) for higher order systems. Sample attributes for collector systems and summary data for the local roads. New requirements for HPMS took effect in 2014 that required each State DOTs to expand their Linear Referencing Systems (LRS), a statewide geospatial representation of their road system that includes all public roads. This requirement was put in place to support highway safety. States DOTs submit HPMS data annually to the FHWA following a prescribed format outlined in the Highway Performance Monitoring System Field Manual.
Grade Crossing Inventory System - Highway-Rail Grade Crossing Inventory (Form 71) Field Reference Table

This a reference table for the Grade Crossing Inventory System, which is the application used to submit data for the Highway-Rail Grade Crossing Inventory (Form 71). The data dictionary for GCIS is attached as well. The LookupType column contains the name of the field/column in the source GCIS/Form 71 dataset. The LookupValue column contains the submitted value and the LookupText field is the human-readable text description of that value (e.g. for LookupType=TypeXing; LookupValue=3 and LookupText=Public, which designates that a crossing is public). This reference table can be used for the Crossing Inventory Source Data Form 71 – Current: https://datahub.transportation.gov/dataset/Crossing-Inventory-Source-Data-Form-71-Current/xp92-5xme.
Geospatial Transportation Typology

This dataset includes the inputs and results for developing a transportation geo-typology that categorizes every location in the United States in terms of their main drivers of transportation demand and supply. It provides the raw inputs to the census tract level microtypes and county or CBSA level geotypes as well as the final typology labels at both the tract (microtype) and county/CBSA (geotype) levels. Inputs include information on the street network, economic characteristics, topography, commute patterns, and land use. The methodology is published in "Popovich, N., Spurlock, C. A., Needell, Z., Jin, L., Wenzel, T., Sheppard, C., & Asudegi, M. (2021). A methodology to develop a geospatial transportation typology. Journal of transport geography, 93, 103061".
General Transit Feed Specification Weblinks

As of Report Year (RY) 2023, FTA requires that reporters with fixed route modes create and maintain a public domain general transit feed specification (GTFS) dataset that reflects their fixed route service. This specification allows for the mapping and other geospatial data visualization and analyses of key transit elements such as stops, routes, and trips. At least one GTFS weblink is provided by the transit agency for each fixed route bus mode and type of service. These include all Rail modes as well as Bus, Bus Rapid Transit, Commuter Bus, Ferryboat and Trolleybus. GTFS requires that an overarching compressed file contain, at a minimum, seven underlying text files: (a) Agency; (b) Stops; (c) Routes; (d) Trips; (e) Stop Times; (f) Calendar or Calendar Dates.txt; and (g) Feed Info.txt. An eighth file, Shapes.txt, is an optional file. FTA collects and publishes these links for further analysis using related GTFS files. FTA is not responsible for managing the websites that host these files, and users with questions regarding the GTFS data are encouraged to contact the transit agency. In many cases, publicly hosted weblinks could not be provided (i.e., due to constraints within the transit agency), but the agency was able to produce a zip file of the required GTFS data. Demand Response, Vanpool, and other non-fixed route modes are excluded. The column "Alternate Format" indicates that the agency provided FTA a weblink in an alternate format with some justification for doing so. The file "Waived" indicates that no GTFS files were produced and FTA granted the agency a waiver from the requirement in Report Year 2024. Note: if the Validated Date is earlier than the Modified Date for a specific row, then the weblink has not yet been reviewed. If you encounter issues with a weblink that has been validated, please contact NTDHelp@dot.gov, as this may indicate an error with the host website. Some URLs may require an API key to access the GTFS feed. In those instances, navigate to the root URL to find information on how to get an API key from the data provider. If you have any other questions about this table, please contact the NTD Help Desk at NTDHelp@dot.gov.
FRA Regulated Mode Major Security 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.