google-transit-jjkavanagh — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-01T07:17:47Z,
for the dataset file:///shared/google-transit-jjkavanagh_51b17735.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-07-30
Feed End Date:
2027-07-30

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: 377
  • Routes: 15
  • Shapes: 84
  • Stops: 292
  • Trips: 381

Specification Compliance report

44 notices reported (0 errors, 39 warnings, 5 infos)

Notice Code Severity Total
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.
235 "5795_279" "293 717 m" 499.1157749987355 8.318596249978926 4805 7 "8270B3510501" "Callan" "16:40:00" 4806 8 "843000031" "Killamery" "16:40:00"
237 "5795_280" "293 717 m" 499.1157749987355 8.318596249978926 4865 7 "8270B3510501" "Callan" "18:40:00" 4866 8 "843000031" "Killamery" "18:40:00"
mixed_case_recommended_field WARNING 37

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.
"trips.txt" "trip_short_name" "1.M-T.43-NUM-6-y11-4" 11
"trips.txt" "trip_short_name" "2.M-T.43-NUM-6-y11-4" 14
"trips.txt" "trip_short_name" "2.M-T.43-MU1-4-y11-3" 22
"trips.txt" "trip_short_name" "3.M-T.43-MU1-4-y11-3" 23
"trips.txt" "trip_short_name" "4.M-T.43-MU1-4-y11-3" 25
"trips.txt" "trip_short_name" "5.M-T.43-MU1-4-y11-3" 26
"trips.txt" "trip_short_name" "7.M-T.43-MU1-4-y11-3" 27
"trips.txt" "trip_short_name" "6.M-T.43-MU1-4-y11-3" 29
"trips.txt" "trip_short_name" "1.daily.12-735-y11-6" 242
"trips.txt" "trip_short_name" "2.daily.12-735-y11-6" 243
"trips.txt" "trip_short_name" "3.daily.12-735-y11-6" 244
"trips.txt" "trip_short_name" "4.daily.12-735-y11-6" 245
"trips.txt" "trip_short_name" "5.daily.12-735-y11-6" 246
"trips.txt" "trip_short_name" "14.daily.12-735-y11-" 248
"trips.txt" "trip_short_name" "14.daily.12-735-y11-" 249
"trips.txt" "trip_short_name" "7.daily.12-735-y11-6" 250
"trips.txt" "trip_short_name" "9.daily.12-735-y11-6" 251
"trips.txt" "trip_short_name" "10.daily.12-735-y11-" 252
"trips.txt" "trip_short_name" "11.daily.12-735-y11-" 253
"trips.txt" "trip_short_name" "12.daily.12-735-y11-" 254
"trips.txt" "trip_short_name" "13.daily.12-735-y11-" 255
"trips.txt" "trip_short_name" "15.daily.12-735-y11-" 256
"trips.txt" "trip_short_name" "16.daily.12-735-y11-" 257
"trips.txt" "trip_short_name" "26.daily.12-735-y11-" 260
"trips.txt" "trip_short_name" "19.daily.12-735-y11-" 261
"trips.txt" "trip_short_name" "18.daily.12-735-y11-" 262
"trips.txt" "trip_short_name" "20.daily.12-735-y11-" 263
"trips.txt" "trip_short_name" "21.daily.12-735-y11-" 264
"trips.txt" "trip_short_name" "22.daily.12-735-y11-" 265
"trips.txt" "trip_short_name" "23.daily.12-735-y11-" 266
"trips.txt" "trip_short_name" "24.daily.12-735-y11-" 267
"trips.txt" "trip_short_name" "25.daily.12-735-y11-" 268
"trips.txt" "trip_short_name" "6.MF-BH.38-874-y11-6" 307
"trips.txt" "trip_short_name" "2.MF-BH.38-874-y11-6" 308
"trips.txt" "trip_short_name" "3.MF-BH.38-874-y11-6" 309
"trips.txt" "trip_short_name" "5.MF-BH.38-874-y11-6" 310
"trips.txt" "trip_short_name" "4.MF-BH.38-874-y11-6" 311
big_gap_in_service INFO 1

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.
"41" "2026-12-18" "2027-01-08" 20
service_window_outside_feed_period INFO 4

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).
"3" "2026-07-29" "2027-07-30" 1 0
"6" "2026-07-29" "2027-07-29" 1 0
"60" "2026-07-29" "2027-07-30" 1 0
"40" "2026-07-29" "2027-07-30" 1 0