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

kgb-ak-us — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-19T13:03:33Z,
for the dataset file:///shared/kgb-ak-us_fba30973.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+test+kgb-ak-us@trilliumtransit.com
Feed Language:
English
Feed Start Date:
2026-05-12
Feed End Date:
2027-06-30

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_rules.txt
  10. farezone_attributes.txt
  11. feed_info.txt
  12. frequencies.txt
  13. linked_datasets.txt
  14. location_groups.txt
  15. routes.txt
  16. runcut.txt
  17. shapes.txt
  18. stop_attributes.txt
  19. stop_times.txt
  20. stops.txt
  21. timetable_stop_order.txt
  22. timetables.txt
  23. transfers.txt
  24. trips.txt

Counts

  • Agencies: 2
  • Blocks: 6
  • Routes: 4
  • Shapes: 14
  • Stops: 164
  • Trips: 280

Specification Compliance report

95 notices reported (0 errors, 46 warnings, 49 infos)

Notice Code Severity Total
mixed_case_recommended_field WARNING 33

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.
"routes.txt" "route_desc" "CITY LOOP" 2
"routes.txt" "route_desc" "BOROUGH / CITY LOOP" 3
"routes.txt" "route_desc" "FREE SHUTTLE: DOWNTOWN LOOP" 4
"trips.txt" "trip_headsign" "SILVER NORTH" 178
"trips.txt" "trip_headsign" "SILVER NORTH" 191
"trips.txt" "trip_headsign" "SILVER NORTH" 192
"trips.txt" "trip_headsign" "SILVER NORTH" 193
"trips.txt" "trip_headsign" "SILVER NORTH" 194
"trips.txt" "trip_headsign" "SILVER NORTH" 195
"trips.txt" "trip_headsign" "SILVER NORTH" 196
"trips.txt" "trip_headsign" "SILVER NORTH" 197
"trips.txt" "trip_headsign" "SILVER NORTH" 198
"trips.txt" "trip_headsign" "SILVER NORTH" 199
"trips.txt" "trip_headsign" "SILVER NORTH" 200
"trips.txt" "trip_headsign" "SILVER NORTH" 201
"trips.txt" "trip_headsign" "SILVER NORTH" 202
"trips.txt" "trip_headsign" "SILVER NORTH" 203
"trips.txt" "trip_headsign" "SILVER NORTH" 204
"trips.txt" "trip_headsign" "SILVER SOUTH" 205
"trips.txt" "trip_headsign" "SILVER SOUTH" 206
"trips.txt" "trip_headsign" "SILVER SOUTH" 207
"trips.txt" "trip_headsign" "SILVER SOUTH" 208
"trips.txt" "trip_headsign" "SILVER SOUTH" 209
"trips.txt" "trip_headsign" "SILVER SOUTH" 210
"trips.txt" "trip_headsign" "SILVER SOUTH" 211
"trips.txt" "trip_headsign" "SILVER SOUTH" 212
"trips.txt" "trip_headsign" "SILVER SOUTH" 213
"trips.txt" "trip_headsign" "SILVER SOUTH" 214
"trips.txt" "trip_headsign" "SILVER SOUTH" 215
"trips.txt" "trip_headsign" "SILVER SOUTH" 216
"trips.txt" "trip_headsign" "SILVER SOUTH" 217
"trips.txt" "trip_headsign" "SILVER SOUTH" 218
"trips.txt" "trip_headsign" "SILVER SOUTH" 219
route_long_name_contains_short_name WARNING 4

route_long_name_contains_short_name

Long name should not contain short name for a single route.

In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.

Good examples:

route_short_name/route_long_name Dataset
"N"/"Judah" Muni San Fransisco
"6"/"ML King Jr Blvd" Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent" STM Montreal
"1"/"Rangiora/Cashmere" Metro Christchurch

Bad examples:

route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"

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`. routeLongName (?) The faulty record's `route_long_name`.
"4519" 2 "Green Line" "Green Line Loop"
"4520" 3 "Silver Line" "Silver Line"
"4505" 4 "Downtown Shuttle" "Downtown Shuttle"
"4683" 5 "Airport Ferry" "Airport Ferry"
route_short_name_too_long WARNING 2

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`.
"4505" 4 "Downtown Shuttle"
"4683" 5 "Airport Ferry"
same_route_and_agency_url WARNING 1

same_route_and_agency_url

Same routes.route_url and agency.agency_url.

A route should not have the same routes.route_url as a record from agency.txt.

You can see more about this notice here.

routeCsvRowNumber (?) The row number of the faulty record from `routes.txt`. routeId (?) The faulty record's id. agencyName (?) The faulty record's referenced agency name. routeUrl (?) The duplicate URL value agencyCsvRowNumber (?) The row number of the faulty record from `agency.txt`.
5 "4683" "Airport Ferry" "http://www.borough.ketchikan.ak.us/147/Airport-Ferry" 2
stop_without_stop_time WARNING 6

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.
18 "4248588" "Ted Ferry Civic Center"
80 "832015" "North Tongass Hwy/ Across from Ward Cove Post Office"
128 "832063" "Third Avenue Bypass / Rainbird Trail"
129 "832064" "Third Avenue Bypass / Rainbird Trail Parking Lot"
156 "832095" "Washington Ave/ Third Ave"
164 "832105" "North Tongass Hwy/ Across from Alaska State Troopers"
service_extends_far_in_the_future INFO 3

service_extends_far_in_the_future

A service end date is more than 2 years in the future.

You can see more about this notice here.

serviceId (?) The service_id that ends far in the future. serviceWindowEndDate (?) The end date of the service (YYYY-MM-DD format).
"c_70697_b_84575_d_127" "2029-06-30"
"c_70696_b_84563_d_127" "2029-06-30"
"c_2166_b_614_d_127" "2028-06-30"
service_window_outside_feed_period INFO 4

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).
"c_71841_b_86647_d_127" "2026-05-10" "2026-09-26" 2 0
"c_70697_b_84575_d_127" "2025-03-26" "2029-06-30" 412 731
"c_2166_b_614_d_127" "2024-05-08" "2028-06-30" 734 366
"c_70696_b_84563_d_127" "2025-03-26" "2029-06-30" 412 731
unknown_column INFO 34

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.
"agency.txt" "tts_agency_name" 8
"areas.txt" "wkt" 2
"calendar_dates.txt" "holiday_name" 3
"calendar.txt" "service_name" 2
"feed_info.txt" "feed_license" 5
"feed_info.txt" "feed_id" 10
"location_groups.txt" "location_id" 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" "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
unknown_file INFO 8

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"
"farezone_attributes.txt"
"linked_datasets.txt"
"runcut.txt"
"stop_attributes.txt"
"timetable_stop_order.txt"
"timetables.txt"