Feed status · checked 2026-10-07
Service Discontinued
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-10-06
Cataloged in District of Columbia.
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.4, validator 8.0.1.
Checked for changes 3 hours ago; last changed 105 days ago.
Measured 3 of 4 score categories from the feed URL on file (publisher not verified).
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 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.
About this feed
Service Discontinued’s published feed lists 7 bus routes, 7,721 scheduled trips and 146 stops. Its service dates run from 2021-10-03 through 2022-04-02. The published file has not changed since our first check on 2026-06-19.
Top things to fix
Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change.Likely your export tool
Service data ended 1649 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
This one is about the feed as a whole, so there is no share of it to count.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 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
146 of 146 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.
Fixing this covers all 146 stops in the feed.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 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.
This one is about the feed as a whole, so there is no share of it to count.
⏱ A small file for most flat-fare systems.worth about +15 points in its category
Riders and need behind these fixes
- This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
- District of Columbia as a whole measures moderate on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-10-05.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
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.
- Finding
- Fix 01 in Top things to fix: its feed evidence and the requested change.
- 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
- Finding
- Fix 02 in Top things to fix: its feed evidence and the requested change.
- 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
- Finding
- Fix 03 in Top things to fix: its feed evidence and the requested change.
- 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.
Fix 01 · Read the fix guide for scorecard_feed_expired
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.
Fix 02 · 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. Self-check a feed before you publish.
Fix 03 · 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. 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 was 1649 days ago.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 16.2% 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.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 9 kinds of issue across 6171 instances (0 error, 6169 warning, 2 informational).
Service data ended 1649 day(s) ago. Trip planners have likely already dropped this feed.
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
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (GT-US, NMS, RS-DP, WP-AM).
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.
134 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Martin Luther King Jr Ave and W Street SE (NB)", "Martin Luther King Jr Ave and W Street SE (SB)", "M Street and 4th Street SE (EB)", 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.
This feed has 146 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.
- CH-US (white)
- EM-LP (white)
- GT-US (white)
- NMS (white)
- RS-DP (white)
- WP-AM (white)
| Route | Type | Line color |
|---|---|---|
| 9999 Test Route | Bus | white (no shape in feed) |
| CH-US Congress Heights – Union Station | Bus | white |
| EM-LP Eastern Market – L’Enfant Plaza | Bus | white |
| GT-US Georgetown – Union Station | Bus | white |
| NMS National Mall Route | Bus | white |
| RS-DP Dupont Circle – Rosslyn | Bus | white |
| WP-AM Woodley Park – Adams Morgan – McPherson Square | Bus | white |
List every stop
- 35th Street and Wisconsin Avenue NW (SB)
- K Street and 13th Street NW (EB)
- 19th Street and N Street NW (SB)
- M Street and 24th Street NW (WB)
- M Street and 28th Street NW (WB)
- 15th Street and Madison Drive NW (SB)
- 15th Street and Jefferson Drive SW (SB)
- 3rd Street near Madison Drive NW (NB)
- Constitution Avenue and 18th Street NW (EB)
- E St and Columbus Circle NE (Union Station) (EB)
- East Basin Drive SW at Jefferson Memorial (WB)
- Jefferson Drive and 12th Street SW (EB)
- Jefferson Drive and 7th Street SW (EB)
- L Street and 24th Street NW (WB)
- Lincoln Memorial Circle SW (WB)
- Madison Drive and 4th Street NW (WB)
- Madison Drive and 7th Street NW (WB)
- Madison Drive and 12th Street NW (WB)
- Massachusetts Avenue and 7th Street NW (EB)
- Massachusetts Avenue and 5th Street NW (EB)
- Massachusetts Avenue and 5th Street NW (WB)
- 15th Street near Maine Avenue SW (SB)
- Union Station Parking Garage
- West Basin Drive near Independence Avenue SW (NB)
- Rosslyn Metro Station
- M Street and 4th Street SE (EB)
- M Street and New Jersey Avenue SE (EB)
- Stanton Road and Alabama Ave SE
- Stanton Road and Bruce Place SE
- Stanton Road and Elvans Road SE
- Stanton Road and Pomeroy Road SE
- Stanton Road and Douglass Road SE
- Stanton Road and Washington View Apts
- Sheridan Road and Bowen Road SE
- M Street and Delaware Ave SW
- M Street and 4th Street SW
- M Street and 4th Street SE (WB)
- M Street and Half Street SE
- M Street and Delaware Ave SW
- 7th Street and I Street SW
- 8th Street and E Capitol NE
- Pennsylvania Avenue and 22nd Street NW
- K Street and 14th Street NW
- 14th Street and U Street NW
- Calvert Street and Lanier Pl NW
- Anacostia Station Bus Bay F
- M Street and Half Street SE
- 8th Street and L Street SE (NB)
- Congress Heights Bus Bay G
- Stanton Road and Bryan Place SE
- D Street and 7th Street SW
- M Street and 4th Street SW
- 8th Street and L Street SE
- Martin Luther King Jr Ave and Good Hope Road SE
- 11th Street and O Street NE
- 7th Street and I Street SW
- Maine Avenue and 7th Street SW
- Stanton Road and Alabama Ave SE
- Stanton Road and Bruce Place SE
- Stanton Road and Elvans Road SE
- Sheridan Road and Bowen Road SE
- Martin Luther King Jr Ave and U Street SE
- 8th Street and G Street SE (NB)
- 8th Street and E Capitol NE
- Stanton Road and Washington View Apts
- Stanton Road and Pomeroy Road SE
- 11th Street and O Street NE
- Test Route Start
- Test Stop 1
- Test Stop 2
- Test Stop 3
- 8th Street and G Street SE (SB)
- Test Route End
- Maine Avenue and 7th Street SW
- 8th Street and E Street SE (NB)
- 8th Street and D Street SE (SB)
- Pennsylvania Avenue and 8th Street SE (EB)
- Pennsylvania Avenue and 7th Street SE (WB)
- Constitution Avenue and 21st Street NW (EB)
- Massachusetts Avenue and First Street NE (EB)
- N Capitol Street and Massachusetts Avenue NW (SB)
- Massachusetts Avenue and New Jersey Avenue NW (EB)
- Massachusetts Avenue and New Jersey Avenue NW (WB)
- North Capitol Street and H Street NE (NB)
- Pennsylvania Avenue and 21st Street NW (EB)
- I Street and 14th Street NW (WB)
- Pennsylvania Avenue and 22nd Street NW (EB)
- 14th Street and K Street NW (NB)
- K Street and 19th Street NW (EB)
- K Street and 14th Street NW (EB)
- K Street and 16th Street NW (EB)
- K Street and 17th Street NW (EB)
- K Street and 19th Street NW (WB)
- K Street and Connecticut Avenue NW (WB)
- K Street and 16th Street NW (WB)
- 13th Street and K Street NW (SB)
- Pennsylvania Avenue and 24th Street NW (EB)
- Pennsylvania Avenue and 26th Street NW (EB)
- M Street and 34th Street NW (WB)
- Pennsylvania Avenue and 28th Street NW (WB)
- M Street and Potomac Street NW (WB)
- M Street and Wisconsin Avenue NW (EB)
- M Street and Thomas Jefferson Street NW (EB)
- M Street and 30th Street NW (WB)
- M Street and 31st Street NW (WB)
- New Hampshire Avenue and M Street NW (SB)
- Wisconsin Avenue and N Street NW (SB)
- Wisconsin Avenue and Dumbarton Street NW (NB)
- Wisconsin Avenue and P Street NW (NB)
- 14th Street and Rhode Island Avenue NW (NB)
- Wisconsin Avenue and P Street NW (SB)
- 14th Street and P Street NW (SB)
- Wisconsin Avenue and Q Street NW (NB)
- Wisconsin Avenue and Q Street NW (SB)
- Wisconsin Avenue and R Street NW (NB)
- Wisconsin Avenue and R Street NW (SB)
- Martin Luther King Jr Ave and W Street SE (NB)
- Wisconsin Avenue and 34th Street NW (NB)
- Wisconsin Avenue and 34th Street NW (SB)
- 14th Street and U Street NW (NB)
- Columbia Road and Ontario Road NW (EB)
- Connecticut Avenue and 24th Street NW (SB)
- Columbia Road and Ontario Road NW (WB)
- Columbia Roat and 16th Street NW (WB)
- Columbia Road and 14th Street NW (WB)
- Mount Pleasant Street and Irving Street NW (NB)
- M Street and New Jersey Avenue SE (WB)
- Martin Luther King Jr Ave and W Street SE (SB)
- Irving Street and 14th Street NW (WB)
- M Street and Wisconsin Avenue NW (WB)
- M Street and 33rd Street NW (WB)
- 600 M Street SE (Navy Yard Entrance) (WB)
- Wisconsin Avenue and M Street NW (NB)
- K Street and 11th Street NW (EB)
- Massachusetts Avenue and 7th Street NW (WB)
- New York Avenue and 9th Street NW (EB)
- 600 M Street SE (Navy Yard Entrance) (EB)
- New York Avenue and 9th Street NW (WB)
- Adams Mill Road and Columbia Road NW (WB)
- Mass. Avenue and Columbus Cir (Union Station) (WB)
- New Hampshire Avenue and M Street NW (NB)
- K Street and 13th Street NW (WB)
- 21st Street and K Street NW (SB)
- K Street and 24th Street NW (WB)
- Lower K Street and 30th Street NW (WB)
- Lower K Street and Wisconsin Avenue NW (WB)
Over time
Overall score across the last 2 checks — unchanged since 2026-10-06.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-10-06 | 39.4 | first check |
| 2026-10-07 | 39.4 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Feed history
Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-10-06 to 2026-10-07 (2 checks) | d46701460bee | 2022-04-02 | Current rubric: see the trend above |
| 2026-08-06 to 2026-09-13 (4 checks) | d46701460bee | 2022-04-02 | F, 39.4 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-06-19 to 2026-07-10 (21 checks) | d46701460bee | 2022-04-02 | F, 39.4 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
What changed in this feed
Overall grade and score held steady since 2026-10-06.
Same feed file as 2026-10-06; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
Everything we checked
14 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 1649 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Finding code: scorecard_feed_expired · Read the fix guide for scorecard_feed_expired · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning6471 instances
6471 of 7721 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)
- Warning6152 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 for mixed_case_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning146 instances
146 of 146 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)
- Warning7 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide for expired_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 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 for stop_without_stop_time · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date7_days · Read the fix guide for feed_expiration_date7_days · 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 for missing_feed_contact_email_and_url · 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 for route_color_contrast · See MobilityData GTFS Validator rules (opens the validator rules 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 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 for unused_shape · 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)
- Info2 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · Read the fix guide for unknown_file · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. Service data expired 1649 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- Service data expired 1649 days ago, so FTA would find the link out of date.
- 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 7721 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
Two requirements remain for this feed to earn the conformance mark. Service data expired 1649 days ago. States wheelchair access on 0% of stops and 16% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 1649 days ago.
- Accessible Not yet
- States wheelchair access on 0% of stops and 16% 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 5 of 146 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.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.
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 62 / 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 0 / 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 40 / 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.
Part of the District of Columbia portfolio: the same scorecards for every feed we track in that group, on one free page.
For programs that support several agencies
This scorecard and the board one-pager for Service Discontinued are free, and they stay free. If you support several agencies, as a state program, a technical-assistance center, a feed vendor, or a consultancy, you can buy the program report bundle. It puts this agency's board report in one archive with the reports for the other agencies you support, and each cover carries your program's name, logo, and accent color.
The report for Service Discontinued uses the same numbers as this page: grade F (39.4 out of 100) as of the check on 2026-10-07, its category scores, its top fixes, and its score at each check.
One bundle, up to 25 agencies: $149, paid once, delivered within 2 business days or refunded. Other plans, including a monthly refresh, are on the bundle page.
See a sample bundle report: a real agency's current grade, with placeholder branding.
A purchase buys no influence over grades, methodology, or which agencies are listed. The grade on this page comes from the check on 2026-10-07, scored with rubric v1.4 and MobilityData gtfs-validator 8.0.1. Based on the feed source on file; publisher ownership is not verified. Read how the grade is calculated.
Similar feeds in District of Columbia
Other scorecards in District of Columbia, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
Show your grade
Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.
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/dc-circulator/2026-10-07.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-10-07. 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.