Feed status · checked 2026-08-01
Towson Loop
Based on the feed this agency publishes
Service mode Bus
down 2.9 since 2026-07-31
Catalogued 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.3, validator 8.0.1.
Checked for changes 67 minutes ago; last changed 67 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
Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs.
5 of 5 trips scheduled during the sampling window had no live predictions. Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.
⏱ A vendor data-mapping question.worth about +35 points in its category
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 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
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.
⏱ A default or per-trip field in your export.worth about +15 points in its category
This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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
- 5 of 5 trips scheduled during the sampling window had no live predictions.
- Next action
- Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs.
- 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
- 47 of 47 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
- 369 of 369 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
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.
Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. · 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.
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.
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.
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.
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. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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 30 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
- Live-arrival data covered 0% of scheduled trips in the sampled window.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
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: 3 of 3 configured feeds healthy; 0.0% of scheduled trips had live predictions; 92.3% of vehicles on their route.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 47 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.
- O (orange)
- P (purple)
| Route | Type | Line color |
|---|---|---|
| O Orange Loop | Bus | orange |
| P Purple Loop | Bus | purple |
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 2 checks — down 2.9 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-31 | 66.6 | first check |
| 2026-08-01 | 63.7 | down 2.9 |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality down 14.4
What changed in this feed
Overall score fell 2.9 points since 2026-07-31.
The feed file was re-published since 2026-07-31.
Changed counts
- up 5 of 5 trips scheduled during the sampling window had no live predictions. (4 → 5) (scorecard_rt_trip_coverage)
No longer reported since 2026-07-31 (2 findings)
- Some live predictions disagree with the schedule by more than 30 minutes. (scorecard_rt_predictions_implausible)
- 4 of 14 sampled vehicle positions were far from their assigned route (worst: 1600 m). (scorecard_rt_vehicles_off_route)
This records the later feed state. It does not establish who made a change or why.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
7 findings, ordered by severity.
Show every finding
- 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. 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.)
Finding code: 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 lack rider-facing destination or direction text.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: 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.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning5 instances
5 of 5 trips scheduled during the sampling window had no live predictions.
Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.
Fix: Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. (A vendor data-mapping question.)
Finding code: scorecard_rt_trip_coverage · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Warning1 instance
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: 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.)
Finding code: 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.)
Finding code: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS 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 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 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, 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 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 200 checks over the last 34 days, with 4s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Live predictions vs schedule
92.3% of reported vehicle positions sat on or near the published route shape.
From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.
Clears the Google and Apple Maps four-week coverage bar. This feed has 517 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 96 / 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 50 / 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 30 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 64 / 100
- 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/towson-loop/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.