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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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 3.0.

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 3.0.

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 3.0.

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 3.0.

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 3.0.

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 3.0.

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 3.0.

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 3.0.

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 3.0.

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 3.0.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Beginning in 2023, certain agencies are required to submit one week of service data on a monthly basis to comply with FTA’s Weekly Reference reporting requirement on form WE-20. This data release will therefore present the limited set of key indicators reported by transit agencies on this form and will be updated each month with the most current data. The resulting dataset provides data users with data shortly after the transit service was provided and consumed, over one month in advance of FTA’s routine update to the Monthly Ridership Time Series dataset. One use of this data is for reference in understanding ridership patterns (e.g., to develop to a full month estimate ahead of when the data reflecting the given month of service is released by FTA at the end of the following month). Generally, FTA has defined the reference week to be the second or third full week of the month. All sampled agencies will report data referencing the same reference week. The form collects the following service data points, as described in the metadata below: • Weekday 5-day UPT total for the reference week; • Weekday 5-day VRM total for the reference week; • Weekend 2-day UPT total for either the weekend preceding or following the reference week; and • Weekend 2-day VRM total for either the weekend preceding or following the reference week. • Vehicles Operated in Maximum Service (vanpool mode only) for the reference week. FTA has also derived the change from the prior month for the same agency/mode/type of service/data point. Users should take caution when aggregating this measure and are encouraged to use the dataset export to measure service trends at a higher level (i.e., by reporter or nationally). For any questions regarding this dataset, please contact the NTD helpdesk at ntdhelp@dot.gov .

Beginning in 2023, certain agencies are required to submit one week of service data on a monthly basis to comply with FTA’s Weekly Reference reporting requirement on form WE-20. This data release will therefore present the limited set of key indicators reported by transit agencies on this form and will be updated each month with the most current data. The resulting dataset provides data users with data shortly after the transit service was provided and consumed, over one month in advance of FTA’s routine update to the Monthly Ridership Time Series dataset. One use of this data is for reference in understanding ridership patterns (e.g., to develop to a full month estimate ahead of when the data reflecting the given month of service is released by FTA at the end of the following month). Generally, FTA has defined the reference week to be the second or third full week of the month. All sampled agencies will report data referencing the same reference week. The form collects the following service data points, as described in the metadata below: • Weekday 5-day UPT total for the reference week; • Weekday 5-day VRM total for the reference week; • Weekend 2-day UPT total for either the weekend preceding or following the reference week; and • Weekend 2-day VRM total for either the weekend preceding or following the reference week. • Vehicles Operated in Maximum Service (vanpool mode only) for the reference week. FTA has also derived the change from the prior month for the same agency/mode/type of service/data point. Users should take caution when aggregating this measure and are encouraged to use the dataset export to measure service trends at a higher level (i.e., by reporter or nationally). For any questions regarding this dataset, please contact the NTD helpdesk at ntdhelp@dot.gov .

Beginning in 2023, certain agencies are required to submit one week of service data on a monthly basis to comply with FTA’s Weekly Reference reporting requirement on form WE-20. This data release will therefore present the limited set of key indicators reported by transit agencies on this form and will be updated each month with the most current data. The resulting dataset provides data users with data shortly after the transit service was provided and consumed, over one month in advance of FTA’s routine update to the Monthly Ridership Time Series dataset. One use of this data is for reference in understanding ridership patterns (e.g., to develop to a full month estimate ahead of when the data reflecting the given month of service is released by FTA at the end of the following month). Generally, FTA has defined the reference week to be the second or third full week of the month. All sampled agencies will report data referencing the same reference week. The form collects the following service data points, as described in the metadata below: • Weekday 5-day UPT total for the reference week; • Weekday 5-day VRM total for the reference week; • Weekend 2-day UPT total for either the weekend preceding or following the reference week; and • Weekend 2-day VRM total for either the weekend preceding or following the reference week. • Vehicles Operated in Maximum Service (vanpool mode only) for the reference week. FTA has also derived the change from the prior month for the same agency/mode/type of service/data point. Users should take caution when aggregating this measure and are encouraged to use the dataset export to measure service trends at a higher level (i.e., by reporter or nationally). For any questions regarding this dataset, please contact the NTD helpdesk at ntdhelp@dot.gov .

