Prep for a call: printable one-page brief · For your board packet: printable one-pager · Fix log: every issue this feed has cleared · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
Towson Loop
Based on the feed this agency publishes
up 4.4 since 2026-07-08 · D → C
Ahead of 62% of all tracked agencies and 59% of small agencies. Operates in Maryland.
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.1, validator 8.0.1.
Checked for changes 12 minutes ago; last changed 12 minutes ago.
Measured 4 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- 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
47 of 47 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
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).Likely your export tool
369 of 369 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ Often one default setting in your export.worth about +15 points
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Populate trip_headsign to match what the bus displays.Likely your export tool
369 of 369 trips have no headsign. Riders at the stop can't tell which direction a bus is going.
⏱ Usually a bulk edit in your scheduling software.worth about +15 points
This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
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. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). · Read the fix guide
Make the change. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
Populate trip_headsign to match what the bus displays. · Read the fix guide
Make the change. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
Send Passio a fix request
This feed is generated by your Passio system. Copy this and send it to your Passio contact; the fixes apply to the route and stop data behind your AVL setup. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 2 kinds of issue across 3 instances (0 error, 1 warning, 2 informational).
Service data covers the next 30 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.
2 accessibility depth signals
2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (O, P).
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.
41 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Campus View Dr at Sheppard Pratt (EB)", "Dulaney Valley Rd at Towson Town Center Mall - Macy's (NB)", "Dulaney Valley Rd at Towson Town Center Mall (Macy's) (SB)", 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.
Sampled 9 times outside service hours: 3 of 3 feeds healthy.
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.
- O (orange)
- P (purple)
| Route | Type | Line color |
|---|---|---|
| O Orange Loop | Bus | orange |
| P Purple Loop | Bus | purple |
This feed has 47 stops.
List every stop
- Bykota
- ByKota Senior Center
- Edenwald NB
- Southerly Rd at Towson Gate Drive (EB)
- Fairmount Ave at Towson Town Center Mall (EB)
- Fairmount Ave at E. Joppa Rd (SB)
- Dulaney Valley Rd at Towson Town Center Mall - Macy's (NB)
- York Rd at E. Pennsylvania Ave (NB)
- W. Pennsylvania Ave at York Rd (WB)
- W. Chesapeake Ave at Courtland Ave (EB)
- York Rd at E. Chesapeake Ave (NB)
- York Rd at Aigburth Rd (NB)
- York Rd at Aigburth Rd (SB)
- York Rd at St. Joseph Hospital Rd (SB)
- York Rd at St. Joseph Hospital Rd (NB)
- York Rd at Stevenson Ln (SB)
- York Rd at Stevenson Ln (NB)
- Stevenson Ln at Heathfield Rd (EB)
- Stevenson Ln at Heathfield Rd (WB)
- Osler Dr at Sister Pierre Dr (SB)
- Osler Dr at Sister Pierre Dr (NB)
- Campus View Dr at Sheppard Pratt (EB)
- W. Pennsylvania Ave at Baltimore Ave (WB)
- GBMC East Pavillion
- GBMC internal roadway at LaPetite Child Care Center (SB)
- LaSalle Rd at SECU (NB)
- Putty Hill Ave at Calvert Hall College High School (EB)
- Goucher Blvd at Prince Rd (SB)
- Goucher Blvd at Prince Rd (NB)
- Prince Rd at Towson Place Shopping Mall (SB)
- E. Joppa Rd at Black & Decker (EB)
- E. Joppa Rd at Black & Decker (WB)
- Dulaney Valley Rd at Towson Town Center Mall (Macy's) (SB)
- E. Joppa Rd at Virginia Ave (WB)
- E. Joppa Rd at Virginia Ave (EB)
- E. Joppa Rd at Fairmount Ave (WB)
- E. Joppa Rd at Tabco Towers (EB)
- Fairmount Ave at Bosley Ave (WB)
- Fairmount Ave at Bosley Ave (EB)
- Fairmount Ave at York Rd (EB)
- Fairmount Ave at Radcliffe Rd (WB)
- West Rd at 111 West Rd (EB)
- West Rd at 32 West Rd. (WB)
- Kenilworth Dr at The Shops at Kenilworth (EB)
- Kenilworth Dr at The Shops at Kenilworth (WB)
- Donington Cir
- E. Pennsylvania Ave At Jefferson Ave (WB)
Over time
Overall score across the last 21 checks — up 4.4 since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 62.7 | first check |
| 2026-06-20 | 67.7 | up 5.0 |
| 2026-06-21 | 70.9 | up 3.2 |
| 2026-06-22 | 68.1 | down 2.8 |
| 2026-06-23 | 67.3 | down 0.8 |
| 2026-06-24 | 67.0 | down 0.3 |
| 2026-06-25 | 67.0 | no change |
| 2026-06-26 | 67.3 | up 0.3 |
| 2026-06-27 | 64.7 | down 2.6 |
| 2026-06-28 | 70.9 | up 6.2 |
| 2026-06-29 | 66.5 | down 4.4 |
| 2026-06-30 | 67.2 | up 0.7 |
| 2026-07-01 | 66.5 | down 0.7 |
| 2026-07-02 | 66.0 | down 0.5 |
| 2026-07-03 | 66.8 | up 0.8 |
| 2026-07-04 | 62.7 | down 4.1 |
| 2026-07-05 | 70.9 | up 8.2 |
| 2026-07-06 | 68.3 | down 2.6 |
| 2026-07-07 | 65.3 | down 3.0 |
| 2026-07-08 | 66.5 | up 1.2 |
| 2026-07-09 | 70.9 | up 4.4 |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality up 21.9
What changed in this feed
Grade improved from D to C since 2026-07-08.
The feed file was re-published since 2026-07-08.
Resolved since 2026-07-08 (2 findings)
- Some live predictions disagree with the schedule by more than 30 minutes. (scorecard_rt_predictions_implausible)
- 5 of 8 trips scheduled during the sampling window had no live predictions. (scorecard_rt_trip_coverage)
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-06-19 this feed started at grade D. On 2026-06-21 the grade moved from D to C. On 2026-06-22 the grade moved from C to D. On 2026-06-28 the grade moved from D to C. As of 2026-07-09 it holds grade C.
A plain-language history of this feed, newest first.
- 2026-07-09 Grade went D to C, realtime rose 22 points.
- 2026-07-07 Score fell 3 points, realtime fell 15 points.
- 2026-07-06 Grade went C to D, realtime fell 13 points.
- 2026-07-05 Grade went D to C, realtime rose 41 points.
- 2026-07-04 Score fell 4 points, realtime fell 20 points.
- 2026-06-29 Grade went C to D, realtime fell 22 points.
- 2026-06-28 Grade went D to C, realtime rose 31 points.
- 2026-06-22 Grade went C to D, realtime fell 14 points.
- 2026-06-21 Grade went D to C, realtime rose 16 points.
- 2026-06-20 Score rose 5 points, realtime rose 25 points.
Everything we checked
- Warning369 instances
369 of 369 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 (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning369 instances
369 of 369 trips have no headsign.
Riders at the stop can't tell which direction a bus is going.
Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)
Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning47 instances
47 of 47 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
Stops match shape out of order (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stops_match_shape_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules 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
Service window outside feed period (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_window_outside_feed_period' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 17 observed fixes).
Validator rule: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD certification readiness Needs attention
This feed is close to NTD-ready. Service data runs out in 30 days; renew before you certify.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Needs attention
- Service data runs out in 30 days; renew before you certify.
- agency_id matches your NTD ID Not checked yet
- Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
- shapes.txt covers your trips Ready
- All 369 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 and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
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). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and 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 Not yet
This feed is close to the conformance mark. Service data runs out in 30 days; renew to qualify. 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 Not yet
- Service data runs out in 30 days; renew to qualify.
- 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.
Realtime reliability
The realtime feed responded on 100.0% of 105 checks over the last 16 days, with 3s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Clears the Google and Apple Maps four-week coverage bar. This feed has 540 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
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.
- Correctness 96 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 50 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 30 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: stop names and headsigns.
- Realtime quality 100 / 100
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a live badge on your agency site or feed README. It updates daily 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/towson-loop/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, 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.