← Back to the full scorecard

Board packet · transit data quality · checked 2026-11-09

DC Streetcar

Grade C · 76.3 / 100 · partial: freshness not measured

The scoring methodology changed since the prior check; the trend restarts here without an improvement or regression claim.

Scored from a Mobility Database mirror copy downloaded on 2026-10-19, because the feed URL on file could not be downloaded. Service dates in that copy run 2023-07-01 to 2025-06-30. It may not match the feed the agency publishes today.

What this grade measures

The quality of the schedule data in the feed scored here for trip-planning apps: whether riders using Google Maps, Apple Maps, or Transit see current, correct, and complete information. It measures the data feed, not service quality or operations.

Progress this period

No newly cleared items this period. The score and trend above reflect the mirror copy described above, which may not match the feed the agency publishes today.

What needs attention next

Three improvements, in priority order, each sized so the board can see what it is approving:

  1. Check that https://mjcaction.com/MJC_GTFS_Public/dcstreetcar_gtfs.zip still serves your current feed. If the feed moved, publish the new address.

    The feed URL on file, https://mjcaction.com/MJC_GTFS_Public/dcstreetcar_gtfs.zip, could not be downloaded: the server answered with an error instead of the file. Trip planners download the feed from that address too. The grade here was measured on an older Mobility Database copy whose service ended 2025-06-30, so freshness is not graded until the current feed can be downloaded.

    This one is about the feed as a whole, so there is no share of it to count.

    Estimated effort: Usually a server or hosting setting, not a change to the feed itself.

  2. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

    15 of 15 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 15 stops in the feed.

    Estimated effort: A column in stops.txt; your scheduling software likely has it.

  3. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.

    383 of 383 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the transit vehicle itself can take them.

    Fixing this covers all 383 trips in the feed.

    Estimated effort: A default or per-trip field in your export.

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-11-02.

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.

Feed evidence
The feed URL on file, https://mjcaction.com/MJC_GTFS_Public/dcstreetcar_gtfs.zip, could not be downloaded: the server answered with an error instead of the file.
Next action
Check that https://mjcaction.com/MJC_GTFS_Public/dcstreetcar_gtfs.zip still serves your current feed. If the feed moved, publish the new address.
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

Produced by the GTFS Scorecard, an open-source data quality tool. A data-quality read to support the board conversation, not an official compliance determination. Live scorecard: https://gtfsscorecard.org/agency/dc-streetcar-2223/. Rubric v1.4, validator 8.0.1.