GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-09

Bus

Grade F · 36.4 / 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-generate shape distances in your export; flag to your vendor if it persists.

    Some trips have stop times whose distances along the route go backwards. Apps can show buses jumping backwards or mis-order stops.

    Effort: Usually an export-tool fix, not hand editing.

  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.

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

NTD certification readiness: Needs attention

This feed is close to NTD-ready. 2 validator errors to resolve.

Published Ready
Published at a public URL.
Valid Needs attention
2 validator errors to resolve.
Current Ready
Service data covers the next 178 days.

agency_id and NTD ID: Not aligned. Your feed's agency_id is NJB; your National Transit Database ID is 20080. 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 20080 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
https://www.njtransit.com/bus_data.zip
Last checked
2026-07-09
Service window
169 days of service data remain. Last service date 2026-12-25.
State
New Jersey

Part of the New Jersey 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.