GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T19:41:34Z,
for the dataset file:///shared/kigali-rwanda-wet.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
N/A
Publisher URL:
N/A
Feed Email:
N/A
Feed Language:
N/A

Files included

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

Counts

  • Agencies: 3
  • Blocks: 0
  • Routes: 50
  • Shapes: 99
  • Stops: 1112
  • Trips: 99

Specification Compliance report

166 notices reported (12 errors, 154 warnings, 0 infos)

Notice Code Severity Total
foreign_key_violation ERROR 12

foreign_key_violation

Wrong foreign key.

A foreign key references the primary key of another file. A foreign key violation means that the foreign key referenced from a given row (the child file) cannot be found in the corresponding file (the parent file). The Foreign keys are defined in the specification under "Type" for each file.

You can see more about this notice here.

childFilename (?) The name of the file from which reference is made. childFieldName (?) The name of the field that makes reference. parentFilename (?) The name of the file that is referred to. parentFieldName (?) The name of the field that is referred to. fieldValue (?) The faulty record's value. csvRowNumber (?) The row of the faulty record.
"fare_rules.txt" "route_id" "routes.txt" "route_id" "110" 12
"fare_rules.txt" "route_id" "routes.txt" "route_id" "120" 17
"fare_rules.txt" "route_id" "routes.txt" "route_id" "121" 18
"fare_rules.txt" "route_id" "routes.txt" "route_id" "122" 19
"fare_rules.txt" "route_id" "routes.txt" "route_id" "204" 22
"fare_rules.txt" "route_id" "routes.txt" "route_id" "207" 26
"fare_rules.txt" "route_id" "routes.txt" "route_id" "210" 28
"fare_rules.txt" "route_id" "routes.txt" "route_id" "307" 45
"fare_rules.txt" "route_id" "routes.txt" "route_id" "405" 47
"fare_rules.txt" "route_id" "routes.txt" "route_id" "323" 54
"fare_rules.txt" "route_id" "routes.txt" "route_id" "414" 62
"fare_rules.txt" "route_id" "routes.txt" "route_id" "407" 63
expired_calendar WARNING 2

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 "0"
3 "1"
missing_recommended_file WARNING 1

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"
mixed_case_recommended_field WARNING 148

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.

Only the first 50 of 148 affected records are displayed below.

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" "CHUK DOWN" 2
"stops.txt" "stop_name" "kicukiro centre" 8
"stops.txt" "stop_name" "ku isoko taxi stop" 17
"stops.txt" "stop_name" "sonatubes stop" 31
"stops.txt" "stop_name" "segiteri" 38
"stops.txt" "stop_name" "prince house" 41
"stops.txt" "stop_name" "sonatube" 42
"stops.txt" "stop_name" "reandex" 43
"stops.txt" "stop_name" "camp zaire" 44
"stops.txt" "stop_name" "payage" 45
"stops.txt" "stop_name" "kwa rubangura" 47
"stops.txt" "stop_name" "downtown gare" 48
"stops.txt" "stop_name" "victory" 69
"stops.txt" "stop_name" "masaka" 97
"stops.txt" "stop_name" "sonatube" 102
"stops.txt" "stop_name" "princehouse" 111
"stops.txt" "stop_name" "mushumbamwiza" 122
"stops.txt" "stop_name" "remera park" 123
"stops.txt" "stop_name" "sonatube" 124
"stops.txt" "stop_name" "rwandex" 125
"stops.txt" "stop_name" "nyabugogo park" 127
"stops.txt" "stop_name" "remera park" 128
"stops.txt" "stop_name" "chez rando" 129
"stops.txt" "stop_name" "kugishushu" 130
"stops.txt" "stop_name" "kimihurura" 131
"stops.txt" "stop_name" "king faisal" 132
"stops.txt" "stop_name" "minagri" 133
"stops.txt" "stop_name" "kacyuru gar" 134
"stops.txt" "stop_name" "kuri police" 135
"stops.txt" "stop_name" "kukinamba" 137
"stops.txt" "stop_name" "kwamirimo" 138
"stops.txt" "stop_name" "nyabugogo park" 139
"stops.txt" "stop_name" "nyabugogo park" 140
"stops.txt" "stop_name" "kukinamba" 143
"stops.txt" "stop_name" "kugisozi" 144
"stops.txt" "stop_name" "kacyuru park" 145
"stops.txt" "stop_name" "minagri" 146
"stops.txt" "stop_name" "gisimeti" 148
"stops.txt" "stop_name" "the mirror hotel" 149
"stops.txt" "stop_name" "remera park" 150
"stops.txt" "stop_name" "kinamba" 151
"stops.txt" "stop_name" "kwa mironko" 153
"stops.txt" "stop_name" "rwandex" 154
"stops.txt" "stop_name" "kuri chelle" 156
"stops.txt" "stop_name" "sonatube" 157
"stops.txt" "stop_name" "nyabugogo park" 160
"stops.txt" "stop_name" "kicukiro centre" 200
"stops.txt" "stop_name" "segiteri" 203
"stops.txt" "stop_name" "gasaraba" 204
"stops.txt" "stop_name" "airport" 206
stop_too_far_from_shape WARNING 2

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
79 "30460935" "30460935" 916 "30459523" "nyabugogo park to kanyinya" [-1.940592,30.043729000000006] 115.80522647922345
30 "30625986" "30625986" 346 "100016424" "ka Kigali" [-1.9497850000000003,30.125505] 106.88926423926401
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" "20201120" "20211210"