Feed status · checked 2026-09-13
Ben Franklin Transit
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-09-12
Catalogued in Washington.
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 30 hours ago; last changed 11 days ago.
Measured 4 of 4 score categories from the feed URL on file (publisher not verified).
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 configured feed URL. Publisher ownership of that URL is not verified.
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
657 of 876 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 +19 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
13025 of 13025 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
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
- 657 of 876 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
- 13025 of 13025 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
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 for scorecard_wheelchair_boarding_unknown
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.
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 for scorecard_wheelchair_accessible_unknown
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.
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 for scorecard_no_fare_data
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 181 days.
- Published accessibility data
- Accessibility information is stated for 25% 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
- One or more realtime feeds were reachable; live-arrival coverage is not known.
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 4 kinds of issue across 6 instances (0 error, 1 warning, 5 informational).
Service data covers the next 181 days.
25% of stops state wheelchair accessibility (25% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
25% of stops state accessibility (25% 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 (67, 41).
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.
860 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Knight St Transit Center", "Goethals Dr at Swift Blvd", "Swift Blvd at Gilmore St", 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 configured feeds healthy; vehicle position plausibility was not measurable.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 876 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.
- 1 (gray)
- 10 (teal)
- 123 (orange)
- 123s (orange)
- 170 (yellow)
- 20 (red)
- 225 (pink)
- 240X (yellow)
- 25 (pink)
- 26 (teal)
- 26s (teal)
- 27X (yellow)
- 2X (yellow)
- 3 (gray)
- 3s (gray)
- 40 (pink)
- 41 (purple)
- 42 (teal)
- 47 (orange)
- 48 (blue)
- 50 (red)
- 60 (pink)
- 61 (red)
- 64 (pink)
- 64X (pink)
- 65 (orange)
- 65s (orange)
- 66 (teal)
- 67 (teal)
- 68 (blue)
- 68s (blue)
| Route | Type | Line color |
|---|---|---|
| 1 Metro Route 1 | Bus | gray |
| 10 Route 10 | Bus | teal |
| 123 Route 123 | Bus | orange |
| 123s Route 123s Overload Tripper | Bus | orange |
| 170 Route 170 | Bus | yellow |
| 20 Route 20 | Bus | red |
| 225 Route 225 | Bus | pink |
| 240X Express 240 | Bus | yellow |
| 25 Route 25 | Bus | pink |
| 26 Route 26 | Bus | teal |
| 26s Route 26s Overload Tripper | Bus | teal |
| 27X Express 27 | Bus | yellow |
| 2X Express 2 | Bus | yellow |
| 3 Metro Route 3 | Bus | gray |
| 3s Metro Route 3 Overload Tripper | Bus | gray |
| 40 Route 40 | Bus | pink |
| 41 Route 41 | Bus | purple |
| 42 Route 42 | Bus | teal |
| 47 Route 47 | Bus | orange |
| 48 Route 48 | Bus | blue |
| 50 Route 50 | Bus | red |
| 60 Route 60 | Bus | pink |
| 61 Route 61 | Bus | red |
| 64 Route 64 | Bus | pink |
| 64X Express 64 | Bus | pink |
| 65 Route 65 | Bus | orange |
| 65s Route 65s Overload Tripper | Bus | orange |
| 66 Route 66 | Bus | teal |
| 67 Route 67 | Bus | teal |
| 68 Route 68 | Bus | blue |
| 68s Route 68s Overload Tripper | Bus | blue |
List every stop
- 1st St at Alma Ave
- Babs Ave at 3rd St
- Babs Ave at 7th St
- 9th St at Ellen Ave
- Horne Dr at Grace Ave
- Hazel Ave at 13th St
- (FLAG STOP)Highland Rd at Breezie PR
- Highland Rd at Windy Ln
- Horne Drive at Irene Ave
- Horne Dr at Ida Ave
- Horne Dr at Grace Ave
- 9th St at Della Ave
- 9th St at Chris Ave
- Babs Ave at 2nd St
- 1st St at Abby Ave
- 9th St at BABS
- 9TH St at Chris Ave
- Three Rivers Transit Center
- Dayton Transfer Point
- Quinault Ave at Okanogan Pl
- Quinault Ave at Okanogan Pl
- Quinault Ave at Columbia Center Blvd
- Crosswind Blvd at Canal Dr
- Crosswind Blvd at Okanagan Pl
- Canal Dr at Crosswind Blvd
- Canal Dr at Kellogg St
- Canal Dr at Quinault St
- Edison St at Canal Dr
- Metaline Ave at Edison St
- Metaline Ave at Arthur St
- Volland St at Klamath Ave
- Fruitland St at Grand Ronde Ave
- Columbia Dr at Jean St
- Clearwater Ave at Hwy 395
- Metaline Ave at Volland St
- Metaline Ave at Arthur St
- Metaline Ave at Edison St
- Edison St at Okanogan Ave
- Canal Dr at Grant St
- Canal Dr at Grant St
- Canal Dr at Kellogg St
- Grandridge Blvd at Young St
- Columbia Center Blvd at Grandridge Blvd
- Columbia Center Blvd at Deschutes Ave
- Clearwater Ave at Colorado St
- Clearwater Ave at Colorado St
- Clearwater Ave at Taft St
- Clearwater Ave at Quay St
- Clearwater Ave at Kellogg St
- Clearwater Ave at Fillmore St
- Clearwater Ave at Edison St
- Clearwater Ave at Yost St
- Clearwater Ave at Union St
- Clearwater Ave at Morain St
- Clearwater Ave at Johnson St
- Vista Way at Hwy 395
- Kennewick Ave at Underwood St
- Kennewick Ave at Quincy St
- Garfield St at 5th Ave
- 1st Ave at Auburn St
- Washington St at Canal Dr
- Columbia Dr at Beech St
- Columbia Dr at Date St
- Columbia Dr at Cedar St
- Washington St at Canal Dr
- Washington St at 1st Ave
- Washington St at 5th Ave
- 6th Ave at Auburn St
- 6th Ave at Dayton St
- Kennewick Ave at Olympia St
- Kennewick Ave at Rainier St
- Kennewick Ave at Vancouver St
- Vista Way at Conway St
- Clearwater Ave at Huntington St
- Clearwater Ave at Johnson St
- Clearwater Ave at Morain St
- Clearwater Ave at Quillan St
- Clearwater Ave at Yost St
- Clearwater Ave at Arthur St
- Clearwater Ave at Fillmore St
- Clearwater Ave at Lincoln St / Mckinley St
- Clearwater Ave at Quay St
- Clearwater Ave at Taft St
- Clearwater Ave at Colorado St
- Columbia Center Blvd at Deschutes Ave
- Columbia Center Blvd at Grandridge Blvd
- Grandridge Blvd at Young St
- Young St at Grandridge Blvd
- Gage Blvd at Steptoe St
- Deschutes Ave at Belfair Ct
- Young St at Deschutes Ave
- Young St at Hood Pl
- Deschutes Ave at Belfair Ct
- Gage Blvd at Pittsburgh St
- Gage Blvd at Steptoe St
- Kennewick Ave at Hwy 395
- 10th Ave at Alder Pl
- 10th Ave at Date St
- Gum St at 10th Ave
- Gum St at 6th Ave
- Gum St at 4th Ave
- 3rd Ave at Date St
- 3rd Ave at Washington St
- Auburn St at 3rd Ave
- Auburn St at Keewaydin Dr
- 3rd Ave at Washington St
- 3rd Ave at Elm St
- Gum St at 4th Ave
- Gum St at 8th Ave
- 10th Ave at Date St
- 10th Ave at Beech St
- Washington St at 12th Pl
- Washington St at 15th Ave
- Washington St at 19th Ave
- 19th Ave at Dayton Pl
- Garfield St at 19th Ave
- 19th Ave at Kent St
- Olympia St at 20th Ave
- Olympia St at 22nd Pl
- Olympia St at 26th Ave
- Olympia St at 30th Ave
- Olympia St at Highland Pl
- Vancouver St at 36th Ave
- Vancouver St at 31st Ave
- Vancouver St at 26th Ave
- Vancouver St at 22nd Ave
- Vancouver St at 19th Ave
- Vancouver St at 15th Ave
- Vancouver St at 10th Ave
- Vancouver St at Tacoma St
- Kennewick Ave at Hwy 395
- Young St at Canal Dr
- Kellogg St at Rio Grande Ave
- Kellogg St at Lincoln St
- Kellogg St at Metaline Ave
- Kellogg St at Clearwater Ave
- Kellogg St at Kennewick Ave
- Kellogg St at 1st Ave
- 4th Ave at Jefferson St
- 4th Ave at Grant St
- 4th Ave at Dawes St
- 4th Ave at Volland St
- 4th Ave at Tweedt St
- 4th Ave at Quillan St
- 4th Ave at Morain St
- 4th Ave at Johnson St
- 4th Ave at Green Pl
- 4th Ave at Conway Pl
- 4th Ave at Zillah St
- 4th Ave at Yelm St
- 4th Ave at Tacoma St
- 4th Ave at Rainier St
- 4th Ave at Olympia St
- 4th Ave at Kent St
- 4th Ave at Garfield St
- 4th Ave at Carmichael Dr
- 4th Ave at Kent St
- 4th Ave at Olympia St
- 4th Ave at Tacoma St
- 4th Ave at Vancouver St
- 4th Ave at Buntin St
- 4th Ave at Dennis St
- 4th Ave at Green St
- 4th Ave at Huntington Pl
- 4th Ave at Morain St
- 4th Ave at Quillan St
- 4th Ave at Tweedt St
- 4th Ave at Williams St
- 4th Ave at Dawes St
- 4th Ave at Edison St / Fillmore St
- 4th Ave at Harrison St / Irving St
- Kellogg St at Kennewick Ave
- Kellogg St at Clearwater Ave
- Kellogg St at Metaline Ave
- Kellogg St at Quinault Ave
- Kellogg St at Rio Grande Ave
- Canal Dr at Young St
- Young St at Canal Dr
- Kennewick Ave at Johnson St
- Kennewick Ave at Reed St
- Kennewick Ave at Tweedt St
- Union St at 4th Ave
- Union St at 7th Ave (WEST)
- Union St at 9th Ave
- Union St at 12th Ave
- Union St at 15th Ave
- Union St at 24th Ave
- Union St at 26th Ave
- Southridge Blvd at Hildebrand Blvd
- Hildebrand Blvd at Plaza Way
- 27th Ave at Yelm St
- 27th Ave at Tacoma St
- 27th Ave at Quincy St
- 27th Ave at Kent St
- 27th Ave at Jean St
- Garfield St at 24th Ave
- Garfield St at 20th Ave
- Garfield St at 16th Ave
- Garfield St at 11th Ave
- Garfield St at 18th Ct
- (FLAG STOP)Garfield St at 24th Ave
- Garfield St at 26th Ave
- 27th Ave at Jean St
- 27th Ave at Quincy St
- 27th Ave at Tacoma St
- 27th Ave at Zillah St
- Southridge Blvd at Hildebrand Blvd
- Union St at 24th Ave
- Union St at 21st Ave
- Union St at 15th Ave
- Union St at 12th Ave
- Union St at 9th Ave
- Union St at 7th Ave
- Union St at 3rd Ave
- Kennewick Ave at Tweedt St
- Kennewick Ave at Perry St
- Kennewick Ave at Irby St
- Southridge Blvd at Southridge High School
- Columbia Center Blvd at Clearwater Ave
- Columbia Center Blvd at 4th Ave
- Columbia Center Blvd at 7th Ave
- 10th Ave at Wilson Ct
- 10th Ave at Roosevelt St
- 10th Ave at Osborne St
- 10th Ave at Jefferson St
- (FLAG STOP)10th Ave at Irving St
- 10th Ave at Edison St
- 10th Ave at Arthur St
- 10th Ave at Union St
- 10th Ave at Morain St
- 10th Ave at Irby St
- 19th Ave at Huntington Pl
- 19th Ave at Ely St
- 10th Ave at 9th Pl
- 10th Ave at Vancouver St
- 10th Ave at Quincy Pl
- 10th Ave at Newport St
- 10th Ave at Hartford St
- 10th Ave at Garfield St
- 10th Ave at Heatherstone Apts
- 10th Ave at Olympia St
- 10th Ave at Vancouver St
- 10th Ave at 8th Pl
- 19th Ave at Ely St
- 19th Ave at Hwy 395
- 10th Ave at Huntington St
- 10th Ave at Morain St
- 10th Ave at Union St
- 10th Ave at Arthur Pl
- 10th Ave at Edison St
- and 626 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 6 checks — unchanged since 2026-09-12.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 72.3 | first check |
| 2026-08-07 | 71.9 | down 0.4 |
| 2026-08-10 | 70.1 | down 1.8 |
| 2026-09-01 | 84.1 | up 14.0 |
| 2026-09-12 | 85.9 | up 1.8 |
| 2026-09-13 | 85.9 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality no change
What changed over time
On 2026-08-06 this feed started at grade C. On 2026-09-01 the grade moved from C to B. On 2026-09-13 the check no longer reported: this feed's service calendar runs out within the next 30 days; service data runs out in 22 day(s); 1 of 48 trips scheduled during the sampling window had no live predictions. As of 2026-09-13 it holds grade B.
A plain-language history of this feed, newest first.
- 2026-09-01 Grade went C to B, freshness rose 68 points.
Everything we checked
7 findings, ordered by severity.
Show every finding
- Warning13025 instances
13025 of 13025 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning657 instances
657 of 876 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide for trip_coverage_not_active_for_next7_days · 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 for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info3 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide for big_gap_in_service · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Future calendar (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'future_calendar' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: future_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Future feed (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'future_feed' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: future_feed · 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 181 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 13025 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
One requirement remains for this feed to earn the conformance mark. States wheelchair access on 25% 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 181 days.
- Accessible Not yet
- States wheelchair access on 25% 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 in the 31 days to 2026-09-15, with 18s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment. The window ends at the newest observation, which is not always today: if the monitor stops, this window stops with it.
Clears the Google and Apple Maps four-week coverage bar. This feed has 179 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.
A local transit-data support resource is WSDOT Transportation Data. WSDOT builds and publishes GTFS for Washington transit agencies. This resource supports agencies; it is not a scoring authority.
- Correctness 94 / 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 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. FTA NTD readiness also checks that the published feed is current.
- Rider experience 51 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 100 / 100
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Part of the Washington portfolio: the same scorecards for every feed we track in that group, on one free page.
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/ben-franklin-transit-2122/2026-09-13.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-09-13. 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.