← Back to the full scorecard

Call-prep brief · checked 2026-07-09

Long Island Rail Road

Grade C · 79.5 / 100

Down 0.4 points since 2026-07-08 (C to C).

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. Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).

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

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

  3. Remove retired stops from the export, or add them back to the trips that should serve them.

    Some stops exist in the feed but no trip ever stops at them. Riders may walk to a stop where no bus is scheduled to arrive.

    Effort: A review pass in your scheduling software.

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

NTD certification readiness: Ready

Published at a public URL, valid, and current: the three things the NTD GTFS requirement asks of a feed all hold here. Only your own D-10 certification makes that official; this is a heads-up, not a determination.

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

agency_id and NTD ID: Not aligned. Your feed's agency_id is LI; your National Transit Database ID is 20100. 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 20100 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://rrgtfsfeeds.s3.amazonaws.com/gtfslirr.zip
Last checked
2026-07-09
Service window
38 days of service data remain. Last service date 2026-08-16.
Feed version
2026-07-02T12:06:00

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