Feed status · checked 2026-08-01
Greater Dayton Regional Transit Authority (Greater Dayton RTA)
Based on the feed this agency publishes
Service mode Bus
down 0.4 since 2026-07-31
Catalogued in Ohio.
Heads-up: The score rose 36 points in one step, from 31 on 2026-07-25 to 68 on 2026-07-30. A jump this size usually means the export changed rather than the service. Worth checking the run on this date. (checked 2026-07-30). This can be a brief vendor export glitch; watch the next update before acting.
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.3, validator 8.0.1.
Checked for changes 76 minutes ago; last changed 3 days ago.
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
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool
Some rider-facing names are in ALL CAPS or all lowercase. ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
⏱ Often a bulk fix in your scheduling software.worth about +8 points in its category
Turn on 'remove unused shapes' (or the like) in your export tool.Likely your export tool
The feed contains route shapes no trip uses. Harmless to riders, but it bloats the feed and suggests stale export data.
⏱ One setting.worth about +6 points in its category
Remove retired stops from the export, or add them back to the trips that should serve them.Likely your export tool
Some stops exist in the feed but no trip ever stops at them. Riders may walk to a stop where no bus is scheduled to arrive.
⏱ A review pass in your scheduling software.worth about +6 points in its category
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
- Some rider-facing names are in ALL CAPS or all lowercase.
- Next action
- Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
- 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 route shapes no trip uses.
- Next action
- Turn on 'remove unused shapes' (or the like) in your export tool.
- 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
- Some stops exist in the feed but no trip ever stops at them.
- Next action
- Remove retired stops from the export, or add them back to the trips that should serve them.
- 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
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.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · 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. See this feed's finding-clearance log.
Turn on 'remove unused shapes' (or the like) in your export tool. · 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. See this feed's finding-clearance log.
Remove retired stops from the export, or add them back to the trips that should serve them. · 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. See this feed's finding-clearance log.
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 35 days.
- Published accessibility data
- Accessibility information is stated for 99.5% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- 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 7 kinds of issue across 2913 instances (0 error, 2913 warning, 0 informational).
Service data covers the next 35 days.
100% of stops state wheelchair accessibility (13% marked accessible, 86% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
100% of stops state accessibility (13% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
9 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (01, 02, 04, 06, 07, and more).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
2672 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("3RD @ PERRY", "3RD @ MARYS", "3RD @ GRIMES", 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.
Fares are applied to trips.
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.
This feed has 2715 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 01 (pink)
- 02 (green)
- 03 (white)
- 04 (teal)
- 06 (purple)
- 07 (red)
- 08 (teal)
- 09 (gray)
- 12 (green)
- 16 (teal)
- 17 (yellow)
- 18 (gray)
- 19 (red)
- 22 (red)
- 28 (orange)
- 43 (teal)
- 44 (teal)
- 70 (teal)
- 71 (green)
- FLYER (blue)
- X6 (green)
| Route | Type | Line color |
|---|---|---|
| 01 ROUTE 1 | Bus | pink |
| 02 ROUTE 2 | Bus | green |
| 03 ROUTE 3 | Bus | white |
| 04 ROUTE 4 | Bus | teal |
| 06 ROUTE 6 | Bus | purple |
| 07 ROUTE 7 | Bus | red |
| 08 ROUTE 8 | Bus | teal |
| 09 ROUTE 9 | Bus | gray |
| 12 ROUTE 12 | Bus | green |
| 16 ROUTE 16 | Bus | teal |
| 17 ROUTE 17 | Bus | yellow |
| 18 ROUTE 18 | Bus | gray |
| 19 ROUTE 19 | Bus | red |
| 22 ROUTE 22 | Bus | red |
| 28 ROUTE 28 | Bus | orange |
| 43 ROUTE 43 | Bus | teal |
| 44 ROUTE 44 | Bus | teal |
| 70 NORTH CONNECTOR | Bus | teal |
| 71 WEST CONNECTOR | Bus | green |
| 999 TEST ROUTES | Bus | white (no shape in feed) |
| FLYER | Bus | blue |
| X6 ROUTE X6 | Bus | green |
List every stop
- 3RD @ PERRY
- W 3RD ST @ CLEMMER ST
- WATERVLIET @ KING
- PATTERSON @ HAMPSHIRE
- PATTERSON @ SHADOWLAWN
- PATTERSON @ SHROYER
- IRVING @ FIRWOOD
- IRVING @ ACACIA
- IRVING @ MAHRT
- IRVING @ EVANSTON
- IRVING @ LAWNVIEW
- IRVING @ BROWN
- SMITHVILLE @ FAIRPARK
- WATERVLIET @ REVERE
- SMITHVILLE @ RADIO
- SMITHVILLE @ RANGELEY
- WATERVLIET @ WAYNE
- SMITHVILLE @ WAYNE
- SMITHVILLE @ ASHLAND
- SMITHVILLE @ TABOR
- DOROTHY @ WILMINGTON
- DOROTHY @ LARUE
- DOROTHY @ BULAH
- WOODMAN @ DOROTHY
- WOODMAN @ 3085 WOODMAN
- WOODMAN @ DANUBE
- WOODMAN @ STOCKER
- WOODMAN @ GRICE
- WOODMAN @ DORIS
- WOODMAN @ STROOP
- BIGGER @ DAVID
- BIGGER @ POLEN
- BIGGER @ CAROL PARKWAY
- BIGGER @ BELLOAK
- BIGGER @ 5099 BIGGER
- BIGGER @ RAHN
- BIGGER @ RAHN
- BIGGER @ BELLOAK
- ARBOR @ ALICE
- BIGGER @ 4800 BIGGER
- BIGGER @ POLEN
- BIGGER @ DAVID
- DAVID @ WILMINGTON
- WOODMAN @ STROOP
- WOODMAN @ 3720 WOODMAN
- WOODMAN @ GRICE
- WOODMAN @ STOCKER
- WOODMAN @ DANUBE
- WOODMAN @ 3080 WOODMAN
- WOODMAN @ DOROTHY
- DOROTHY @ 2001 DOROTHY
- DOROTHY @ MOHICAN
- DOROTHY @ BOBBIE
- WILMINGTON @ ANSEL
- WILMINGTON @ IMPERIAL
- SMITHVILLE @ TABOR
- ARBOR @ WYOMING
- SMITHVILLE @ ASHLAND
- SMITHVILLE @ ARCADIA
- SMITHVILLE @ CORINTH
- WYOMING @ CREIGHTON
- SMITHVILLE @ RADIO
- SMITHVILLE @ FAIRPARK
- SMITHVILLE @ SPRINGFIELD
- WYOMING @ NICHOLAS
- WAYNE @ JACKSON
- 5TH @ BAINBRIDGE
- 5TH @ DAYTON TOWERS
- 5TH @ HIGH
- 5TH @ LABELLE
- 5TH @ MCCLURE
- 5TH @ HUFFMAN
- 5TH @ COLUMBUS
- 5TH @ LINDEN
- W 3RD ST @ ORCHARD AV
- WYOMING @ JOSEPH
- 5TH @GARFIELD
- 5TH @ FINDLAY
- MARTZ @ BURKHARDT
- MARTZ @ HUFFMAN
- HUFFMAN @ GILBERT
- HUFFMAN @ HOLLIER
- HUFFMAN @ WRIGHT
- HUFFMAN @ HEISS
- HUFFMAN @ SMITHVILLE
- HUFFMAN @ MERTLAND
- WYOMING @ ILLINOIS
- HUFFMAN @ KESTER
- HUFFMAN @ SHEDBORNE
- SHEDBORNE @ BURKHARDT (STOP)
- BURKHARDT @ 4740 BURKHARDT
- BURKHARDT @ VALENTINE
- BURKHARDT @ WOODMAN
- BURKHARDT @ WOODMAN
- BURKHARDT @ COSLER
- BURKHARDT @ GRANVILLE
- BURKHARDT @ DODGE
- WYOMING @ NASSAU
- BURKHARDT @ SPINNING
- SPINNING @ 635 SPINNING
- SPINNING @ DUQUESNE
- SPINNING @ ROBINWOOD
- SPINNING @ EASTMAN
- SPINNING @ PENN
- LINDEN @ 4514 LINDEN
- LINDEN @ 4433 LINDEN
- LINDEN @ WOODMAN
- SPINNING @ ROBINWOOD
- WYOMING @ STEELE
- SPINNING @ MARBLEHEAD
- SPINNING @ 700 SPINNING
- BURKHARDT @ KETCHAM
- BURKHARDT @ ABILENE
- BURKHARDT @ PANDORA
- BURKHARDT @ WOODMAN
- BURKHARDT @ VALENTINE
- WYOMING @ HAWKER
- HUFFMAN @ HEISS
- HUFFMAN @ WRIGHT
- HUFFMAN @ GARLAND
- HUFFMAN @ HEDGES
- HUFFMAN @ HOLLIER
- WYOMING @ WAYNE
- JERSEY @ HUFFMAN
- JERSEY @ 5TH
- 5TH @ MONMOUTH
- 5TH @ FINDLAY
- 5TH @GARFIELD
- 5TH @ VAN LEAR
- 5TH @ COLUMBUS
- 5TH @ HUFFMAN
- 5TH @ JUNE
- 5TH @ TERRY
- WYOMING @ CROSS
- 5TH @ DUTOIT
- 5TH @ HIGH
- 5TH @ KEOWEE
- 5TH @ 1111 5TH
- 5TH @ WALNUT
- WAYNE @ 5TH
- MAIN @ 6TH
- MAIN @ FRANKLIN
- WYOMING @ JAY
- MAIN @ LINCOLN
- MAIN @STOUT
- MAIN @ APPLE
- MAIN @ WYOMING
- STEWART @ MAIN
- STEWART @ BROWN
- WILMINGTON @ 3045 WILMINGTON
- WILMINGTON @ 3313 WILMINGTON
- MAIN @ STEWART
- WYOMING @ ALBERTA
- MAIN @ FAIRGROUND
- MAIN @ WYOMING
- MAIN @ APPLE
- MAIN @STOUT
- MAIN @ FRANKLIN
- STEWART @ BROWN
- IRVING @ BROWN
- IRVING @ LAWNVIEW
- WYOMING @ BROWN
- IRVING @ EVANSTON
- IRVING @ MAHRT
- IRVING @ ACACIA
- IRVING @ MIDBLOCK
- IRVING @ FIRWOOD
- IRVING @ KLING
- SHROYER @ SHELBY
- SHROYER @ KREBS
- SHROYER @ ROY
- SHROYER @ PATTERSON
- PATTERSON @ SHROYER
- PATTERSON @ DEVONSHIRE
- PATTERSON @ HAMPSHIRE
- PATTERSON @ WILMINGTON
- PATTERSON @ WHITE OAK
- PATTERSON @ KENMORE
- PATTERSON @ MARTEL
- PATTERSON @ SMITHVILLE
- FORRER @ SMITHVILLE
- MAIN @ PIONEER
- FORRER @ MAYL
- FORRER @ HAZEL
- FORRER @ CULVER
- FORRER @ 2000 FORRER
- FORRER @ 2000 FORRER
- KETTERING RECREATIONAL CENTER
- GETTYSBURG @ FRANCES
- GETTYSBURG @ 2ND
- GETTYSBURG @ EDISON
- GETTYSBURG @ 900 GETTYSBURG
- MAIN @ VINCENT
- GETTYSBURG @ HOOVER
- GETTYSBURG @ FAIRBANKS
- GETTYSBURG @ DANDRIDGE
- GETTYSBURG @ FRUEDENBERGER
- GETTYSBURG @ JAMES H MCGEE
- GETTYSBURG @ LITTLE RICHMOND
- GETTYSBURG @ SAINT JAMES
- GETTYSBURG @ HILLCREST
- MAIN @ HELENA
- FREE PIKE @ GETTYSBURG
- FREE PIKE @ ENGLAND
- FREE PIKE @ FAIR
- FREE PIKE @ ARLENE
- FREE PIKE @ BRUMBAUGH
- DENLINGER @ 3656 DENLINGER
- DENLINGER @ NATALIE
- DENLINGER @ THORAIN
- DENLINGER @ JOHN WOLFE PARK
- DENLINGER @ MARIA JOSEPH
- MAIN @ MUMMA
- DENLINGER @ SALEM
- DENLINGER @ FRANKS NURSERY
- DENLINGER @ BERQUIST
- FRIENDSHIP VILLAGE
- DENLINGER @ WESTBROOK
- FAR HILLS @ 5112 FAR HILLS
- FAR HILLS @ ENID
- FAR HILLS @ LAURELANN
- FAR HILLS @ WESTGATE
- FAR HILLS @ DAVID
- MAIN @ BURTON
- FAR HILLS @ SHROYER
- FAR HILLS @ 4300 FAR HILLS
- FAR HILLS @ MOSSOAK
- FAR HILLS @ STROOP
- 1ST @ PATTERSON
- 1ST @ MADISON
- KEOWEE @ HUNTER
- MAIN @ RIDGE
- KEOWEE @ 1496 KEOWEE
- KEOWEE @ STANLEY
- DIXIE @ OME
- DIXIE @ NEVA
- DIXIE @ BERWYCK
- DIXIE @ SIEBENTHALER
- DIXIE @ MAPLE GROVE
- DIXIE @ KEENAN
- WEBSTER @ PRODUCTION
- WEBSTER @ OBCO
- MAIN @ HUDSON
- WEBSTER @ NORDIC
- WEBSTER @ 6192 WEBSTER
- STOP EIGHT @ VENTOR
- STOP EIGHT @ 3345 STOP EIGHT
- POE @ WYSE
- POE @ 6520 POE
- POE @ SPACE
- and 2465 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — down 0.4 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 31.3 | first check |
| 2026-07-30 | 67.6 | up 36.3 |
| 2026-07-31 | 67.2 | down 0.4 |
| 2026-08-01 | 66.8 | down 0.4 |
What changed since your last check
- Correctness no change
- Freshness down 1.7
- Rider experience no change
What changed in this feed
Overall score fell 0.4 points since 2026-07-31.
Same feed file as 2026-07-31; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
What changed over time
On 2026-07-25 this feed started at grade F. On 2026-07-30 the grade moved from F to D. As of 2026-08-01 it holds grade D.
A plain-language history of this feed, newest first.
- 2026-07-30 Grade went F to D, rider experience rose 78 points.
Everything we checked
10 findings, ordered by severity.
Show every finding
- Warning2846 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning50 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Finding code: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning13 instances
13 of 2715 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.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning12 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some route long names repeat the route's short name inside them.
Apps show both names together, so riders see the number twice, like '5 5 Downtown'.
Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)
Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2686 instances
About 2686 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 35 days.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
- agency_id equals your NTD ID (optional) Not checked yet
- This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
- shapes.txt covers your trips Ready
- All 4165 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Awarded
This feed earns the conformance mark: valid, current, and stating wheelchair access on nearly every stop and trip.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 35 days.
- Accessible Met
- States wheelchair access on 100% of stops and 100% of trips.
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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 12 of 2715 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Clears the Google and Apple Maps four-week coverage bar. This feed has 35 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, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
- Correctness 64 / 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. FTA NTD readiness also checks that the published feed is valid.
- Freshness 58 / 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. FTA NTD readiness also checks that the published feed is current.
- Rider experience 78 / 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/greater-dayton-regional-transit-authority-greater-dayton-rta/2026-08-01.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-08-01. 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.