hills-ata-bus — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-20T01:55:35Z,
for the dataset file:///shared/hills-ata-bus_4bf4553c.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
Flint Hills ATA
Publisher URL:
https://www.fhata.org/
Feed Email:
fhata@fhata.org
Feed Language:
English
Feed Start Date:
2026-01-03
Feed End Date:
2027-01-01

Files included


  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. fare_attributes.txt
  5. fare_rules.txt
  6. feed_info.txt
  7. frequencies.txt
  8. routes.txt
  9. shapes.txt
  10. stop_times.txt
  11. stops.txt
  12. transfers.txt
  13. trips.txt

Counts


  • Agencies: 1
  • Blocks: 10
  • Routes: 9
  • Shapes: 17
  • Stops: 184
  • Trips: 207

Specification Compliance report

27 notices reported (0 errors, 19 warnings, 8 infos)

Notice Code Severity Total
missing_recommended_field WARNING 2

missing_recommended_field

A recommended field is missing.

The given field has no value in some input row, even though values are recommended.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) The name of the missing field.
"fare_attributes.txt" 2 "agency_id"
"fare_attributes.txt" 3 "agency_id"
mixed_case_recommended_field WARNING 15

mixed_case_recommended_field

This field has customer-facing text and should use Mixed Case (should contain upper and lower case letters).

This field contains customer-facing text and should use Mixed Case (upper and lower case letters) to ensure good readability when displayed to riders. Avoid the use of abbreviations throughout the feed (e.g. St. for Street) unless a location is called by its abbreviated name (e.g. “JFK Airport”). Abbreviations may be problematic for accessibility by screen reader software and voice user interfaces.

Good examples:
Field Text Dataset
"Schwerin, Hauptbahnhof" Verkehrsverbund Berlin-Brandenburg
"Red Hook/Atlantic Basin" NYC Ferry
"Campo Grande Norte" Carris
Bad examples:
Field Text
"GALLERIA MALL"
"3427 GG 17"
"21 Clark Rd Est"

You can see more about this notice here.

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"trips.txt" "trip_headsign" "MATC(WB)" 118
"trips.txt" "trip_headsign" "MATC(WB)" 119
"trips.txt" "trip_headsign" "MATC(WB)" 120
"trips.txt" "trip_headsign" "MATC(WB)" 121
"trips.txt" "trip_headsign" "MATC(WB)" 122
"trips.txt" "trip_headsign" "MATC(WB)" 123
"trips.txt" "trip_headsign" "MATC(WB)" 124
"trips.txt" "trip_headsign" "MATC(WB)" 125
"trips.txt" "trip_headsign" "MATC(WB)" 132
"trips.txt" "trip_headsign" "MATC(WB)" 133
"trips.txt" "trip_headsign" "MATC(WB)" 134
"trips.txt" "trip_headsign" "MATC(WB)" 135
"trips.txt" "trip_headsign" "MATC(WB)" 136
"trips.txt" "trip_headsign" "MATC(WB)" 137
"trips.txt" "trip_headsign" "MATC(WB)" 138
stop_without_stop_time WARNING 2

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty stop. stopName (?) The name of the faulty stop.
6 "111" "Aldi"
41 "167" "GTM"
big_gap_in_service INFO 2

big_gap_in_service

A service has a gap of more than 13 days between active service dates.

You can see more about this notice here.

serviceId (?) The service_id that has the gap. gapStartDate (?) The first day of the gap. gapEndDate (?) The last day of the gap. gapDurationDays (?) The number of days in the gap.
"k-state" "2026-12-18" "2027-01-18" 30
"JC_highschool" "2026-12-18" "2027-01-04" 16
feed_valid_beyond_total_service_window INFO 1

feed_valid_beyond_total_service_window

The feed is valid 14 days beyond its total service window.

You can see more about this notice here.

feedStartDate (?) The feed start date from feed_info.txt. feedEndDate (?) The feed end date from feed_info.txt. serviceWindowStartDate (?) The earliest active service date across all services. serviceWindowEndDate (?) The latest active service date across all services.
"2026-01-03" "2027-01-01" "2026-06-01" "2028-01-01"
service_window_outside_feed_period INFO 5

service_window_outside_feed_period

A service window is not covered by the feed's validity period.

You can see more about this notice here.

serviceId (?) The service_id whose active window extends outside the feed validity period. serviceWindowStartDate (?) The first active date of the service window. serviceWindowEndDate (?) The last active date of the service window. daysBeforeFeedStart (?) Number of days the service window extends before feed_start_date (0 if none). daysAfterFeedEnd (?) Number of days the service window extends after feed_end_date (0 if none).
"k-state" "2026-08-17" "2027-05-14" 0 133
"sat" "2026-06-06" "2028-01-01" 0 365
"mtwtf" "2026-06-01" "2027-12-31" 0 364
"JC_mtwtf" "2026-06-01" "2027-12-31" 0 364
"JC_highschool" "2026-08-06" "2027-05-21" 0 140