Call-prep brief · checked 2026-07-09
Dallas Host Committee
Grade F · 53.8 / 100
Down 0.4 points since 2026-07-08 (F to F).
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 down 1.7
- Rider experience no change
Top three things to fix
Re-export with a validity window that reaches at least 60 days out.
Service data runs out in 5 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Effort: One export setting.
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
2 of 2 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.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).
12 of 12 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Effort: Often one default setting in your export.
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Ready to send to the agency
Hi Dallas Host Committee team, Service data runs out in 5 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice. The fix is usually one export setting: Re-export with a validity window that reaches at least 60 days out. 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/dallas-host-committee/
NTD certification readiness: Needs attention
This feed is close to NTD-ready. Service data runs out in 17 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 17 days; renew before you certify.
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.
Key facts
- Feed URL
- https://d2igk3wxwksqfb.cloudfront.net/dallashostcommitteedata.zip
- Last checked
- 2026-07-09
- Service window
- 5 days of service data remain. Last service date 2026-07-14.
- Feed version
- JUNE_2026_20260608_1
- State
- Texas
Part of the Texas 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.