Feed status · checked 2026-07-24
City Direct
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Ireland.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.2, validator 8.0.1.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top 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.Likely your team
229 of 229 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.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
754 of 754 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
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.
⏱ A small file for most flat-fare systems.worth about +15 points in its category
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
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. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 364 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- No fare information is published in the feed.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 1 kind of issue across 2 instances (0 error, 0 warning, 2 informational).
Service data covers the next 364 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
19 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("St Francis Street", "Kilminchy Ave", "St Luke's Hospital", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 410 (green)
- 411 (green)
- 412 (green)
- KK1 (green)
- KK2 (green)
- PL1 (green)
- PL2 (green)
| Route | Type | Line color |
|---|---|---|
| 410 Mount Prospect - Eyre Square | Bus | green |
| 411 Mount Prospect - Eyre Square | Bus | green |
| 412 Mount Prospect - Eyre Square | Bus | green |
| KK1 N77 Roundabout - Danville Business Park | Bus | green |
| KK2 Cillín Hill - Saint Luke's Hospital | Bus | green |
| PL1 Colliers Lane - Woodgrove | Bus | green |
| PL2 Kilminchy Avenue - Bellingham | Bus | green |
This feed has 229 stops.
List every stop
- Archers Cres
- Middleknock
- Middleknock
- Leggetsrath
- Leggetsrath
- Johnswell Road
- Johnswell Road
- Beechlawns
- Beechlawns
- Newpark SC
- Newpark SC
- Nowlan Park
- Nowlan Park
- Kilkenny Stn
- Kilkenny Stn
- John Street Lwr
- John Street Lwr
- Market Yard
- Market Yard
- Parliament St
- Parliament St
- The Sycamores
- The Sycamores
- St Luke's Hospital
- Danville B Park
- Danville B Park
- Archers Cres
- Loughboy SC
- Loughboy SC
- Laurel Drive
- Laurel Drive
- Larchfield
- Larchfield
- Deans Court
- Deans Court
- Upr Patrick St
- Upr Patrick St
- Ormonde Road
- Ormonde Road
- College Road
- College Road
- Old Callan Rd
- Old Callan Rd
- Dominic Street
- Dominic Street
- Dean Street
- Dean Street
- Kilkenny Stn
- Kilkenny Stn
- Newpark Lwr
- Newpark Lwr
- Kilkenny Coll
- Glendine
- Glendine
- Glenbawn
- Stephen's Street
- Stephen's Street
- Cillín Hill
- Kilkenny Coll
- Butt's Green
- Butt's Green
- Ayresfields
- Ayresfields
- Grange Road
- Grange Road
- Market Sq
- Market Sq
- Laois Eductn Centre
- St Peter and P's Ch
- St Peter and P's Ch
- Kilminchy
- Portlaoise Hosp
- Portlaoise JFL Ave
- Portlaoise JFL Ave
- Portlaoise Hosp
- Colliers Lane
- Colliers View
- The Hermitage
- Borris Great
- Forest Park
- Borris Little
- Doctor Murphy Place
- Saint Peter and Paul's Church
- Kellyville Park
- Portlaoise Stn
- Green Road
- Lakeglen
- Liogard
- Rossleighan Park
- Glenkeen Crescent
- Gandon Court
- Cosby Avenue
- Clonroosk Abbey
- Woodgrove
- Woodgrove
- Cosby Avenue
- Gandon Court
- Glenkeen Crescent
- Rossleighan Park
- Liogard
- Lakeglen
- Green Road
- Portlaoise Station
- Kellyville Park
- Saint Peter and Paul's Church
- Doctor Murphy Place
- Borris Little
- Forest Park
- Borris Great
- Colliers View
- Kilminchy Ave
- Carrick Hill
- Block Road
- Summerhill
- Saint Fintans Campus
- Stradbrook
- Harpur's Lane
- Parnell Crescent
- Clonroosk Abbey
- The Hermitage
- Harpur's Crescent
- Portlaoise College
- Dromadoon
- Maryborough Villge
- Bellingham
- Maryborough Village
- Dromadoon
- Portlaoise College
- Harpur's Crescent
- Parnell Crescent
- Harpur's Lane
- Stradbrook
- Saint Fintans Campus
- Summerhill
- Block Road
- Laois Education Centre
- Carrick Hill
- Kilminchy
- Kilminchy View
- Rockfield Pk
- Gort na Bró
- Eyre Square
- Eyre Square
- Páirc na Ceapaí
- An Logan
- Ard Fraoigh
- Mnr Mhóin na Lao
- Clybaun Ct
- Slí na Craoibhe
- Fearnog
- Cúirt an Mhainéir
- Fearnog
- Ladies Beach
- Binn Bhán
- Fána an Bhúrcaigh
- Fána an Bhúrcaigh
- Knocknacarragh
- Tor Buí
- Mnr Mhóin na Lao
- Prc Cnc na Cathrach
- Port an Chairrín
- Clós na dTúdarach
- Clós na dTúdarach
- Linn Bheag
- Gort Greine
- Rockfield Pk
- Rosan Glas
- Gort Greine
- Rosan Glas
- Mincloon
- Saint Mary's Road
- Westside Pk
- Lios Ealtan
- Salthill Road Lwr
- Devon Park
- Lenaboy Pk
- Salthill Upr
- Salthill Prom
- Seamount
- Ladies Beach
- Salthill Prom
- Salthill Upr
- Lenaboy Pk
- Devon Park
- Salthill Road Lwr
- Lios Ealtan
- Círín na Mara
- Knocknacarra Rd
- Brooklawn
- University Hospl
- University South
- Galway Cathdrl
- St Francis Street
- St Francis Street
- University South
- University Hospl
- IS Cnc na Cathrach
- Galway Cathdrl
- Lw Newcastle
- Lw Newcastle
- Garrai De Brun
- B O'Donnell Rd
- Gleann Dara
- Westside SC
- Westside CC
- Snipe Lawn
- Snipe Lawn
- Shantalla Park
- Westside CC
- Westside Pk
- Gleann Dara
- B O'Donnell Rd
- Garrai De Brun
- An Cimín Mór
- Gort na Bró
- Cul Aitinn
- Hawthorn Pl
- Páirc na Ceapaí
- Hawthorn Pl
- Círín na Mara
- IS Cnc na Cathrach
- Arda an Chlaí Bháin
- Altan
- An Logan
- Knocknacarra Rd
- Prc Cnc na Cathrach
- Saint Mary's Road
- Knocknacarragh
- Altan
Over time
This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.
Everything we checked
4 findings, ordered by severity.
Show every finding
- Warning754 instances
754 of 754 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning229 instances
229 of 229 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.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: 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. (A small file for most flat-fare systems.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info2 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Validator rule: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
This feed is close to the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 364 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 364 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance. Read the full standards crosswalk.
- Correctness 100 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication.
- Freshness 100 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners.
- Rider experience 45 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/city-direct-ie/2026-07-24.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-07-24. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.