← All agencies

Feed status · checked 2026-11-02

City of Longview

Based on the official feed source on file

Service mode Bus

FDCBA

68.6 / 100

unchanged since 2026-11-01

Cataloged in Texas.

Feed expiredRealtime not yet published

Source feed: https://cloud.longviewtexas.gov/maps/LongviewTransitGTFS/LongviewTransitGTFS.zip Version history on the Mobility Database

A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.4, validator 8.0.1.

Checked for changes 6 hours ago; last changed 45 days ago.

Measured 3 of 4 score categories from the official feed URL on file.

How we measured this

Confidence in this measurement: medium.

Realtime quality was not measured this run. It does not count against the grade.
The feed was downloaded from the official feed URL on file.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

About this feed

City of Longview’s published feed lists 6 bus routes, 162 scheduled trips and 123 stops. Its service dates run from 2020-04-08 through 2026-09-30. The published file has not changed since our first check on 2026-09-18.

Top things to fix

Fix 01

Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change.Likely your export tool

Service data ended 33 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.

This one is about the feed as a whole, so there is no share of it to count.

⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category

Fix 02

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.

This one is about the feed as a whole, so there is no share of it to count.

⏱ A small file for most flat-fare systems.worth about +15 points in its category

Fix 03

Schedule a feed re-export now so the new calendar is live well before the current one ends.Likely your export tool

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.

This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

⏱ Usually a re-export from your scheduling software.worth about +4 points in its category

Riders and need behind these fixes

This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
Texas as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-11-02.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

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.

Finding: Fix 01 in Top things to fix: its feed evidence and the requested change.
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

Agency: City of Longview
Finding: scorecard_feed_expired
Feed evidence: Service data ended 33 day(s) ago.
Why it matters: When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Requested change: Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change.
Recheck: Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Evidence: https://gtfsscorecard.org/agency/city-of-longview/?finding=scorecard_feed_expired#finding-handoff

How to make and check these changes

Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.

Fix 01 · Read the fix guide for scorecard_feed_expired
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Fix 02 · Read the fix guide for scorecard_no_fare_data
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Fix 03 · Read the fix guide for feed_expiration_date30_days
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility: The feed's last published service date was 33 days ago.
Published accessibility data: Accessibility information is stated for 100% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information: No fare information is published in the feed.
Realtime information: Realtime-feed availability and live-arrival coverage are not known from this scorecard.

Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.

Send your vendor a fix request

You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.

Hi,