Beginning in 2023, certain agencies are required to submit one week of service data on a monthly basis to comply with FTA’s Weekly Reference reporting requirement on form WE-20. This data release will therefore present the limited set of key indicators reported by transit agencies on this form and will be updated each month with the most current data. The resulting dataset provides data users with data shortly after the transit service was provided and consumed, over one month in advance of FTA’s routine update to the Monthly Ridership Time Series dataset. One use of this data is for reference in understanding ridership patterns (e.g., to develop to a full month estimate ahead of when the data reflecting the given month of service is released by FTA at the end of the following month). Generally, FTA has defined the reference week to be the second or third full week of the month. All sampled agencies will report data referencing the same reference week. The form collects the following service data points, as described in the metadata below: • Weekday 5-day UPT total for the reference week; • Weekday 5-day VRM total for the reference week; • Weekend 2-day UPT total for either the weekend preceding or following the reference week; and • Weekend 2-day VRM total for either the weekend preceding or following the reference week. • Vehicles Operated in Maximum Service (vanpool mode only) for the reference week. FTA has also derived the change from the prior month for the same agency/mode/type of service/data point. Users should take caution when aggregating this measure and are encouraged to use the dataset export to measure service trends at a higher level (i.e., by reporter or nationally). For any questions regarding this dataset, please contact the NTD helpdesk at ntdhelp@dot.gov .

Beginning in 2023, certain agencies are required to submit one week of service data on a monthly basis to comply with FTA’s Weekly Reference reporting requirement on form WE-20. This data release will therefore present the limited set of key indicators reported by transit agencies on this form and will be updated each month with the most current data. The resulting dataset provides data users with data shortly after the transit service was provided and consumed, over one month in advance of FTA’s routine update to the Monthly Ridership Time Series dataset. One use of this data is for reference in understanding ridership patterns (e.g., to develop to a full month estimate ahead of when the data reflecting the given month of service is released by FTA at the end of the following month). Generally, FTA has defined the reference week to be the second or third full week of the month. All sampled agencies will report data referencing the same reference week. The form collects the following service data points, as described in the metadata below: • Weekday 5-day UPT total for the reference week; • Weekday 5-day VRM total for the reference week; • Weekend 2-day UPT total for either the weekend preceding or following the reference week; and • Weekend 2-day VRM total for either the weekend preceding or following the reference week. • Vehicles Operated in Maximum Service (vanpool mode only) for the reference week. FTA has also derived the change from the prior month for the same agency/mode/type of service/data point. Users should take caution when aggregating this measure and are encouraged to use the dataset export to measure service trends at a higher level (i.e., by reporter or nationally). For any questions regarding this dataset, please contact the NTD helpdesk at ntdhelp@dot.gov .

Beginning in 2023, certain agencies are required to submit one week of service data on a monthly basis to comply with FTA’s Weekly Reference reporting requirement on form WE-20. This data release will therefore present the limited set of key indicators reported by transit agencies on this form and will be updated each month with the most current data. The resulting dataset provides data users with data shortly after the transit service was provided and consumed, over one month in advance of FTA’s routine update to the Monthly Ridership Time Series dataset. One use of this data is for reference in understanding ridership patterns (e.g., to develop to a full month estimate ahead of when the data reflecting the given month of service is released by FTA at the end of the following month). Generally, FTA has defined the reference week to be the second or third full week of the month. All sampled agencies will report data referencing the same reference week. The form collects the following service data points, as described in the metadata below: • Weekday 5-day UPT total for the reference week; • Weekday 5-day VRM total for the reference week; • Weekend 2-day UPT total for either the weekend preceding or following the reference week; and • Weekend 2-day VRM total for either the weekend preceding or following the reference week. • Vehicles Operated in Maximum Service (vanpool mode only) for the reference week. FTA has also derived the change from the prior month for the same agency/mode/type of service/data point. Users should take caution when aggregating this measure and are encouraged to use the dataset export to measure service trends at a higher level (i.e., by reporter or nationally). For any questions regarding this dataset, please contact the NTD helpdesk at ntdhelp@dot.gov .

