Prep for a call: printable one-page brief · For your board packet: printable one-pager · Fix log: every issue this feed has cleared · Compare with another agency · Watch this feed: get an email before it expires

Feed status · checked 2026-07-09

City of Long Beach Transportation

Based on the feed this agency publishes

FDCBA

64.2 / 100

unchanged since 2026-07-08

Ahead of 54% of all tracked agencies and 52% of mid-size agencies. Operates in New York.

Covers 175 daysAccessibility gapsNo realtime feed

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.1, validator 8.0.1.

Checked for changes 10 hours ago; last changed 2 days ago.

Measured 3 of 4 score categories from the agency's own feed.

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 agency's own URL.

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

Top things to fix

Fix 01

Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team

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

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points

Fix 02

Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).Likely your export tool

170 of 170 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

⏱ Often one default setting in your export.worth about +15 points

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

Fix 03

Populate trip_headsign to match what the bus displays.Likely your export tool

170 of 170 trips have no headsign. Riders at the stop can't tell which direction a bus is going.

⏱ Usually a bulk edit in your scheduling software.worth about +15 points

Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.

Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
Populate trip_headsign to match what the bus displays. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.

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 Long Beach Transportation) scored D (64.2 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
   What: 135 of 135 stops don't say whether a wheelchair user can board there.
   Validator notice: scorecard_wheelchair_boarding_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_boarding_unknown/

2. Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).
   What: 170 of 170 trips don't say whether the vehicle is wheelchair accessible.
   Validator notice: scorecard_wheelchair_accessible_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_accessible_unknown/

3. Populate trip_headsign to match what the bus displays.
   What: 170 of 170 trips have no headsign.
   Validator notice: scorecard_missing_headsigns
   Guide: https://gtfsscorecard.org/fix/scorecard_missing_headsigns/

Full scorecard: https://gtfsscorecard.org/agency/city-of-long-beach-transportation/

Score by category

Correctness73.5 / 100

The MobilityData validator flagged 6 kinds of issue across 4642 instances (0 error, 4639 warning, 3 informational).

Freshness100.0 / 100

Service data covers the next 175 days.

Rider experience22.5 / 100

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

Accessibility0 / 100

