GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-19T16:54:21Z,
for the dataset file:///shared/londontransit_6216f195.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
London Transit
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2026-06-28
Feed End Date:
2026-09-05

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. feed_info.txt
  5. routes.txt
  6. shapes.txt
  7. stop_times.txt
  8. stops.txt
  9. transfers.txt
  10. trips.txt

Counts

  • Agencies: 1
  • Blocks: 459
  • Routes: 34
  • Shapes: 184
  • Stops: 1938
  • Trips: 8602

Specification Compliance report

11 notices reported (0 errors, 8 warnings, 3 infos)

Notice Code Severity Total
missing_feed_contact_email_and_url WARNING 1

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2
mixed_case_recommended_field WARNING 2

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.
"stops.txt" "stop_name" "COMMISSIONERS & WHARNCLIF - #2312" 1494
"stops.txt" "stop_name" "STACKHOUSE at FANSHAWE NB - #2910" 1874
service_has_no_active_day_of_the_week WARNING 4

service_has_no_active_day_of_the_week

A service is not valid for any day of the week.

You can see more about this notice here.

csvRowNumber (?) The row number in calendar.txt where the error occurs. serviceId (?) The service_id field value.
5 "30"
6 "11202"
7 "11203"
8 "11204"
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.
"20260619" "20260629" "20260904"
big_gap_in_service INFO 1

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.
"30" "2026-07-01" "2026-08-03" 32
future_calendar INFO 1

future_calendar

All services in the feed start in the future; no service covers today's date.

You can see more about this notice here.

minServiceStartDate (?) The earliest service start date across all services in the feed. currentDate (?) Today's date at validation time.
"2026-06-28" "2026-06-19"
future_feed INFO 1

future_feed

The feed covers the future only.

The minimum start_date in feed_info.txt is greater than today's date, indicating the feed covers the future only.

You can see more about this notice here.

feedStartDate (?) Feed start date. currentDate (?) Current date.
"20260628" "20260619"