GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-08-01

Long Beach Transit (LBT)

Grade F · 28.3 / 100

Down 0.4 points since 2026-07-31 (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 21 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.

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

    Trip distance exceeds shape distance (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

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

    Equal shape distance diff coordinates (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

Finding handoff

Move one finding to a recheck

Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.

Feed evidence
Service data runs out in 21 day(s).
Next action
Re-export with a validity window that reaches at least 60 days out.
Recheck
Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text

Ready to send to the agency

Hi Long Beach Transit (LBT) team, Service data runs out in 21 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/long-beach-transit-lbt/

Copy this note from the full scorecard.

NTD GTFS readiness: Needs attention

This feed is close to NTD-ready. 2 validator errors to resolve. Service data runs out in 21 days; renew before you certify.

Published Ready
Published at a public URL.
Valid Needs attention
2 validator errors to resolve.
Current Needs attention
Service data runs out in 21 days; renew before you certify.
agency_id provided Ready
agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.

agency_id equals NTD ID (optional): Not checked yet. This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.

The bar this score answers to

The published guideline in California is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.

Key facts

Feed URL
https://drive.google.com/uc?export=download&id=1869EVa1z6m_iD6QmvRXyTHtYiaSUBROl
Last checked
2026-08-01
Service window
21 days of service data remain. Last service date 2026-08-22.
Location
California

Part of the California 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.3, validator 8.0.1.