← Back to the full scorecard

Call-prep brief · checked 2026-07-09

Detroit Department of Transportation (DDOT)

Grade F · 36.0 / 100

Unchanged since 2026-07-08.

For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. Each fix is framed as a next step, not a failure.

What changed since the last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change

Top three things to fix

  1. Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.

    Service data ended 6 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.

    Effort: Usually one export setting; export on a schedule so it never lapses again.

    Agencies here usually clear this within about 1 week (based on 18 observed fixes).

  2. Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Block trips with overlapping stop times (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

    Agencies here usually clear this within about 1 week (based on 5 observed fixes).

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

    5120 of 5120 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.

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

Ready to send to the agency

Hi Detroit Department of Transportation (DDOT) team, Service data ended 6 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. The fix is usually one export setting: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/detroit-department-of-transportation-ddot/

Copy this note from the full scorecard.

NTD certification readiness: Not ready

Resolve this before you certify on the D-10. 1 validator error to resolve. Service data expired 5 days ago, so FTA would find the link out of date.

Published Ready
Published at a public URL.
Valid Needs attention
1 validator error to resolve.
Current Not ready
Service data expired 5 days ago, so FTA would find the link out of date.

agency_id and 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.

The bar this score answers to

The state transit-data program is Michigan Public Transit Open Data Program. MDOT's program helping agencies produce and maintain GTFS and GTFS-Flex.

Key facts

Feed URL
https://www.detroitmi.gov/Portals/0/docs/deptoftransportation/pdfs/ddot_gtfs.zip
Last checked
2026-07-09
Service window
Feed has expired. Last service date 2026-07-12.
Feed version
S1000180
State
Michigan

Part of the Michigan portfolio: see where this agency sits among the state's feeds before the call.

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.1, validator 8.0.1.