← Back to the full scorecard

Call-prep brief · checked 2026-07-09

GoTriangle

Grade F · 54.6 / 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

  1. Re-export with a validity window that reaches at least 60 days out.

    Service data runs out in 23 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).

  2. Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).

    1569 of 1569 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).

  3. 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.

    Effort: A small file for most flat-fare systems.

Ready to send to the agency

Hi GoTriangle team, Service data runs out in 23 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/gotriangle-3183/

Copy this note from the full scorecard.

NTD certification readiness: Ready

This feed looks ready for your NTD certification: published at a public URL, valid, and current. The official check is still your D-10 certification.

Published Ready
Published at a public URL.
Valid Ready
Passes validation with no errors.
Current Ready
Service data covers the next 35 days.

agency_id and NTD ID: Not aligned. Your feed's agency_id is f42c368f-0d16-403f-9c7c-493c9beb84ef; your National Transit Database ID is 40108. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id, so a difference here is a heads-up, not an error. Optionally set the agency_id for your service to 40108 in agency.txt (and the matching agency_id in routes.txt) so the feed lines up with your NTD record. It is a convenience, not a required feed change: FTA also links agency_id to your NTD ID on your P-50 form.

Key facts

Feed URL
http://gotriangle.org/gtfs
Last checked
2026-07-09
Service window
23 days of service data remain. Last service date 2026-08-01.
Feed version
2026-03 service V1

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