Search
  1. Home
  2. United States Feeds
  3. coloradoshuttle-co-us
  4. Source Data Validation Report

coloradoshuttle-co-us — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-09T10:34:05Z,
for the dataset file:///shared/coloradoshuttle-co-us_d1555657.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

Feed Info

Publisher Name:
Trillium Solutions, Inc.
Feed Email:
support+test+coloradoshuttle-co-us@trilliumtransit.com
Feed Language:
English
Feed Start Date:
2022-12-09
Feed End Date:
2022-12-31

Files included

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 1
  • Shapes: 2
  • Stops: 6
  • Trips: 48

Specification Compliance report

54 notices reported (2 errors, 6 warnings, 46 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"
expired_calendar WARNING 3

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_21855_b_30717_d_15"
3 "c_21855_b_30717_d_127"
4 "c_21854_b_30716_d_127"
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 "20260509" "20221231" "20260516"
route_short_name_too_long WARNING 1

route_short_name_too_long

Short name of a route is too long (more than 12 characters).

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeShortName (?) The faulty record's `route_short_name`.
"12334" 2 "Groome Transportation"
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.
"20260509" "20210827" "20221231"
unknown_column INFO 37

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.
"areas.txt" "wkt" 2
"agency.txt" "tts_agency_name" 8
"calendar.txt" "service_name" 2
"calendar_dates.txt" "holiday_name" 3
"feed_info.txt" "feed_license" 5
"feed_info.txt" "feed_id" 10
"rider_categories.txt" "rider_category_description" 2
"routes.txt" "min_headway_minutes" 11
"routes.txt" "eligibility_restricted" 12
"routes.txt" "tts_route_short_name" 15
"routes.txt" "tts_route_long_name" 16
"stop_times.txt" "start_service_area_id" 11
"stop_times.txt" "end_service_area_id" 12
"stop_times.txt" "start_service_area_radius" 13
"stop_times.txt" "end_service_area_radius" 14
"stop_times.txt" "start_pickup_dropoff_window" 19
"stop_times.txt" "end_pickup_dropoff_window" 20
"stop_times.txt" "mean_duration_factor" 21
"stop_times.txt" "mean_duration_offset" 22
"stop_times.txt" "safe_duration_factor" 23
"stop_times.txt" "safe_duration_offset" 24
"stop_times.txt" "tts_stop_headsign" 25
"stop_times.txt" "min_arrival_time" 26
"stop_times.txt" "max_departure_time" 27
"stops.txt" "position" 13
"stops.txt" "direction" 14
"trips.txt" "trip_type" 11
"trips.txt" "drt_max_travel_time" 12
"trips.txt" "drt_avg_travel_time" 13
"trips.txt" "drt_advance_book_min" 14
"trips.txt" "drt_pickup_message" 15
"trips.txt" "drt_drop_off_message" 16
"trips.txt" "continuous_pickup_message" 17
"trips.txt" "continuous_drop_off_message" 18
"trips.txt" "tts_trip_headsign" 19
"trips.txt" "tts_trip_short_name" 20
"location_groups.txt" "location_id" 2
unknown_file INFO 9

unknown_file

A file is unknown.

You can see more about this notice here.

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