Call-prep brief · checked 2026-08-01
Nitelink (Dublin Bus)
Grade C · 77.1 / 100
Up 1.9 points since 2026-07-31 (C to C).
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the rider information is complete. Each fix is framed as a next step, not a failure.
What changed since the last check
- Correctness up 4.5
- Freshness no change
- Rider experience no change
No longer reported since the last check (2 findings):
- Many of the feed's trips don't run at all in the next 7 days. (trip_coverage_not_active_for_next7_days)
- Future calendar (flagged by the MobilityData validator). (future_calendar)
This compares feed state. It does not identify who made a change or why.
Top three things to fix
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
822 of 822 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Effort: A column in stops.txt; your scheduling software likely has it.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
105 of 105 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Effort: A default or per-trip field in your export.
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Effort: A small file for most flat-fare systems.
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- 822 of 822 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- 105 of 105 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- The feed contains no fare information.
- Next action
- Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
Key facts
- Feed URL
- https://www.transportforireland.ie/transitData/Data/GTFS_Nitelink.zip
- Last checked
- 2026-08-01
- Service window
- 148 days of service data remain. Last service date 2026-12-27.
- Feed version
- 1676C027-860A-4613-B81E-09E232E8FF48
- Location
- Dublin, Ireland
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.3, validator 8.0.1.