Feed status · checked 2026-08-01
City of Glendale
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in California.
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.3, validator 8.0.1.
Checked for changes 80 minutes ago; last fetch returned HTTP 403.
Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: provisional.
- Realtime quality was not measured this run. It does not count against the grade.
- The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 1431 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.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category
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
350 of 350 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 in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
1167 of 1167 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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 ended 1431 day(s) ago.
- Next action
- Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date 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.
Copy handoff text
- Feed evidence
- 350 of 350 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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
- Feed evidence
- 1167 of 1167 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
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.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · Read the fix guide
Make the change. This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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. Self-check a feed before you publish.
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. This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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. Self-check a feed before you publish.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
Make the change. This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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. Self-check a feed before you publish.
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 1431 days ago.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% 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
This feed is served from the TransitFeeds archive, which is no longer maintained. The most useful request is publishing the current feed from a live URL, then these fixes. Each fix names the validator notice and a guide link.
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.
Score by category
The MobilityData validator flagged 4 kinds of issue across 13 instances (0 error, 9 warning, 4 informational).
Service data ended 1431 day(s) ago. Trip planners have likely already dropped this feed.
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.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (33, 34, 8, 12).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
3 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Foothill at Angeles Crest Hwy", "Chevy Chase at Mid Block (La Boice & Boynton)", "Chevy Chase at Mid Block (La Boice & Boynton)").
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
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 350 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.
- 1 (yellow)
- 11 (teal)
- 12 (orange)
- 3 (blue)
- 31 (blue)
- 3 (blue)
- 33 (green)
- 34 (green)
- 4 (purple)
- 5 (green)
- 6 (brown)
- 7 (brown)
- 8 (red)
| Route | Type | Line color |
|---|---|---|
| 1 Glendale Transportation Center to Stocker Square | Bus | yellow |
| 11 Glendale Transportation Center to Downtown Glendale | Bus | teal |
| 12 Glendale Transportation Center to Downtown Burbank Station | Bus | orange |
| 3 Glendale Galleria to Jet Propulsion Laboratory (JPL) | Bus | blue |
| 31 Glendale Galleria to La Crescenta | Bus | blue |
| 3 Glendale Galleria to Glendale Community College | Bus | blue |
| 33 Montrose to Jet Propulsion Laboratory | Bus | green |
| 34 Montrose to La Canada High School | Bus | green |
| 4 Glendale Transportation Center to Glendale Galleria | Bus | purple |
| 5 Pacific Park to Hoover High School | Bus | green |
| 6 Pacific Park to Glendale High School | Bus | brown |
| 7 Riverside Rancho to Glendale Community College | Bus | brown |
| 8 Glendale Transportation Center to Glendale Community College | Bus | red |
List every stop
- Brand at Broadway
- Brand at California
- Brand at Chevy Chase
- Brand at Glenoaks
- Brand at Milford
- Brand at Monterey
- Central at Americana
- Central at Arden
- Central at California
- Central at Chevy Chase
- Central at Colorado
- Central at Doran
- Central at Lomita
- Central at Los Feliz
- Central at Magnolia
- Central at Milford
- Central at Windsor
- Brand at Colorado
- Brand at Doran
- Brand at Lexington
- Central at Broadway
- Central at Laurel
- Central at Laurel
- Glendale Transportation Center (GTC)
- Brand at Dryden
- Stocker at Brand
- Brand at California
- Brand at Chevy Chase
- Central at Arden
- Central at California
- Central at Chevy Chase
- Central at Doran
- Central at Dryden
- Central at Lexington
- Central at Los Feliz
- Central at Magnolia
- Central at Milford
- Central at Stocker
- Central at Windsor
- Brand at Broadway
- Brand at Lexington
- Brand at Colorado
- Brand at Milford
- Brand at Harvard
- Central at Americana
- Central at Broadway
- Central at Lomita
- Central at Colorado
- Brand at Fairview
- Stocker at Brand
- Broadway at Brand
- Broadway at Jackson
- Broadway at Jackson
- Broadway at Louise
- Foothill at Alta Canyada
- Foothill at Alta Canyada
- Foothill at Beulah
- Foothill at Briggs
- Foothill at Briggs
- Foothill at Chevy Chase
- Foothill at Angeles Crest Hwy
- Foothill at Commonwealth
- Foothill at Commonwealth
- Foothill at Cornishon
- Foothill at Cornishon
- Foothill at Crown
- Foothill at Crown
- Foothill at Gould
- Foothill at Gould
- Foothill at Hill
- Foothill at Hillard
- Foothill at Hillard
- Foothill at Indiana
- Foothill at La Canada
- Foothill at La Canada Plaza
- Foothill at La Canada Plaza
- Foothill at Lasheart
- Foothill at Oakwood
- Foothill at Oakwood
- Foothill at Ocean View
- Foothill at Ocean View
- Foothill at Palm
- Foothill at Palm
- Foothill at Raymond
- Foothill at Raymond
- Foothill at Rosemont
- Foothill at Rosemont
- Foothill at Vineta
- Glendale at Broadway
- Glendale at Broadway (NS)
- Glendale at California
- Glendale at Doran
- Glendale at Doran
- Glendale at Lexington
- Glendale at Lexington
- Glendale at Monterey
- Glendale at Wilson
- Glendale at Wilson
- Honolulu at La Crescenta
- Honolulu at La Crescenta
- Honolulu at Las Palmas
- Honolulu at Market
- Honolulu at Ocean View
- Honolulu at Orangedale
- Honolulu at Rosemont
- Honolulu at Rosemont
- La Crescenta at Altura
- La Crescenta at Altura
- La Crescenta at Mary
- La Crescenta at Mary
- La Crescenta at Montrose
- La Crescenta at Montrose
- La Crescenta at Piedmont
- La Crescenta at Piedmont
- La Crescenta at Prospect
- La Crescenta at Prospect
- Oak Grove at Foothill
- Jet Propulsion Laboratory (JPL)
- Verdugo at Oakwood
- Verdugo at Bagdad
- Verdugo at Bara
- Verdugo at Crestmont
- Verdugo at Crestmont
- Verdugo at El Cino
- Verdugo at Fern
- Verdugo at Fern
- Verdugo at Glencoe
- Verdugo at Glencoe
- Verdugo at Glorietta
- Verdugo at Glorietta
- Verdugo at Honolulu
- Verdugo at Kirkby
- Verdugo at Kirkby
- Verdugo at Ocean View
- Verdugo at Sunview
- Verdugo at Sunview
- Verdugo at Verdugo Loma
- Montrose at Pennsylvania
- Verdugo at Opechee
- Verdugo at Oakwood
- Montrose at Ramsdell
- La Canada High School
- Foothill at Rinetti
- Montrose at Waltonia
- Montrose at Ocean View
- Oak Grove at Foothill
- Ocean View at Honolulu
- Verdugo at Honolulu
- Canada at Towne (Glendale College)
- Harvard at Louise
- Glendale at Glenoaks
- Glendale at Glenoaks
- Glendale at Monterey
- Glendale at Verdugo
- Glendale at Verdugo
- Verdugo at Mountain
- Verdugo at Calle Vaquero
- Verdugo at Civic Auditorium (Glendale College)
- Verdugo at Towne (Glendale College)
- Broadway at Adams
- Broadway at Adams
- Broadway at Cedar
- Broadway at Cedar
- Broadway at Glendale
- Chevy Chase at Adams
- Chevy Chase at Adams
- Chevy Chase at Boynton
- Chevy Chase at Boynton
- Chevy Chase at Brand
- Chevy Chase at Carlton
- Chevy Chase at Mid Block (La Boice & Boynton)
- Chevy Chase at Mid Block (La Boice & Boynton)
- Chevy Chase at Colorado
- Chevy Chase at Colorado
- Chevy Chase at Garfield
- Chevy Chase at Garfield
- Chevy Chase at Glendale
- Chevy Chase at Maple
- Chevy Chase at Maple
- Glendale at Broadway (FS)
- Glendale at Palmer
- Harvard at Isabel
- Harvard at Isabel
- Harvard at Louise
- Broadway at Brand
- Chevy Chase at Broadway
- Colorado at Central
- Pacific at Arden
- Pacific at Arden
- Pacific at California
- Pacific at California
- Pacific at Colorado
- Pacific at Doran
- Pacific at Doran
- Pacific at Harvard
- Pacific at Harvard
- Pacific at Ivy
- Pacific at Lexington
- Pacific at Lexington
- Pacific at Vine
- Pacific at Wilson
- Pacific at Wilson
- Colorado at Columbus
- Colorado at Pacific
- Glenwood at Concord (Hoover High School)
- Pacific at Dryden
- Pacific at Palm
- Stocker at Pacific
- Broadway at Carr
- Colorado at Adams
- Colorado at Adams
- Colorado at Brand
- Colorado at Brand
- Colorado at Campus
- Colorado at Chevy Chase
- Colorado at Chevy Chase
- Colorado at Columbus
- Colorado at Everett
- Colorado at Everett
- Colorado at Fischer
- Colorado at Fischer
- Colorado at Glendale
- Colorado at Glendale
- Colorado at Carr Park
- Colorado at Louise
- Colorado at Louise
- Colorado at Verdugo
- Pacific at Colorado
- San Fernando at Riverdale
- Verdugo at Broadway
- Verdugo at Colorado
- Pacific at Riverdale
- Broadway at Sinclair
- San Fernando at Elk
- Alameda at Glenoaks
- Alameda at Glenoaks
- Glenoaks at Allen
- Glenoaks at Allen
- Glenoaks at Concord
- Glenoaks at Concord
- Glenoaks at Grandview
- Glenoaks at Grandview
- Glenoaks at Graynold
- Glenoaks at Highland
- Glenoaks at Highland
- Glenoaks at Jackson
- Glenoaks at Jackson
- Glenoaks at Justin
- Glenoaks at Justin
- Glenoaks at Kenilworth
- and 100 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 49.1 | first check |
| 2026-07-30 | 49.1 | no change |
| 2026-07-31 | 49.1 | no change |
| 2026-08-01 | 49.1 | 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-31.
Same feed file as 2026-07-31; 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
10 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 1431 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, and set feed_info feed_end_date 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 · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1167 instances
1167 of 1167 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. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning350 instances
350 of 350 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.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning7 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Finding code: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Finding code: scorecard_missing_feed_info_dates · 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.)
Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info4 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · 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).
Trip-planning apps and regional data coordinators 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.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. Service data expired 1431 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 1431 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 1167 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
This feed is close to the conformance mark. Service data expired 1431 days ago. 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 Not yet
- Service data expired 1431 days ago.
- 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.
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.
In California, the published guideline is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.
California Minimum GTFS Guidelines checklist (3 of 6 measured items met)
The state's own Data Process Checklist, matched item by item to what this scorecard already measures. An item marked "not measured here" is real ground the checklist covers that this tool does not check; see the official checklist for the full picture.
- Meets Publish GTFS Schedule at a stable, automatically-fetchable URL
The published feed URL downloaded at the last check.
- Not measured here Implement required fields: Fares v2, text-to-speech stop names, shapes.txt, wheelchair_boarding, and Pathways where applicable
This scorecard measures wheelchair_boarding, shapes.txt coverage, fare data, and station pathways separately, below; it does not check the Fares v2 format specifically or text-to-speech stop names.
- Not measured here Achieve a passing score in every category of the MobilityData GTFS Grading Scheme v1
This scorecard automates a proxy for the Grading Scheme's rider-facing fields (see the standards crosswalk) rather than running the scheme itself, which grades by comparison to the real world by hand.
- Not measured here Publish changes to the base schedule at least one week ahead of every service change
This scorecard does not track a feed's publish history, so advance notice cannot be checked.
- Meets Produce no critical errors in the MobilityData GTFS Validator
Passes validation with no errors.
- Not measured here Publish Trip Updates, Vehicle Positions, and Alerts feeds
This scorecard checks realtime reachability and freshness overall; it does not check for all three feed types individually.
- Not measured here Update Trip Updates and Vehicle Positions at least every 20 seconds
This scorecard samples realtime freshness; it does not check this specific 20-second cadence.
- Not measured here Publish information for at least 99% of vehicles in service
This scorecard measures the share of scheduled trips represented in TripUpdates, a related but different figure than vehicle coverage.
- Not measured here Keep 100% of trip_ids consistent between Schedule and Realtime
This scorecard does not currently check trip_id consistency between the Schedule and Realtime feeds.
- Not measured here Produce no critical errors in the Center for Urban Transportation Research realtime validator
This scorecard does not run the CUTR realtime validator.
- Not measured here Publish accessible feed links on the agency or regional partner website
This scorecard does not check the agency's own website.
- Not measured here Register GTFS and GTFS-Realtime feeds with transit.land and the Mobility Database
This scorecard does not currently check aggregator registration for this section.
- Gap Designate a technical contact in feed_info.txt's feed_contact_email
feed_info.txt has no feed_contact_email or feed_contact_url.
- Gap wheelchair_boarding stated on stops and trips
States wheelchair access on 0% of stops and 0% of trips.
- Meets shapes.txt with a shape for every trip
All 1167 trips have a shape in shapes.txt.
- Gap Fare data published, or the service marked fare-free
No fare data is published.
- Correctness 86 / 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 38 / 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.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.
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-glendale/2026-08-01.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-08-01. 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.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.