google-transit-citylink — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-07T16:21:30Z,
for the dataset file:///shared/google-transit-citylink_c10fda5a.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
National Transport Authority
Feed Email:
apisupport@nationaltransport.ie
Feed Language:
English
Feed Start Date:
2026-08-05
Feed End Date:
2027-08-05

Files included


  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. feed_info.txt
  5. routes.txt
  6. shapes.txt
  7. stop_times.txt
  8. stops.txt
  9. translations.txt
  10. trips.txt

Counts


  • Agencies: 1
  • Blocks: 338
  • Routes: 11
  • Shapes: 46
  • Stops: 123
  • Trips: 347

Specification Compliance report

97 notices reported (1 errors, 69 warnings, 27 infos)

Notice Code Severity Total
block_trips_with_overlapping_stop_times ERROR 1

block_trips_with_overlapping_stop_times

Trips with the same block id have overlapping stop times.

You can see more about this notice here.

csvRowNumberA (?) The row number from `trips.txt` of the first faulty trip. tripIdA (?) The id of first faulty trip. serviceIdA (?) The service id of the first faulty trip. csvRowNumberB (?) The row number from `trips.txt` of the second faulty trip. tripIdB (?) The id of the other faulty trip. serviceIdB (?) The service id of the other faulty trip. blockId (?) The `trips.block_id` of the overlapping trip. intersection (?) The overlapping period.
322 "5830_75" "37" 325 "5830_78" "37" "5830_7778001_263" "20260804"
mixed_case_recommended_field WARNING 63

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 63 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.
"trips.txt" "trip_short_name" "2.BH.3-707-y11-7.2.O" 6
"trips.txt" "trip_short_name" "19.BH.3-707-y11-7.2." 9
"trips.txt" "trip_short_name" "3.BH.3-707-y11-7.2.O" 12
"trips.txt" "trip_short_name" "4.BH.3-707-y11-7.2.O" 16
"trips.txt" "trip_short_name" "5.BH.3-707-y11-7.2.O" 19
"trips.txt" "trip_short_name" "6.BH.3-707-y11-7.2.O" 22
"trips.txt" "trip_short_name" "7.BH.3-707-y11-7.2.O" 26
"trips.txt" "trip_short_name" "8.BH.3-707-y11-7.2.O" 29
"trips.txt" "trip_short_name" "9.BH.3-707-y11-7.2.O" 32
"trips.txt" "trip_short_name" "10.BH.3-707-y11-7.2." 37
"trips.txt" "trip_short_name" "11.BH.3-707-y11-7.2." 40
"trips.txt" "trip_short_name" "12.BH.3-707-y11-7.2." 43
"trips.txt" "trip_short_name" "13.BH.3-707-y11-7.2." 46
"trips.txt" "trip_short_name" "14.BH.3-707-y11-7.2." 50
"trips.txt" "trip_short_name" "15.BH.3-707-y11-7.2." 54
"trips.txt" "trip_short_name" "16.BH.3-707-y11-7.2." 57
"trips.txt" "trip_short_name" "17.BH.3-707-y11-7.2." 61
"trips.txt" "trip_short_name" "18.BH.3-707-y11-7.2." 64
"trips.txt" "trip_short_name" "1.daily.3-430-y11-3." 80
"trips.txt" "trip_short_name" "2.daily.3-430-y11-3." 91
"trips.txt" "trip_short_name" "3.daily.3-430-y11-3." 102
"trips.txt" "trip_short_name" "4.daily.3-430-y11-3." 114
"trips.txt" "trip_short_name" "11.daily.3-430-y11-3" 125
"trips.txt" "trip_short_name" "5.daily.3-430-y11-3." 136
"trips.txt" "trip_short_name" "12.daily.3-430-y11-3" 147
"trips.txt" "trip_short_name" "13.daily.3-430-y11-3" 158
"trips.txt" "trip_short_name" "6.daily.3-430-y11-3." 169
"trips.txt" "trip_short_name" "7.daily.3-430-y11-3." 180
"trips.txt" "trip_short_name" "8.daily.3-430-y11-3." 191
"trips.txt" "trip_short_name" "9.daily.3-430-y11-3." 202
"trips.txt" "trip_short_name" "10.daily.3-430-y11-3" 213
"trips.txt" "trip_short_name" "14.daily.3-430-y11-3" 225
"trips.txt" "trip_short_name" "1.daily.9-763-y11-2." 228
"trips.txt" "trip_short_name" "2.daily.9-763-y11-2." 229
"trips.txt" "trip_short_name" "3.daily.9-763-y11-2." 230
"trips.txt" "trip_short_name" "4.daily.9-763-y11-2." 231
"trips.txt" "trip_short_name" "5.daily.9-763-y11-2." 232
"trips.txt" "trip_short_name" "6.daily.9-763-y11-2." 233
"trips.txt" "trip_short_name" "7.daily.9-763-y11-2." 234
"trips.txt" "trip_short_name" "8.daily.9-763-y11-2." 235
"trips.txt" "trip_short_name" "15.daily.3-430-y11-3" 236
"trips.txt" "trip_short_name" "16.daily.3-430-y11-3" 247
"trips.txt" "trip_short_name" "1.BH.3-707-y11-7.2.O" 280
"trips.txt" "trip_short_name" "2.BH.3-707-y11-7.2.O" 284
"trips.txt" "trip_short_name" "3.BH.3-707-y11-7.2.O" 287
"trips.txt" "trip_short_name" "4.BH.3-707-y11-7.2.O" 290
"trips.txt" "trip_short_name" "5.BH.3-707-y11-7.2.O" 293
"trips.txt" "trip_short_name" "6.BH.3-707-y11-7.2.O" 297
"trips.txt" "trip_short_name" "7.BH.3-707-y11-7.2.O" 300
"trips.txt" "trip_short_name" "8.BH.3-707-y11-7.2.O" 303
service_has_no_active_day_of_the_week WARNING 6

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.
6 "63"
8 "262"
10 "264"
11 "265"
12 "266"
14 "268"
big_gap_in_service INFO 20

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.
"63" "2026-10-26" "2026-12-25" 59
"63" "2027-01-01" "2027-02-01" 30
"63" "2027-02-01" "2027-03-17" 43
"63" "2027-03-29" "2027-05-03" 34
"63" "2027-05-03" "2027-06-07" 34
"63" "2027-06-07" "2027-08-02" 55
"261" "2026-10-25" "2027-04-04" 160
"262" "2026-10-26" "2027-05-03" 188
"262" "2027-05-03" "2027-06-07" 34
"262" "2027-06-07" "2027-08-02" 55
"263" "2026-10-31" "2027-04-01" 151
"267" "2026-10-25" "2026-12-20" 55
"267" "2026-12-20" "2027-04-04" 104
"268" "2026-10-26" "2026-12-25" 59
"268" "2026-12-26" "2027-05-03" 127
"268" "2027-05-03" "2027-06-07" 34
"268" "2027-06-07" "2027-08-02" 55
"269" "2026-10-31" "2026-12-21" 50
"269" "2026-12-26" "2027-04-01" 95
"270" "2026-10-31" "2027-04-01" 151
service_window_outside_feed_period INFO 7

service_window_outside_feed_period

A service window is not covered by the feed's validity period.

You can see more about this notice here.

serviceId (?) The service_id whose active window extends outside the feed validity period. serviceWindowStartDate (?) The first active date of the service window. serviceWindowEndDate (?) The last active date of the service window. daysBeforeFeedStart (?) Number of days the service window extends before feed_start_date (0 if none). daysAfterFeedEnd (?) Number of days the service window extends after feed_end_date (0 if none).
"45" "2026-08-04" "2027-08-03" 1 0
"37" "2026-08-04" "2027-08-05" 1 0
"270" "2026-08-04" "2027-08-05" 1 0
"263" "2026-08-04" "2027-08-05" 1 0
"276" "2026-08-04" "2027-08-03" 1 0
"269" "2026-08-04" "2027-08-05" 1 0
"40" "2026-08-04" "2027-08-05" 1 0