Our GTFS feed (City of Longview) scored D (68.6 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change.
   What: Service data ended 33 day(s) ago.
   Finding code: scorecard_feed_expired
   Guide: https://gtfsscorecard.org/fix/scorecard_feed_expired/

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.
   What: The feed contains no fare information.
   Finding code: scorecard_no_fare_data
   Guide: https://gtfsscorecard.org/fix/scorecard_no_fare_data/

3. Schedule a feed re-export now so the new calendar is live well before the current one ends.
   What: This feed's service calendar runs out within the next 30 days.
   Finding code: feed_expiration_date30_days
   Guide: https://gtfsscorecard.org/fix/feed_expiration_date30_days/

Full scorecard: https://gtfsscorecard.org/agency/city-of-longview/

Send the agency a note

Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.

Hi City of Longview team,

Service data ended 33 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.

The fix is usually one export setting: Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change.

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/

Score by category

Correctness96.0 / 100

The MobilityData validator flagged 1 kind of issue across 1 instance (0 error, 1 warning, 0 informational).

Freshness0.0 / 100

Service data ended 33 day(s) ago. Trip planners have likely already dropped this feed.

Rider experience85.0 / 100

100% of stops state wheelchair accessibility (100% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.

Accessibility100 / 100

100% of stops state accessibility (100% marked accessible). Reflects what the feed states, not verified physical usability.

Realtime qualityNot yet measured

Not scored yet. Nothing here counts against the grade.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

This feed has 123 stops.

The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

BLUE (green)
RED (green)
ORANGE (green)
PURPLE (green)
YELLOW (green)
GREEN (green)

Routes in City of Longview's feed
Route	Type	Line color
BLUE Mobberly/LeTourneau University	Bus	green
RED Medical District/Longview HS	Bus	green
ORANGE Pine Tree/Spring Hill	Bus	green
PURPLE East Marshall/Alpine	Bus	green
YELLOW Loop 281/Silver Falls	Bus	green
GREEN MLK/South Eastman	Bus	green

List every stop

Walmart Supercenter On Gilmer Rd
Across From Colony Park Apartments
City Hall & Longview Public Library
Kroger
Booshay'S & Patterson Truck Stop
Christus Good Shepherd South Of Marshall Av
Wellness Pointe On Marshall W Of Teague
Churchill At Longview Apts
Jalapeno Tree
Texas Health And Human Services
Sam'S Club And Walmart
Se Corner Of Fourth St & Hollybrook Dr
Across From South Ward Park
W Side Of Mobberly Av, N Of Birdsong St
Letourneau University
Us Post Office On S Mobberly Av
Highland Village Apartments
South Side Wal-Mart
Donut Delux, Across From Knights Inn
Workforce Solutions
Super 1 Foods - S High St
La Michoacana
Kilgore College Longview
Quadrangle Medical Offices
Texas Oncology-Longview Cancer Center
W Side Of Pine Tree At Evergreen St
West Entrance, Maude Cobb Convention Center
Brookshire'S & Jucy'S Hamburgers
Zippy J'S - S High St @ Marion Dr
Townhouse South Apartments
Hillside Village Apts
Across From Cedar Ridge Apartments
Burger King, Across From Longview Mall
Across From Northloop Plaza
Ihop & Marketplace Shopping Center
Oak Forest Plaza Ii Shopping Center
Drug Emporium & Super 1 Foods
Crestview Apartments
S Side Of Sapphire St, E Of Mlk Bl
Mill Creek Village Apartments
Rollins Park
Lisd Education Support Center
W Side Of S Eastman Rd, N Of I-20
Fire Station 3; Across From Foster Middle School
Across From Regency Park Apartments
Waffle House
Perry Clay Cemetery
Jack In The Box - 1-20 Near Estes Pkwy
Chaparral Plaza Shopping Center
Christus Trinity Clinic
Flewellen Park
Burlington Coat Factory
Longview High School Athletics
Christus Good Shepherd North Parking Lot
Across From Va Clinic
O'Reilly Auto Parts, W Side Of Alpine Rd
Sw Corner Of Alpine Rd And Eden Dr
Ware Elementary School
Ware Meadows Apts
W Side Of S High St, N Of W Potter St
Across From Kilgore College Longview
Across From Us Post Office On S Mobberly Av
Nw Corner Of Mobberly Av & E Highland Av
Dollar General - S High St
E Side Of High St, N Of Nelson St
Family Dollar - S High St
E Side Of Mobberly, S Of E Cotton St
Sw Corner Of Mlk Bl And Young St
Village South Apartments
Across From Los Papagallo'S Restaurant
W Side Of Mobberly, N Of E Cotton St
Neiman Marcus Service Center
2411 S Eastman Rd
Across From Broughton Park
S Side Of W Marshall Av, W Of W Methvin St
Triple Creek Shopping Center
Across From Chaparral Plaza Shopping Center
Across From Parkway Gardens Apartments
Tele'S Mexican
Oak Forest Center
China King & Shopping Center With Best Buy
Homewood Suites
Se Corner Of Whitney St And Bates St
N Side Of Young St, E Of Mlk Bl
Sw Corner Of Mlk Bl And Millie St
E Side Of Lilly St, N Of Wilburn St
E Side Of Bates St, N Of Sapphire St
Vista College & Securecare Self Storage
N Side Of W Marshall Av, E Of N Lane Wells Dr
Se Corner Of Silver Falls Rd And Spring St
E Side Of Silver Falls Rd, S Of Jester Ci
Burger King - W Loop 281
Hidden Hills Apartments
E Side Of Gilmer Rd, N Of W Marshall Av
Across From Christus Trinity Clinic
E Side Of Gilmer Rd At Preston Dr
Cvs & Chik-Fil-A
E Side Of Gilmer, S Of Birdwell Ln
Nw Corner Of Clyde St And Tammy Lynn Dr
Sw Corner Of Tammy Lynn Dr And Denson Dr
North Entrance, Maude Cobb Convention Center
Across From Longview Square Apartments
Pegues-Hurst Ford
S Side Of W Marshall Av, W Of Enterprise St
Magrill Park (Padon St & First St)
Sylvan & Mlk
Jaycee & Hwy 31
Institute Of Healthy Living
Oak Creek & Mccann
Tenneryville Rd & Pine Tree Rd
Huntington Hills Apts
Target And N Eastman Rd
Golden Corral On Loop 281
Marshall & Alpine (Super 1)
Teague & Marshall
Ridgecrest & Mlk
Eugene & Ridgecrest
Twelfth & Raney
Longview Transit Terminal
Westminster Place
Across From Medical Cl Before Intersection
By Entrance Of Davita Dialysis Center
In Front Of Spur 63 Whataburger

Over time

Overall score across the last 32 checks — unchanged since 2026-11-01.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-10-02	68.6	first check
2026-10-03	68.6	no change
2026-10-04	68.6	no change
2026-10-05	68.6	no change
2026-10-06	68.6	no change
2026-10-07	68.6	no change
2026-10-08	68.6	no change
2026-10-09	68.6	no change
2026-10-10	68.6	no change
2026-10-11	68.6	no change
2026-10-12	68.6	no change
2026-10-13	68.6	no change
2026-10-14	68.6	no change
2026-10-15	68.6	no change
2026-10-16	68.6	no change
2026-10-17	68.6	no change
2026-10-18	68.6	no change
2026-10-19	68.6	no change
2026-10-20	68.6	no change
2026-10-21	68.6	no change
2026-10-22	68.6	no change
2026-10-23	68.6	no change
2026-10-24	68.6	no change
2026-10-25	68.6	no change
2026-10-26	68.6	no change
2026-10-27	68.6	no change
2026-10-28	68.6	no change
2026-10-29	68.6	no change
2026-10-30	68.6	no change
2026-10-31	68.6	no change
2026-11-01	68.6	no change
2026-11-02	68.6	no change

What changed since your last check

Correctness no change
Freshness no change
Rider experience no change

Feed history

Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.

Feed history by published file
Checked	Published file	Service dates through	Grade at the time
2026-10-02 to 2026-11-02 (32 checks)	`05eac1908e5e`	2026-09-30	Current rubric: see the trend above
2026-09-18 to 2026-10-01 (14 checks)	`05eac1908e5e`	2026-09-30	D, 68.6 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade

What changed in this feed

Overall grade and score held steady since 2026-11-01.

Same feed file as 2026-11-01; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.

Everything we checked

3 findings, ordered by severity.

Show every finding

Error1 instance
Service data ended 33 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Finding code: scorecard_feed_expired · Read the fix guide for scorecard_feed_expired · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Warning1 instance
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.
Fix: Schedule a feed re-export now so the new calendar is live well before the current one ends. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date30_days · Read the fix guide for feed_expiration_date30_days · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: 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. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)

NTD GTFS readiness Not ready

Resolve this before you certify on the D-10. Service data expired 33 days ago, so FTA would find the link out of date.

Published Ready: Published at a public URL.
Valid Ready: Passes validation with no errors.
Current Not ready: Service data expired 33 days ago, so FTA would find the link out of date.
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 your 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.

shapes.txt covers your trips Ready: All 162 trips have a shape in shapes.txt.

In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.

A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.

Conformance mark Not yet

One requirement remains for this feed to earn the conformance mark. Service data expired 33 days ago.

Valid Met: Passes validation with no errors.
Current Not yet: Service data expired 33 days ago.
Accessible Met: States wheelchair access on 100% of stops and 100% of trips.

In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.

A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.

Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.

How this agency maps to the standards

The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.

Correctness 96 / 100: GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
Freshness 0 / 100: GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
Rider experience 85 / 100: GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality Not yet published: GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Part of the Texas portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Texas

Other scorecards in Texas, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

Badge HTML

<a href="https://gtfsscorecard.org/agency/city-of-longview/"><img src="https://gtfsscorecard.org/agency/city-of-longview/badge.svg" width="320" height="58" alt="City of Longview: current GTFS data quality score from GTFS Scorecard"></a>

Badge Markdown

[![City of Longview: current GTFS data quality score from GTFS Scorecard](https://gtfsscorecard.org/agency/city-of-longview/badge.svg)](https://gtfsscorecard.org/agency/city-of-longview/)

Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.

Cite this record

This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/city-of-longview/2026-11-02.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-11-02. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.

GTFS Scorecard. (2026). City of Longview GTFS feed-quality record, dated 2026-11-02 (grade D (68.6/100), rubric v1.4, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 05eac1908e5e…). https://gtfsscorecard.org/data/artifacts/city-of-longview/2026-11-02.json

@misc{gtfsscorecard-city-of-longview-2026-11-02,
  title        = {City of Longview GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/city-of-longview/2026-11-02.json}},
  note         = {Checked 2026-11-02; rubric v1.4; gtfs-validator 8.0.1; reader archive profile raw-v1; grade D (68.6/100)}
}

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.