0% of stops state accessibility (0% 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.

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

East Loop (green)
Express (green)
Point (green)
Special (green)
Special (green)
West Loop (green)

Routes in City of Long Beach Transportation's feed
Route	Type	Line color
East Loop	Bus	green
Express Late Night Express	Bus	green
Point Pt. Lookout	Bus	green
Special Shoppers Special East	Bus	green
Special Shoppers Special West	Bus	green
West Loop	Bus	green

This feed has 135 stops.

List every stop

National Blvd & W Park Ave
Grand Blvd & W Park Ave
W Beech St & Grand Blvd
Senior Home
W Hudson St & Magnolia Blvd
35 Broadway
W Broadway & National Blvd
E Broadway & Maple Blvd
Maple Blvd & E Park Ave
LIRR Station
E Park Ave & Edwards Blvd
E Park Ave & Riverside Blvd
E Park Ave & Long Beach Blvd
E Park Ave & Monroe Blvd
E Park Ave & Lincoln Blvd
E Park Ave & Franklin Blvd
E Park Ave & Neptune Blvd
E Park Ave & Roosevelt Blvd
E Park Ave & Pacific Blvd
Parkside Road Drive & Lido Blvd
Garden City Ave & Lido Blvd
Mineola Ave & Lido Blvd
PT Lookout Post Office
PT Lookout Fire House
Glenwood Ave & Lido Blvd
Parkside Road Drive & Lido Blvd
Donna Lane & Lido Blvd
750 Town Houses - Lido Blvd
Greenway Road & Lido Blvd
Maple Blvd & E Park Ave
Blackheath Road & Lido Blvd
E Park Ave & Maple Blvd
Maple Blvd & E Walnut Street
E Broadway & Roosevelt Blvd
E Broadway & Neptune Blvd
E Broadway & Franklin Blvd
E Broadway & Lincoln Blvd
E Broadway & Monroe Blvd
E Broadway & Long Beach Blvd
E Broadway & Riverside Blvd
E Broadway & Edwards Blvd
W Broadway & Magnolia Blvd
W Broadway & Laurelton Blvd
W Broadway & Lafayette Blvd
W Broadway & Washington Blvd
W Broadway & Lindel Blvd
W Beech Street & Grand Blvd
W Beech Street & New York Ave
W Beech Street & Arizona Ave
W Beech Street & Wyoming Ave (WB)
W Beech Street & Tennessee Ave (WB)
W Beech Street & Maryland Ave
W Beech Street & Georgia Ave
W Beech Street & Illinois Ave
Nevada Ave
W Beech Street & Connecticut Ave
W Beech Street & Indiana Ave
W Beech Street & Michigan Street
W Beech Steet & Virginia Ave
W Beech Street & Deleware Ave
W Beech Street & Arizona Ave
W Beech Street & New York Ave
W Park Ave & Lindell Blvd
W Park Ave & Washington Blvd
W Park Ave & Lafayette Blvd
W Park Ave & Laurelton Blvd
W Park Ave & Magnolia Blvd
W Park Ave & National Blvd
W Park Ave & Magnolia Blvd
W Park Ave & Laurelton Blvd
W Park Ave & Lafayette Blvd
W Park Ave & Washington Blvd
W Park Ave & Lindell Blvd
W Park Ave & Grand Blvd
Grand Blvd & W Walnut St
E Park Ave & Pacific Blvd
E Park Ave & Roosevelt Blvd
E Park Ave & Neptune Blvd
E Park Ave & Franklin Blvd
E Park Ave & Lincoln Blvd
E Park Ave & Monroe Blvd
E Park Ave & Long Beach Blvd
E Park Ave & Riverside Blvd
E Park Ave & Edwards Blvd
W Broadway & Lindel Blvd
W Broadway & Washington Blvd
W Broadway & Lafayette Blvd
W Broadway & Laurelton Blvd
W Broadway & Magnolia Blvd
W Broadway & National Blvd
W Broadway & Edwards Blvd
E Broadway & Riverside Blvd
E Broadway & Long Beach Blvd
E Broadway & Monroe Blvd
E Broadway & Lincoln Blvd
522 Shore Road
Shore Road & Neptune Blvd
700 Shore Road
Shore Road & Pacific Blvd
E Broadway & Pacific Blvd
E Broadway & Maple Blvd
Stop & Shop
National Blvd & Walnut Street
National Blvd & W Beech Street
W Hudson Street & National Blvd (WB)
W Hudson Street & Magnolia Blvd (WB)
Magnolia Blvd & W Bay Drive
W Hudson Street & Laurelton Blvd (WB)
W Hudson Street & Lafayette Blvd
W Hudson Street & Washington Blvd (WB)
W Hudson Street & Lindell Blvd (WB)
Lindell Blvd & W Chester Street
Lindell Blvd & W Walnut Street
Blackheath Road & Lido Blvd
Greenway Road & Lido Blvd
Regant Drive & Lido Blvd
Leamington Street & Lido Blvd
Nickerson Beach
750 Town Houses - Lido Blvd
Malibu Shore Club
W Beech St & New York Ave
W Beech St & Ohio Ave
Lindell Blvd & W Park Ave
W Beech St & Grand Blvd
W Beech St & Pennsylvania Ave
Lincoln Blvd & Shore Rd
Grand Blvd & W Park Ave
E Broadway & Long Beach Blvd
W Beech St & Vermont St
Grand Blvd & W Walnut St
W Beech St & National Blvd
Anchor Town Park
Grand Blvd & W Park Ave
W Beech St & Nebraska St
Malibu Beach Club

Over time

Overall score across the last 20 checks — unchanged since 2026-07-08.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-06-19	62.2	first check
2026-06-20	62.2	no change
2026-06-21	62.2	no change
2026-06-22	62.2	no change
2026-06-23	62.2	no change
2026-06-24	62.2	no change
2026-06-25	62.2	no change
2026-06-26	62.2	no change
2026-06-27	62.2	no change
2026-06-28	62.2	no change
2026-06-29	62.2	no change
2026-06-30	62.2	no change
2026-07-01	62.2	no change
2026-07-02	62.2	no change
2026-07-04	62.2	no change
2026-07-05	62.2	no change
2026-07-06	64.2	up 2.0
2026-07-07	64.2	no change
2026-07-08	64.2	no change
2026-07-09	64.2	no change

What changed since your last check

Correctness no change
Freshness no change
Rider experience no change

What changed in this feed

Overall grade and score held steady since 2026-07-08.

Same feed file as 2026-07-08; the published zip did not change.

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

Everything we checked

Warning4599 instances
Missing timepoint value (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_timepoint_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: missing_timepoint_value · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning170 instances
170 of 170 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning170 instances
170 of 170 trips have no headsign.
Riders at the stop can't tell which direction a bus is going.
Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)
Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Warning135 instances
135 of 135 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.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning36 instances
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.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Agencies here usually clear this within about 1 week (based on 11 observed fixes).
Validator rule: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning2 instances
Route long name contains short name (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_long_name_contains_short_name' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
Missing feed contact email and url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Agencies here usually clear this within about 2 weeks (based on 8 observed fixes).
Validator rule: missing_recommended_field · Read the fix guide · 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.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Info3 instances
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Agencies here usually clear this within about 1 week (based on 10 observed fixes).
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

Beyond the grade

Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.

124 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Maple Blvd & E Park Ave", "Maple Blvd & E Walnut Street", "W Beech Street & Wyoming Ave (WB)", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

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 175 days.

agency_id matches your NTD ID Not checked yet: Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.

shapes.txt covers your trips Ready: All 170 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 and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.

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). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and 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

This feed is close to the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

Valid Met: Passes validation with no errors.
Current Met: Service data covers the next 175 days.
Accessible Not yet: States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

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.

Can riders use it?

Checks beyond structural validation: places where the feed is valid but a rider still could not travel.

36 of 135 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.

These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.

Clears the Google and Apple Maps four-week coverage bar. This feed has 175 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.

How this agency maps to the standards

A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.

Correctness 74 / 100: GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
Freshness 100 / 100: The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
Rider experience 22 / 100: GTFS Best Practices for rider-facing fields. MobilityData grading: stop names and headsigns.
Realtime quality Not yet published: GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Show your grade

Put a live badge on your agency site or feed README. It updates daily and links back to this scorecard.

[![City of Long Beach Transportation GTFS data quality grade: D](https://gtfsscorecard.org/data/artifacts/city-of-long-beach-transportation/badge.svg)](https://gtfsscorecard.org/agency/city-of-long-beach-transportation/)

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-long-beach-transportation/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, or a research citation instead of linking the live page, whose content will differ on your next visit.

GTFS Scorecard. (2026). City of Long Beach Transportation GTFS feed-quality record, dated 2026-07-09 (grade D (64.2/100), rubric v1.1, gtfs-validator 8.0.1, feed sha256 d6b11e9d0e01…). https://gtfsscorecard.org/data/artifacts/city-of-long-beach-transportation/2026-07-09.json

@misc{gtfsscorecard-city-of-long-beach-transportation-2026-07-09,
  title        = {City of Long Beach Transportation GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/city-of-long-beach-transportation/2026-07-09.json}},
  note         = {Checked 2026-07-09; rubric v1.1; gtfs-validator 8.0.1; grade D (64.2/100)}
}

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