GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T15:01:43Z,
for the dataset file:///shared/business-council.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Trillium Solutions, Inc.
Feed Email:
support+123bc-ma-us@trilliumtransit.com
Feed Language:
English
Feed Start Date:
2017-10-23
Feed End Date:
2019-01-01

Files included

  1. agency.txt
  2. areas.txt
  3. calendar.txt
  4. calendar_attributes.txt
  5. calendar_dates.txt
  6. directions.txt
  7. fare_attributes.txt
  8. fare_rider_categories.txt
  9. fare_rules.txt
  10. farezone_attributes.txt
  11. feed_info.txt
  12. frequencies.txt
  13. rider_categories.txt
  14. routes.txt
  15. shapes.txt
  16. stop_attributes.txt
  17. stop_times.txt
  18. stops.txt
  19. timetable_stop_order-new.txt
  20. timetables-new.txt
  21. transfers.txt
  22. trips.txt

Counts

  • Agencies: 1
  • Blocks: 21
  • Routes: 9
  • Shapes: 44
  • Stops: 64
  • Trips: 74

Specification Compliance report

34 notices reported (2 errors, 13 warnings, 19 infos)

Notice Code Severity Total
missing_required_column ERROR 2

missing_required_column

A required column is missing in the input file.

You can see more about this notice here.

filename (?) The name of the faulty file. fieldName (?) The name of the missing column.
"rider_categories.txt" "is_default_fare_category"
"rider_categories.txt" "rider_category_name"
equal_shape_distance_same_coordinates WARNING 10

equal_shape_distance_same_coordinates

Two consecutive points have equal shape_dist_traveled and the same lat/lon coordinates in shapes.txt.

When sorted by shape.shape_pt_sequence, the values for shape_dist_traveled must increase along a shape. Two consecutive points with equal values for shape_dist_traveled and the same coordinates indicate a duplicative shape point.

You can see more about this notice here.

shapeId (?) The id of the faulty shape. csvRowNumber (?) The row number from `shapes.txt`. shapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the faulty record. shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`. prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point. prevShapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the previous shape point. prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`.
"p_8026" 19943 26592.29034633 621 19942 26592.29034633 620
"p_8029" 21858 24674.09646687 484 21857 24674.09646687 483
"p_8028" 21235 27888.65170772 662 21234 27888.65170772 661
"p_6755" 7608 9589.07107678 172 7607 9589.07107678 171
"p_8032" 23792 30686.71628588 816 23791 30686.71628588 815
"p_8036" 27068 9151.12510571 484 27067 9151.12510571 483
"p_8034" 25965 32873.28088597 1057 25964 32873.28088597 1056
"p_6753" 6119 9589.07107678 172 6118 9589.07107678 171
"p_6754" 6932 9589.07107678 172 6931 9589.07107678 171
"p_6752" 5618 9589.07107678 172 5617 9589.07107678 171
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 "c_1725_b_642_d_31"
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 "20260123" "20190101" "20260130"
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.
"20260123" "20151102" "20181231"
unknown_column INFO 12

unknown_column

A column name is unknown.

You can see more about this notice here.

filename (?) The name of the faulty file. fieldName (?) The name of the unknown column. index (?) The index of the faulty column.
"calendar.txt" "service_name" 2
"feed_info.txt" "feed_license" 5
"areas.txt" "wkt" 2
"calendar_dates.txt" "holiday_name" 3
"rider_categories.txt" "rider_category_description" 2
"stops.txt" "position" 13
"stops.txt" "direction" 14
"routes.txt" "min_headway_minutes" 11
"trips.txt" "trip_type" 11
"stop_times.txt" "continuous_stops" 11
"stop_times.txt" "area_id" 12
"stop_times.txt" "service_area_radius" 13
unknown_file INFO 7

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"farezone_attributes.txt"
"fare_rider_categories.txt"
"calendar_attributes.txt"
"timetables-new.txt"
"directions.txt"
"stop_attributes.txt"
"timetable_stop_order-new.txt"