GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 5.0.1 at 2024-06-07T15:52:17Z,
for the dataset file:///tmp/1_in.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 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. transfers.txt
  12. trips.txt

Counts


  • Agencies: 0
  • Blocks: 1
  • Routes: 104
  • Shapes: 0
  • Stops: 77
  • Trips: 212

GTFS Features included (?) GTFS features provide a standardized vocabulary to define and describe features that are officially adopted in GTFS.


Route ColorsWheelchair AccessibilityBikes AllowanceLocation Types

Specification Compliance report

52 notices reported (14 errors, 38 warnings, 0 infos)

Notice Code Severity Total
duplicate_key ERROR 13

duplicate_key

Duplicated entity.

The values of the given key and rows are duplicates.

You can see more about this notice here.

filename (?) The name of the faulty file oldCsvRowNumber (?) The row of the first occurrence. newCsvRowNumber (?) The row of the other occurrence. fieldName1 (?) Composite key's first field name. fieldValue1 (?) Composite key's first value.
"stop_times.txt" 1795 1794 "trip_id,stop_sequence" "853-2,2"
"stop_times.txt" 1797 1796 "trip_id,stop_sequence" "853-2,3"
"stop_times.txt" 1799 1798 "trip_id,stop_sequence" "853-2,4"
"stop_times.txt" 1802 1801 "trip_id,stop_sequence" "853-2,6"
"stop_times.txt" 1804 1803 "trip_id,stop_sequence" "853-2,7"
"stop_times.txt" 1806 1805 "trip_id,stop_sequence" "853-2,8"
"stop_times.txt" 1808 1807 "trip_id,stop_sequence" "853-2,9"
"stop_times.txt" 1810 1809 "trip_id,stop_sequence" "853-2,10"
"stop_times.txt" 1812 1811 "trip_id,stop_sequence" "853-2,11"
"stop_times.txt" 2186 2185 "trip_id,stop_sequence" "876-2,26"
"stop_times.txt" 2209 2208 "trip_id,stop_sequence" "878-2,19"
"stop_times.txt" 2840 2839 "trip_id,stop_sequence" "928-2,5"
"stop_times.txt" 2854 2853 "trip_id,stop_sequence" "929-2,5"
missing_required_field ERROR 1

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"
expired_calendar WARNING 3

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 "1"
3 "2"
4 "3"
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 1

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" "GARE ROUTIERE" 45
route_color_contrast WARNING 31

route_color_contrast

Insufficient route color contrast.

A route's color and route_text_color should be contrasting.

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeColor (?) The faulty record's HTML route color. routeTextColor (?) The faulty record's HTML route text color.
"9316" 61 "#FFFF00" "#FFFFFF"
"9318" 63 "#FFFF00" "#FFFFFF"
"9320" 65 "#FFFF00" "#FFFFFF"
"9321" 66 "#FFFF00" "#FFFFFF"
"9322" 67 "#FFFF00" "#FFFFFF"
"9323" 68 "#FFFF00" "#FFFFFF"
"9325" 70 "#FFFF00" "#FFFFFF"
"9326" 71 "#FFFF00" "#FFFFFF"
"9327" 72 "#FFFF00" "#FFFFFF"
"9328" 73 "#FFFF00" "#FFFFFF"
"9329" 74 "#FFFF00" "#FFFFFF"
"9330" 75 "#FFFF00" "#FFFFFF"
"9331" 76 "#FFFF00" "#FFFFFF"
"9332" 77 "#FFFF00" "#FFFFFF"
"9333" 78 "#FFFF00" "#FFFFFF"
"9334" 79 "#FFFF00" "#FFFFFF"
"9335" 80 "#FFFF00" "#FFFFFF"
"9336" 81 "#FFFF00" "#FFFFFF"
"9337" 82 "#FFFF00" "#FFFFFF"
"9338" 83 "#FFFF00" "#FFFFFF"
"9340" 85 "#FFFF00" "#FFFFFF"
"9342" 87 "#FFFF00" "#FFFFFF"
"9343" 88 "#FFFF00" "#FFFFFF"
"9344" 89 "#FFFF00" "#FFFFFF"
"9345" 90 "#FFFF00" "#FFFFFF"
"9346" 91 "#FFFF00" "#FFFFFF"
"9347" 92 "#FFFF00" "#FFFFFF"
"9348" 93 "#FFFF00" "#FFFFFF"
"9349" 94 "#FFFF00" "#FFFFFF"
"9350" 95 "#FFFF00" "#FFFFFF"
"9351" 96 "#FFFF00" "#FFFFFF"
stop_without_stop_time WARNING 1

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.
7 "132" "Altitude 800 2"
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.
"20240607" "20190101" "20191231"