GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-04T22:49:27Z,
for the dataset file:///shared/brindisi_10417a2e.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. routes.txt
  5. stop_times.txt
  6. stops.txt
  7. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 15
  • Shapes: 0
  • Stops: 369
  • Trips: 6363

Specification Compliance report

396 notices reported (0 errors, 396 warnings, 0 infos)

Notice Code Severity Total
expired_calendar WARNING 1

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.
7 "6"
missing_bike_allowance WARNING 393

missing_bike_allowance

Ferry trips should include bike allowance information.

All ferry trips should have a valid value in the bikes_allowed field in trips.txt.

You can see more about this notice here.

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

csvRowNumber (?) The row number of the faulty record. routeId (?) The faulty record's route id. tripId (?) The faulty record's trip id.
122 "4" "1106"
169 "4" "1149"
287 "4" "1255"
290 "4" "1258"
291 "4" "1259"
324 "4" "1289"
505 "4" "1451"
542 "4" "1485"
543 "4" "1486"
544 "4" "1487"
679 "4" "1608"
698 "4" "1625"
699 "4" "1626"
700 "4" "1627"
701 "4" "1628"
702 "4" "1629"
830 "4" "1744"
893 "4" "1800"
993 "4" "1891"
1026 "4" "1920"
1106 "4" "1993"
1221 "4" "2096"
1244 "4" "2116"
1245 "4" "2117"
1321 "4" "2186"
1322 "4" "2187"
1323 "4" "2188"
1362 "4" "2222"
1421 "4" "2276"
1507 "4" "2353"
1527 "4" "2371"
1714 "4" "254"
1725 "4" "255"
1831 "4" "2645"
1843 "4" "2656"
2045 "4" "2838"
2059 "4" "2850"
2060 "4" "2851"
2072 "4" "2862"
2095 "4" "2883"
2129 "4" "2913"
2264 "4" "3034"
2282 "4" "3050"
2285 "4" "3053"
2286 "4" "3054"
2295 "4" "3062"
2300 "4" "3067"
2306 "4" "3072"
2309 "4" "3075"
2312 "4" "3078"
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.
"routes.txt" "route_long_name" "NAVETTA CENTRO" 4