GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-09-18

City of Longview

Grade C · 73.6 / 100

First check for this agency, so there is no trend yet.

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

No category changes since the last check.

Top three things to fix

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

    Service data runs out in 12 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. 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. Schedule a feed re-export now so the new calendar is live well before the current one ends.

    This feed's service calendar runs out within the next 30 days. If a new feed isn't published before it ends, trip planners will drop your agency and riders will see no service.

    Effort: Usually a re-export from your scheduling software.

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 12 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 City of Longview team, Service data runs out in 12 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/city-of-longview/

Copy this note from the full scorecard.

NTD GTFS readiness: Needs attention

This feed is close to NTD-ready. Service data runs out in 12 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 12 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.

Key facts

Feed URL
https://cloud.longviewtexas.gov/maps/LongviewTransitGTFS/LongviewTransitGTFS.zip
Last checked
2026-09-18
Service window
12 days of service data remain. Last service date 2026-09-30.
Feed version
2.0
Location
Texas

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