kigali-rwanda-dry — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-04T12:55:45Z,
for the dataset file:///shared/kigali-rwanda-dry_d7720bde.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: 0
    • Blocks: 0
    • Routes: 55
    • Shapes: 220
    • Stops: 2607
    • Trips: 220

    Specification Compliance report

    518 notices reported (16 errors, 502 warnings, 0 infos)

    Notice Code Severity Total
    foreign_key_violation ERROR 9

    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" "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" "407" 63
    missing_required_field ERROR 6

    missing_required_field

    A required field is missing.

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

    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.
    "agency.txt" 2 "agency_url"
    "agency.txt" 2 "agency_timezone"
    "agency.txt" 3 "agency_url"
    "agency.txt" 3 "agency_timezone"
    "agency.txt" 4 "agency_url"
    "agency.txt" 4 "agency_timezone"
    stop_time_with_arrival_before_previous_departure_time ERROR 1

    stop_time_with_arrival_before_previous_departure_time

    Backwards time travel between stops in stop_times.txt

    For a given trip_id, the arrival_time of (n+1)-th stoptime in sequence must not precede the departure_time of n-th stoptime in sequence in stop_times.txt.

    You can see more about this notice here.

    csvRowNumber (?) The row number of the faulty record. prevCsvRowNumber (?) The row of the previous stop time. tripId (?) The trip_id associated to the faulty record. arrivalTime (?) Arrival time at the faulty record. departureTime (?) Departure time at the previous stop time.
    844 843 "23265833" "07:46:34" "08:01:38"
    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"
    fast_travel_between_consecutive_stops WARNING 2

    fast_travel_between_consecutive_stops

    A transit vehicle moves too fast between two consecutive stops.

    The speed threshold depends on route type:

    Route type Description Threshold, km/h
    0 Light rail 100
    1 Subway 150
    2 Rail 500
    3 Bus 150
    4 Ferry 80
    5 Cable tram 30
    6 Aerial lift 50
    7 Funicular 50
    11 Trolleybus 150
    12 Monorail 150
    - Unknown 200

    You can see more about this notice here.

    tripCsvRowNumber (?) The row number of the problematic trip. tripId (?) `trip_id` of the problematic trip. routeId (?) `route_id` of the problematic trip. speedKph (?) Travel speed (km/h). distanceKm (?) Distance between stops (km). csvRowNumber1 (?) The row number of the first stop time. stopSequence1 (?) `stop_sequence` of the first stop. stopId1 (?) `stop_id` of the first stop. stopName1 (?) `stop_name` of the first stop. departureTime1 (?) `departure_time` of the first stop. csvRowNumber2 (?) The row number of the second stop time. stopSequence2 (?) `stop_sequence` of the second stop. stopId2 (?) `stop_id` of the second stop. stopName2 (?) `stop_name` of the second stop. arrivalTime2 (?) `arrival_time` of the second stop.
    131 "28197116" "322" 720.8172890678524 0.8009080989642804 1519 6 "28197118" "Unknown" "19:01:25" 1520 7 "28197119" "Unknown" "19:01:29"
    221 "27721013" "215" 158.09002982147425 0.4830528688989491 2600 9 "27721019" "Unknown" "21:42:59" 2601 10 "27721020" "Unknown" "21:43:10"
    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 494

    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 494 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" "campkigali" 2
    "stops.txt" "stop_name" "chuk" 3
    "stops.txt" "stop_name" "city market" 5
    "stops.txt" "stop_name" "plaza" 6
    "stops.txt" "stop_name" "rwandex" 8
    "stops.txt" "stop_name" "sonatube" 11
    "stops.txt" "stop_name" "chuk" 16
    "stops.txt" "stop_name" "ku nkurunziza stop" 18
    "stops.txt" "stop_name" "city market" 19
    "stops.txt" "stop_name" "city plaza" 20
    "stops.txt" "stop_name" "ape rugunga stop" 21
    "stops.txt" "stop_name" "mironko stop" 22
    "stops.txt" "stop_name" "rwandex stop" 23
    "stops.txt" "stop_name" "amasezerano stop" 24
    "stops.txt" "stop_name" "sonatubes" 26
    "stops.txt" "stop_name" "prince house" 28
    "stops.txt" "stop_name" "remera bus park" 29
    "stops.txt" "stop_name" "remera park" 30
    "stops.txt" "stop_name" "sonatube" 31
    "stops.txt" "stop_name" "rwandex" 32
    "stops.txt" "stop_name" "payage" 34
    "stops.txt" "stop_name" "rubangura" 35
    "stops.txt" "stop_name" "downtown" 36
    "stops.txt" "stop_name" "gacingiro" 37
    "stops.txt" "stop_name" "meteo" 38
    "stops.txt" "stop_name" "campkigali" 39
    "stops.txt" "stop_name" "remera bus park" 40
    "stops.txt" "stop_name" "sonatubes stop" 41
    "stops.txt" "stop_name" "rwandex stop" 43
    "stops.txt" "stop_name" "ku mazi stop" 46
    "stops.txt" "stop_name" "rubangura stop" 48
    "stops.txt" "stop_name" "down town bus stop" 49
    "stops.txt" "stop_name" "kabuga gare" 51
    "stops.txt" "stop_name" "murindi" 52
    "stops.txt" "stop_name" "prince house" 54
    "stops.txt" "stop_name" "sonatube" 55
    "stops.txt" "stop_name" "rwandex" 56
    "stops.txt" "stop_name" "kanzayire" 57
    "stops.txt" "stop_name" "kinamba" 58
    "stops.txt" "stop_name" "kumagare" 59
    "stops.txt" "stop_name" "nyabugogo" 60
    "stops.txt" "stop_name" "kabuga" 61
    "stops.txt" "stop_name" "murindi" 62
    "stops.txt" "stop_name" "good year" 64
    "stops.txt" "stop_name" "sonatube" 65
    "stops.txt" "stop_name" "kumasezerano" 66
    "stops.txt" "stop_name" "rwandex" 67
    "stops.txt" "stop_name" "kwamironko" 68
    "stops.txt" "stop_name" "kumazi" 69
    "stops.txt" "stop_name" "kinamba1" 70
    stop_too_far_from_shape WARNING 1

    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.
    169 "30460935" "30460935" 1931 "30459523" "nyabugogo park to kanyinya" [-1.940592,30.043729000000006] 115.80522647922345
    stops_match_shape_out_of_order WARNING 1

    stops_match_shape_out_of_order

    Two stop entries are different than their arrival-departure order defined by shapes.txt.

    This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

    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. stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`. stopId1 (?) The id of the first stop that is referred to. stopName1 (?) The name of the first stop that is referred to. match1 (?) Latitude and longitude pair of the first matching location. stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`. stopId2 (?) The id of the second stop that is referred to. stopName2 (?) The name of the second stop that is referred to. match2 (?) Latitude and longitude pair of the second matching location.
    15 "22650531" "22650531" 239 "22650537" "Unknown" [-1.950511,30.060183] 238 "22650536" "Unknown" [-1.9505499999999996,30.059630000000002]
    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.
    "20260504" "20190225" "20210225"