Beginning in 2023, certain agencies are required to submit one week of service data on a monthly basis to comply with FTA’s Weekly Reference reporting requirement on form WE-20. This data release will therefore present the limited set of key indicators reported by transit agencies on this form and will be updated each month with the most current data. The resulting dataset provides data users with data shortly after the transit service was provided and consumed, over one month in advance of FTA’s routine update to the Monthly Ridership Time Series dataset. One use of this data is for reference in understanding ridership patterns (e.g., to develop to a full month estimate ahead of when the data reflecting the given month of service is released by FTA at the end of the following month). Generally, FTA has defined the reference week to be the second or third full week of the month. All sampled agencies will report data referencing the same reference week. The form collects the following service data points, as described in the metadata below: • Weekday 5-day UPT total for the reference week; • Weekday 5-day VRM total for the reference week; • Weekend 2-day UPT total for either the weekend preceding or following the reference week; and • Weekend 2-day VRM total for either the weekend preceding or following the reference week. • Vehicles Operated in Maximum Service (vanpool mode only) for the reference week. FTA has also derived the change from the prior month for the same agency/mode/type of service/data point. Users should take caution when aggregating this measure and are encouraged to use the dataset export to measure service trends at a higher level (i.e., by reporter or nationally). For any questions regarding this dataset, please contact the NTD helpdesk at ntdhelp@dot.gov .

Beginning in 2023, certain agencies are required to submit one week of service data on a monthly basis to comply with FTA’s Weekly Reference reporting requirement on form WE-20. This data release will therefore present the limited set of key indicators reported by transit agencies on this form and will be updated each month with the most current data. The resulting dataset provides data users with data shortly after the transit service was provided and consumed, over one month in advance of FTA’s routine update to the Monthly Ridership Time Series dataset. One use of this data is for reference in understanding ridership patterns (e.g., to develop to a full month estimate ahead of when the data reflecting the given month of service is released by FTA at the end of the following month). Generally, FTA has defined the reference week to be the second or third full week of the month. All sampled agencies will report data referencing the same reference week. The form collects the following service data points, as described in the metadata below: • Weekday 5-day UPT total for the reference week; • Weekday 5-day VRM total for the reference week; • Weekend 2-day UPT total for either the weekend preceding or following the reference week; and • Weekend 2-day VRM total for either the weekend preceding or following the reference week. • Vehicles Operated in Maximum Service (vanpool mode only) for the reference week. FTA has also derived the change from the prior month for the same agency/mode/type of service/data point. Users should take caution when aggregating this measure and are encouraged to use the dataset export to measure service trends at a higher level (i.e., by reporter or nationally). For any questions regarding this dataset, please contact the NTD helpdesk at ntdhelp@dot.gov .

