brindisi — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-01T19:48:02Z,
for the dataset file:///shared/brindisi_f7b59b06.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: 368
  • Trips: 12752

Specification Compliance report

1555 notices reported (0 errors, 1548 warnings, 7 infos)

Notice Code Severity Total
missing_bike_allowance WARNING 1518

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 1518 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.
21 "4" "10014"
22 "4" "10015"
23 "4" "10016"
24 "4" "10017"
41 "4" "10032"
51 "4" "10041"
72 "4" "10060"
74 "4" "10062"
75 "4" "10063"
77 "4" "10065"
78 "4" "10066"
79 "4" "10067"
85 "4" "10072"
87 "4" "10074"
91 "4" "10078"
108 "4" "10093"
118 "4" "10101"
121 "4" "10104"
123 "4" "10106"
124 "4" "10107"
128 "4" "10110"
145 "4" "10126"
146 "4" "10127"
147 "4" "10128"
157 "4" "10137"
158 "4" "10138"
159 "4" "10139"
170 "4" "10149"
173 "4" "10151"
174 "4" "10152"
183 "4" "10160"
194 "4" "10170"
210 "4" "10185"
211 "4" "10186"
213 "4" "10188"
220 "4" "10194"
246 "4" "10217"
247 "4" "10218"
254 "4" "10224"
294 "4" "10260"
306 "4" "10271"
310 "4" "10275"
343 "4" "10304"
351 "4" "10311"
357 "4" "10317"
363 "4" "10322"
364 "4" "10323"
366 "4" "10325"
370 "4" "10329"
378 "4" "10336"
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
service_has_no_active_day_of_the_week WARNING 28

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.
2 "1"
3 "2"
4 "3"
5 "4"
6 "5"
7 "6"
8 "7"
9 "8"
10 "9"
11 "10"
12 "11"
13 "12"
14 "13"
15 "14"
16 "15"
17 "16"
18 "17"
19 "18"
20 "19"
21 "20"
22 "21"
23 "22"
24 "23"
25 "24"
26 "25"
27 "26"
28 "27"
29 "28"
big_gap_in_service INFO 7

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.
"9" "2026-08-06" "2026-08-27" 20
"10" "2026-08-04" "2026-08-25" 20
"11" "2026-08-07" "2026-08-28" 20
"12" "2026-08-08" "2026-08-29" 20
"13" "2026-08-09" "2026-08-30" 20
"14" "2026-08-03" "2026-08-24" 20
"15" "2026-08-05" "2026-08-26" 20