broward-county-transit-usa — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-22T17:48:06Z,
for the dataset file:///shared/broward-county-transit-usa_e9988eb2.zip. No country code was provided.

Use this report alongside our documentation.

A new version of the Canonical GTFS Schedule validator is available! Please update to get the latest/best validation results.

Summary

Agencies included

Broward County Transit
- website: http://www.broward.org/bct/Pages/default.aspx
- phone number: 954-357-8400
- email: Not provided

Feed Info

Publisher Name:
Broward County Transit: Publisher URL:
http://www.broward.org/bct/Pages/default.aspx: Feed Email:
bctgtfsfeed@broward.org: Feed Language:
English: Feed Start Date:
2023-10-02: Feed End Date:
2024-09-30: Service Window:
2023-10-02 to 2024-09-30 (?) The range of service dates covered by the feed, based on trips with an associated service_id in calendar.txt and/or calendar_dates.txt

Files included

agency.txt
calendar.txt
calendar_dates.txt
feed_info.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 7
Routes: 7
Shapes: 7
Stops: 197
Trips: 95

GTFS Features included (?) GTFS features provide a standardized vocabulary to define and describe features that are officially adopted in GTFS.

ShapesFeed InformationHeadsignsStops Wheelchair AccessibilityLocation Types

Specification Compliance report

4 notices reported (1 errors, 3 warnings, 0 infos)

Notice Code Severity Total

invalid_input_files_in_subfolder ERROR 1

invalid_input_files_in_subfolder

At least 1 GTFS file is in a subfolder.

All GTFS files must reside at the root level directly. There are two common cases that trigger this error:

The root folder (e.g., a folder called "GTFS 2020") was zipped instead of the individual files within the folder (e.g., calendar.txt, agency.txt, etc.). This can be fixed by zipping the files directly instead.
A file associated with GTFS is in a subfolder rather than the root folder of the dataset, and needs to be removed if not needed or moved to the root level.

You can see more about this notice here.

expired_calendar WARNING 1

expired_calendar

Dataset should not contain date ranges for services that have already expired.

This warning takes into account the calendar_dates.txt file as well as the calendar.txt file.

You can see more about this notice here.

csvRowNumber (?) The row of the faulty record.	serviceId (?) The service id of the faulty record.
2	"CB2024_muwtf"

feed_expiration_date7_days WARNING 1

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	currentDate (?) Current date (YYYYMMDD format).	feedEndDate (?) Feed end date (YYYYMMDD format).	suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2	"20260522"	"20240930"	"20260529"

trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format).	serviceWindowStartDate (?) The start date of the majority service window.	serviceWindowEndDate (?) The end date of the majority service window.
"20260522"	"20231002"	"20240930"