Beginning in 2023, certain agencies are required to submit one week of service data on a monthly basis to comply with FTA’s Weekly Reference reporting requirement on form WE-20. This data release will therefore present the limited set of key indicators reported by transit agencies on this form and will be updated each month with the most current data. The resulting dataset provides data users with data shortly after the transit service was provided and consumed, over one month in advance of FTA’s routine update to the Monthly Ridership Time Series dataset. One use of this data is for reference in understanding ridership patterns (e.g., to develop to a full month estimate ahead of when the data reflecting the given month of service is released by FTA at the end of the following month). Generally, FTA has defined the reference week to be the second or third full week of the month. All sampled agencies will report data referencing the same reference week. The form collects the following service data points, as described in the metadata below: • Weekday 5-day UPT total for the reference week; • Weekday 5-day VRM total for the reference week; • Weekend 2-day UPT total for either the weekend preceding or following the reference week; and • Weekend 2-day VRM total for either the weekend preceding or following the reference week. • Vehicles Operated in Maximum Service (vanpool mode only) for the reference week. FTA has also derived the change from the prior month for the same agency/mode/type of service/data point. Users should take caution when aggregating this measure and are encouraged to use the dataset export to measure service trends at a higher level (i.e., by reporter or nationally). For any questions regarding this dataset, please contact the NTD helpdesk at ntdhelp@dot.gov .

Beginning in 2023, certain agencies are required to submit one week of service data on a monthly basis to comply with FTA’s Weekly Reference reporting requirement on form WE-20. This data release will therefore present the limited set of key indicators reported by transit agencies on this form and will be updated each month with the most current data. The resulting dataset provides data users with data shortly after the transit service was provided and consumed, over one month in advance of FTA’s routine update to the Monthly Ridership Time Series dataset. One use of this data is for reference in understanding ridership patterns (e.g., to develop to a full month estimate ahead of when the data reflecting the given month of service is released by FTA at the end of the following month). Generally, FTA has defined the reference week to be the second or third full week of the month. All sampled agencies will report data referencing the same reference week. The form collects the following service data points, as described in the metadata below: • Weekday 5-day UPT total for the reference week; • Weekday 5-day VRM total for the reference week; • Weekend 2-day UPT total for either the weekend preceding or following the reference week; and • Weekend 2-day VRM total for either the weekend preceding or following the reference week. • Vehicles Operated in Maximum Service (vanpool mode only) for the reference week. FTA has also derived the change from the prior month for the same agency/mode/type of service/data point. Users should take caution when aggregating this measure and are encouraged to use the dataset export to measure service trends at a higher level (i.e., by reporter or nationally). For any questions regarding this dataset, please contact the NTD helpdesk at ntdhelp@dot.gov .

This dataset contains the up-to-date metadata on Work Zone feeds that meet the Work Zone Data Exchange (WZDx) specifications and is registered with USDOT ITS DataHub. The current work zone data from each feed can be accessed through their respective API links. Some links provide direct access, while others require a user to create their own API access key first. Please see the attached API Key Instructions document to learn how to sign up for API keys for the requisite feeds. The ITS Work Zone Sandbox, contains an archive of work zone data collected from each feed at a rate of at least every 15 minutes. This is not intended as a replacement for the work zone feeds and in many cases does not update as frequently as the feed does.

This dataset contains the up-to-date metadata on Work Zone feeds that meet the Work Zone Data Exchange (WZDx) specifications and is registered with USDOT ITS DataHub. The current work zone data from each feed can be accessed through their respective API links. Some links provide direct access, while others require a user to create their own API access key first. Please see the attached API Key Instructions document to learn how to sign up for API keys for the requisite feeds. The ITS Work Zone Sandbox, contains an archive of work zone data collected from each feed at a rate of at least every 15 minutes. This is not intended as a replacement for the work zone feeds and in many cases does not update as frequently as the feed does.

This dataset contains the up-to-date metadata on Work Zone feeds that meet the Work Zone Data Exchange (WZDx) specifications and is registered with USDOT ITS DataHub. The current work zone data from each feed can be accessed through their respective API links. Some links provide direct access, while others require a user to create their own API access key first. Please see the attached API Key Instructions document to learn how to sign up for API keys for the requisite feeds. The ITS Work Zone Sandbox, contains an archive of work zone data collected from each feed at a rate of at least every 15 minutes. This is not intended as a replacement for the work zone feeds and in many cases does not update as frequently as the feed does.

This dataset contains the up-to-date metadata on Work Zone feeds that meet the Work Zone Data Exchange (WZDx) specifications and is registered with USDOT ITS DataHub. The current work zone data from each feed can be accessed through their respective API links. Some links provide direct access, while others require a user to create their own API access key first. Please see the attached API Key Instructions document to learn how to sign up for API keys for the requisite feeds. The ITS Work Zone Sandbox, contains an archive of work zone data collected from each feed at a rate of at least every 15 minutes. This is not intended as a replacement for the work zone feeds and in many cases does not update as frequently as the feed does.

This dataset contains the up-to-date metadata on Work Zone feeds that meet the Work Zone Data Exchange (WZDx) specifications and is registered with USDOT ITS DataHub. The current work zone data from each feed can be accessed through their respective API links. Some links provide direct access, while others require a user to create their own API access key first. Please see the attached API Key Instructions document to learn how to sign up for API keys for the requisite feeds. The ITS Work Zone Sandbox, contains an archive of work zone data collected from each feed at a rate of at least every 15 minutes. This is not intended as a replacement for the work zone feeds and in many cases does not update as frequently as the feed does.

This dataset contains the up-to-date metadata on Work Zone feeds that meet the Work Zone Data Exchange (WZDx) specifications and is registered with USDOT ITS DataHub. The current work zone data from each feed can be accessed through their respective API links. Some links provide direct access, while others require a user to create their own API access key first. Please see the attached API Key Instructions document to learn how to sign up for API keys for the requisite feeds. The ITS Work Zone Sandbox, contains an archive of work zone data collected from each feed at a rate of at least every 15 minutes. This is not intended as a replacement for the work zone feeds and in many cases does not update as frequently as the feed does.

This dataset contains the up-to-date metadata on Work Zone feeds that meet the Work Zone Data Exchange (WZDx) specifications and is registered with USDOT ITS DataHub. The current work zone data from each feed can be accessed through their respective API links. Some links provide direct access, while others require a user to create their own API access key first. Please see the attached API Key Instructions document to learn how to sign up for API keys for the requisite feeds. The ITS Work Zone Sandbox, contains an archive of work zone data collected from each feed at a rate of at least every 15 minutes. This is not intended as a replacement for the work zone feeds and in many cases does not update as frequently as the feed does.

This dataset contains the up-to-date metadata on Work Zone feeds that meet the Work Zone Data Exchange (WZDx) specifications and is registered with USDOT ITS DataHub. The current work zone data from each feed can be accessed through their respective API links. Some links provide direct access, while others require a user to create their own API access key first. Please see the attached API Key Instructions document to learn how to sign up for API keys for the requisite feeds. The ITS Work Zone Sandbox, contains an archive of work zone data collected from each feed at a rate of at least every 15 minutes. This is not intended as a replacement for the work zone feeds and in many cases does not update as frequently as the feed does.

This dataset contains the up-to-date metadata on Work Zone feeds that meet the Work Zone Data Exchange (WZDx) specifications and is registered with USDOT ITS DataHub. The current work zone data from each feed can be accessed through their respective API links. Some links provide direct access, while others require a user to create their own API access key first. Please see the attached API Key Instructions document to learn how to sign up for API keys for the requisite feeds. The ITS Work Zone Sandbox, contains an archive of work zone data collected from each feed at a rate of at least every 15 minutes. This is not intended as a replacement for the work zone feeds and in many cases does not update as frequently as the feed does.

This dataset contains the up-to-date metadata on Work Zone feeds that meet the Work Zone Data Exchange (WZDx) specifications and is registered with USDOT ITS DataHub. The current work zone data from each feed can be accessed through their respective API links. Some links provide direct access, while others require a user to create their own API access key first. Please see the attached API Key Instructions document to learn how to sign up for API keys for the requisite feeds. The ITS Work Zone Sandbox, contains an archive of work zone data collected from each feed at a rate of at least every 15 minutes. This is not intended as a replacement for the work zone feeds and in many cases does not update as frequently as the feed does.