Feed status · checked 2026-08-01
Metro St. Louis
Based on the feed this agency publishes
Service mode Rail + Bus
down 0.6 since 2026-07-31
Catalogued in Missouri.
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 3 hours ago; last changed 2 days ago.
Measured 4 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- 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
Re-export with a validity window that reaches at least 60 days out.Likely your export tool
Service data runs out in 29 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
⏱ One export setting.worth about +51 points in its category
Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool
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.
⏱ Two fields, set once in export settings.worth about +15 points in its category
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.
⏱ A small file for most flat-fare systems.worth about +15 points in its category
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 29 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
- Feed evidence
- feed_info.txt is missing its start/end dates (the file itself is absent)
- Next action
- Add feed_info.txt with feed_start_date and feed_end_date to your export.
- 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
- The feed contains no fare information.
- Next action
- 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.
- 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 with a validity window that reaches at least 60 days out. · Read the fix guide
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.
Add feed_info.txt with feed_start_date and feed_end_date to your export. · Read the fix guide
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.
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. · Read the fix guide
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 is in 29 days.
- 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
- Live-arrival data covered 81.1% of scheduled trips in the sampled window.
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.
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 7 kinds of issue across 24255 instances (0 error, 14678 warning, 9577 informational).
Service data runs out in 29 day(s). Publish an updated feed soon or riders will lose trip planning.
100% of stops state wheelchair accessibility (42% marked accessible, 58% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
100% of stops state accessibility (42% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
4818 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("THEKLA @ EMERSON SB", "WEST FLORISSANT @ BUZZ WESTFALL SB", "SKINKER @ FOREST PARK PARKWAY SB", and more).
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.
Sampled 9 times: 3 of 3 configured feeds healthy; 81.1% of scheduled trips had live predictions; 100.0% of vehicles on their route; predictions ran a median of 60s behind schedule.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 5118 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.
- MLB (blue)
- MLR (red)
- 1 (white)
- 2 (white)
- 4 (white)
- 5 (white)
- 8 (white)
- 9 (white)
- 10 (white)
- 11 (white)
- 13 (white)
- 16 (white)
- 18 (white)
- 19 (white)
- 21 (white)
- 30 (white)
- 31 (white)
- 32 (white)
- 33 (white)
- 34 (white)
- 35 (white)
- 40 (white)
- 41 (white)
- 42 (white)
- 49 (white)
- 56 (white)
- 57 (white)
- 58 (white)
- 59 (white)
- 60 (white)
- 61 (white)
- 64 (white)
- 70 (white)
- 73 (white)
- 74 (white)
- 76 (white)
- 77 (white)
- 78 (white)
- 79 (white)
- 90 (white)
- 91 (white)
- 94 (white)
- 95 (white)
- 97 (white)
- 98 (white)
- 100 (white)
- 1 (white)
- 2 (white)
- 3 (white)
- 4 (white)
- 5 (white)
- 6 (white)
- 8 (white)
- 9 (white)
- 12 (white)
- 13 (white)
- 14 (white)
- 15 (white)
- 16 (white)
- 23 (white)
- MLB (blue)
- MLR (red)
| Route | Type | Line color |
|---|---|---|
| MLB MetroLink Blue Line | Rail | blue |
| MLR MetroLink Red Line | Rail | red |
| 1 Gold | Bus | white |
| 2 Red | Bus | white |
| 4 Natural Bridge | Bus | white |
| 5 Green | Bus | white |
| 8 Shaw-Cherokee | Bus | white |
| 9 Oakville | Bus | white |
| 10 Gravois-Lindell | Bus | white |
| 11 Chippewa | Bus | white |
| 13 Union | Bus | white |
| 16 City Limits | Bus | white |
| 18 Taylor | Bus | white |
| 19 St Louis Ave | Bus | white |
| 21 Watson Rd | Bus | white |
| 30 Arsenal | Bus | white |
| 31 Chouteau | Bus | white |
| 32 Dr ML King | Bus | white |
| 33 Midland | Bus | white |
| 34 Earth City | Bus | white |
| 35 Rock Road | Bus | white |
| 40 Broadway-Halls Ferry | Bus | white |
| 41 Lee | Bus | white |
| 42 Sarah | Bus | white |
| 49 Lindbergh | Bus | white |
| 56 Kirkwood-Webster | Bus | white |
| 57 Manchester | Bus | white |
| 58 Chesterfield Valley | Bus | white |
| 59 Oakland | Bus | white |
| 60 Shepley-Lilac | Bus | white |
| 61 Chambers Rd | Bus | white |
| 64 Lucas-Hunt | Bus | white |
| 70 Grand | Bus | white |
| 73 Carondelet | Bus | white |
| 74 Florissant | Bus | white |
| 76 N Hanley Shuttle | Bus | white |
| 77 Village Square | Bus | white |
| 78 Bellefontaine | Bus | white |
| 79 Ferguson-Clayton | Bus | white |
| 90 Hampton | Bus | white |
| 91 Olive | Bus | white |
| 94 Page | Bus | white |
| 95 Kingshighway | Bus | white |
| 97 Delmar | Bus | white |
| 98 Ballas-North Hanley | Bus | white |
| 100 Hazelwood | Bus | white |
| 1 Main Street - State Street | Bus | white |
| 2 Cahokia Heights | Bus | white |
| 3 Sauget - Water Street | Bus | white |
| 4 19th & Central | Bus | white |
| 5 Missouri Ave - ML King | Bus | white |
| 6 Rosemont | Bus | white |
| 8 Alta Sita | Bus | white |
| 9 Washington Park | Bus | white |
| 12 OFallon-Fairview Heights | Bus | white |
| 13 Caseyville | Bus | white |
| 14 Memorial Hosp-Westfield Plaza | Bus | white |
| 15 Belleville-O'Fallon | Bus | white |
| 16 St. Clair Square | Bus | white |
| 23 Belleville-College | Bus | white |
| MLB MetroLink Blue Line | Rail | blue |
| MLR MetroLink Red Line | Rail | red |
List every stop
- LINDBERGH @ TESSON FERRY EB
- LINDBERGH @ BOHRER PARK EB
- LINDBERGH @ MUELLER EB
- LINDBERGH @ FLORI EB
- LINDBERGH @ CONCORD EB
- CLARKSON @ SOUTH OUTER FORTY NB
- NEW HALLS FERRY @ DUNN SB
- NEW HALLS FERRY @ CENTRAL CITY SHOPPING CTR SB
- NEW HALLS FERRY @ WOODWIND SB
- HALLS FERRY @ OLD MANOR SB
- HALLS FERRY @ IBIS COURT SB
- HALLS FERRY @ HUDSON SB
- HALLS FERRY @ CAPITOL SB
- HALLS FERRY @ EMPIRE SB
- HALLS FERRY @ CHAMBERS SB
- HALLS FERRY @ HECHT SB
- HALLS FERRY @ LUCAS-HUNT SB
- HALLS FERRY @ DORWOOD SB
- HALLS FERRY @ ST. CYR SB
- HALLS FERRY @ GLEN GARDEN SB
- HALLS FERRY @ COZENS SB
- HALLS FERRY @ COZENS NB
- HALLS FERRY @ GLEN GARDEN NB
- HALLS FERRY @ ST. CYR NB
- HALLS FERRY @ DORWOOD NB
- HALLS FERRY @ LUCAS-HUNT NB
- HALLS FERRY @ HECHT NB
- HALLS FERRY @ CHAMBERS NB
- HALLS FERRY @ EMPIRE NB
- HALLS FERRY @ CAPITOL NB
- HALLS FERRY @ HUDSON NB
- HALLS FERRY @ IBIS COURT NB
- HALLS FERRY @ VORHOF NB
- NEW HALLS FERRY @ WOODWIND NB
- NEW HALLS FERRY @ CENTRAL CITY SHOPPING CTR NB
- NEW HALLS FERRY @ DUNN NB
- DUNN @ NEW HALLS FERRY WB
- HAMPTON @ EICHELBERGER SB
- HAMPTON @ RHODES SB
- HAMPTON @ HOLLY HILLS SB
- HAMPTON @ ROBERT NB
- HAMPTON @ LOUGHBOROUGH NB
- HAMPTON @ HOLLY HILLS NB
- HAMPTON @ MILENTZ NB
- HAMPTON @ EICHELBERGER NB
- HAMPTON @ DELOR NB
- JAMIESON @ LANSDOWNE NB
- GRAVOIS @ COMPTON SB
- LINDBERGH @ CLAYTON SB
- LINDBERGH @ COUNTY LIBRARY SB
- LINDBERGH @ LITZSINGER SB
- LINDBERGH @ HUNTLEIGH WOODS SB
- LINDBERGH @ HUNTLEIGH NB
- LINDBERGH @ HUNTLEIGH WOODS NB
- LINDBERGH @ CLAYTON NB
- WISKOW @ DUNKLIN EB
- LILAC @ KENRAN INDUSTRIAL SB
- LILAC @ FOXLAIR SB
- LILAC @ SHEPLEY SB
- SHEPLEY @ LILAC EB
- SHEPLEY @ MELVICH EB
- SHEPLEY @ RENFREW EB
- SHEPLEY @ BALMORAL EB
- SHEPLEY @ LOTHIAN CIRCLE EB
- SHEPLEY @ SPRING GARDEN EB
- CAMERON @ ROSS CIRCLE WB
- CAMERON @ ESTRIDGE SB
- NORTHGATE @ CAMERON SB
- NORTHGATE @ HABECKING SB
- LILAC @ FOXLAIR NB
- LILAC @ KENRAN INDUSTRIAL NB
- MARCEAU @ ALABAMA SB
- MARCEAU @ MINNESOTA SB
- BROADWAY @ RIVER CITY CASINO SB
- BROADWAY @ WEISS SB
- BROADWAY @ GOETZ SB
- BROADWAY @ HOLDEN SB
- BROADWAY @ RIPA SB
- KINGSTON @ CLYDE SB
- KINGSTON @ CARRINGTON SB
- KINGSTON @ PENTONVILLE SB
- KINGSTON @ TACOMA SB
- KINGSTON @ GENEVA SB
- TELEGRAPH @ KINGSTON NB
- KINGSTON @ SHETLAND NB
- KINGSTON @ EARLSFIELD NB
- KINGSTON @ PENTONVILLE NB
- KINGSTON @ CARRINGTON NB
- 120 KINGSTON NB
- BROADWAY @ RIPA NB
- BROADWAY @ HOLDEN NB
- BROADWAY @ HOFFMEISTER NB
- BROADWAY @ WEISS NB
- BROADWAY @ RIVER CITY CASINO NB
- MARCEAU @ BROADWAY WB
- MARCEAU @ MINNESOTA NB
- GERMANIA @ ALABAMA NB
- GERMANIA @ ON-RAMP I-55 N NB
- 2ND STREET @ ARSENAL SB
- EMERSON PARK METROLINK STATION
- JJK CENTER METROLINK STATION
- WASHINGTON PARK METROLINK STATION
- FAIRVIEW HEIGHTS METROLINK STATION
- MEMORIAL HOSPITAL METROLINK STATION
- SWANSEA METROLINK STATION
- BELLEVILLE METROLINK STATION
- COLLEGE TRANSIT CENTER
- 5TH & MISSOURI METROLINK STATION
- EAST RIVERFRONT METROLINK STATION
- LACLEDE'S LANDING METROLINK STATION
- CONVENTION CENTER METROLINK STATION
- 8TH & PINE METROLINK STATION
- CIVIC CENTER METROLINK STATION
- UNION STATION METROLINK STATION
- GRAND METROLINK STATION
- CENTRAL WEST END METROLINK STATION
- FOREST PARK DEBALIVIERE METROLINK STATION
- DELMAR LOOP METROLINK STATION
- WELLSTON METROLINK STATION
- ROCK ROAD METROLINK STATION
- UMSL SOUTH METROLINK STATION
- UMSL NORTH METROLINK STATION
- NORTH HANLEY METROLINK STATION
- LAMBERT AIRPORT TERMINAL #2 METROLINK STATION
- LAMBERT AIRPORT TERMINAL #1 METROLINK STATION
- 3RD STREET @ LINCOLN WB
- AIR MOBILITY @ WHERRY NB
- EAST US-50 @ EASTGATE WB
- EAST US-50 @ LAKE POINTE CENTRE WB
- EAST US-50 @ COUNTRY OAKS WB
- EAST US-50 @ SEVEN HILLS WB
- 905 EAST US-50 WB
- LINCOLN @ WEST US-50 SB
- LINCOLN @ 5TH STREET SB
- LINCOLN @ 3RD STREET NB
- LINCOLN @ 5TH STREET NB
- LINCOLN @ 7TH STREET SB
- LINCOLN @ 7TH STREET NB
- 904 EAST US-50 EB
- EAST US-50 @ TIMBER CREEK EB
- EAST US-50 @ COUNTRY OAKS EB
- EAST US-50 @ LAKEPOINTE CENTRE EB
- EAST US-50 @ EASTGATE EB
- CHARLES @ C STREET NB
- CHARLES @ B STREET NB
- CHARLES @ MAIN NB
- CARLYLE @ SHOP N SAVE ENTRANCE EB
- CARLYLE @ LAWNDALE EB
- CARLYLE @ WEST EB
- CARLYLE @ LINCOLNSHIRE EB
- CARLYLE @ SHADY WB
- CARLYLE @ BUNKER HILL EB
- CARLYLE @ LINCOLN PLACE COURT EB
- CARLYLE @ BRADFORD PLACE EB
- CHARLES @ C STREET SB
- SCHEEL @ CHARLES WB
- SCHEEL @ BENTON WB
- BELLEVILLE TRANSIT CENTER
- COLLEGE METROLINK STATION
- CARLYLE @ YMCA WB
- CARLYLE @ GREEN MOUNT WB
- CARLYLE @ BRADFORD PLACE WB
- CARLYLE @ CARLYLE EAST WB
- CARLYLE @ CORAL WB
- CARLYLE @ SHADY EB
- CARLYLE @ LINCOLNSHIRE WB
- CARLYLE @ WEST WB
- CARLYLE @ EAST HIGH SCHOOL REAR ENTRANCE WB
- DENVERSHIRE @ SHERWIN WILLIAMS ENTRANCE SB
- B STREET @ PENNSYLVANIA EB
- B STREET @ VIRGINIA EB
- B STREET @ IOWA EB
- B STREET @ FLORIDA EB
- B STREET @ LUCINDA EB
- B STREET @ DELAWARE EB
- 1820 B STREET EB
- WEST @ LEBANON EB
- 1301 WEST SB
- WEST @ DELMAR SB
- WEST @ A STREET SB
- WEST @ MAIN SB
- WEST @ WOODS WAY SB
- WEST @ ORCHARD SB
- WEST @ CARDINAL SB
- WEST @ SHADY SB
- WEST @ LINDBERGH CIRCLE NB
- WEST @ BROOKSHIRE COURT NB
- WEST @ FIVE FORKS NB
- WEST @ VICKSBURG NB
- VICKSBURG @ MILL SPRINGS WB
- VICKSBURG @ CEDAR MOUNTAIN WB
- DENVERSHIRE @ CARLYLE PLAZA ENTRANCE NB
- DENVERSHIRE @ CARLYLE PLAZA ENTRANCE SB
- VICKSBURG @ DENVERSHIRE WB
- VICKSBURG @ MILL SPRINGS EB
- WEST @ VICKSBURG SB
- WEST @ RUTLEDGE NB
- WEST @ FAIR OAKS NB
- WEST @ CARLYLE NB
- WEST @ SHADY NB
- WEST @ CARDINAL NB
- WEST @ CRESTHAVEN NB
- WEST @ MAIN NB
- WEST @ A STREET NB
- WEST @ DELMAR NB
- WEST @ EASTVIEW NB
- WEST @ OLD COLLINSVILLE NB
- WEST @ LEBANON WB
- 1819 B STREET WB
- B STREET @ DELAWARE WB
- B STREET @ KANSAS WB
- B STREET @ LUCINDA WB
- B STREET @ MICHIGAN WB
- B STREET @ FLORIDA WB
- B STREET @ IOWA WB
- B STREET @ VIRGINIA WB
- B STREET @ PENNSYLVANIA WB
- ILLINOIS @ SMELTING WORKS NB
- ILLINOIS @ FULLERTON NB
- ILLINOIS @ PAWNEE SB
- ILLINOIS @ BRACKETT SB
- ILLINOIS @ G STREET SB
- ILLINOIS @ E STREET SB
- ILLINOIS @ C STREET SB
- ILLINOIS @ B STREET NB
- ILLINOIS @ C STREET NB
- ILLINOIS @ D STREET NB
- ILLINOIS @ LEBANON NB
- ILLINOIS @ F STREET NB
- ILLINOIS @ DOUGLAS NB
- ILLINOIS @ GILBERT NB
- ILLINOIS @ BRACKETT NB
- ILLINOIS @ PAWNEE NB
- ILLINOIS @ FULLERTON SB
- ILLINOIS @ OLD FULLERTON SB
- METRO WAY @ SWANSEA METROBUS LOOP EB
- ILLINOIS @ GARDEN SB
- MAIN @ 17TH STREET SB
- DOUGLAS @ LEBANON SB
- MAIN @ 17TH STREET WB
- ILLINOIS @ ILLINOIS ROUTE 161 NB
- ILLINOIS @ ALEXA NB
- ILLINOIS @ METROWAY SB
- MEMORIAL HOSPITAL TRANSIT CENTER
- FRANK SCOTT @ IDA SB
- FRANK SCOTT PARKWAY @ MOUNT PLEASANT SB
- DAPRON @ FRANK SCOTT PARKWAY EB
- MEMORIAL @ ROYAL HEIGHTS WB
- MEMORIAL @ 39TH STREET WB
- MEMORIAL @ 43RD STREET WB
- and 4868 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — down 0.6 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 67.2 | first check |
| 2026-07-30 | 66.0 | down 1.2 |
| 2026-07-31 | 65.7 | down 0.3 |
| 2026-08-01 | 65.1 | down 0.6 |
What changed since your last check
- Correctness no change
- Freshness down 1.7
- Rider experience no change
- Realtime quality down 1.1
What changed over time
On 2026-07-25 this feed started at grade D. On 2026-07-31 feed entered the expiry window (30 days of service left). As of 2026-08-01 it holds grade D.
A plain-language history of this feed, newest first.
- 2026-07-31 Feed entered the expiry window (30 days of service left).
Everything we checked
14 findings, ordered by severity.
Show every finding
- Warning14653 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning21 instances
21 of 111 trips scheduled during the sampling window had no live predictions.
Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.
Fix: Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. (A vendor data-mapping question.)
Finding code: scorecard_rt_trip_coverage · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Warning19 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the transit vehicle route through the wrong path or point riders to the wrong boarding location.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Two or more routes share the same name.
Riders can't tell the routes apart in apps.
Fix: Give each route a distinct short or long name. (One field per route.)
Finding code: duplicate_route_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Finding code: unused_shape · 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
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the transit vehicle doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Service data runs out in 29 day(s).
When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)
Finding code: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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
1 of 5118 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)
- 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)
- Info9577 instances
Trip with shape dist traveled but no shape distances (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'trip_with_shape_dist_traveled_but_no_shape_distances' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: trip_with_shape_dist_traveled_but_no_shape_distances · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info5116 instances
About 5116 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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 Needs attention
This feed is close to NTD-ready. Service data runs out in 29 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 29 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 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 9577 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 runs out in 29 days; renew to qualify.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data runs out in 29 days; renew to qualify.
- 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.
Realtime reliability
The realtime feed responded on 100.0% of 200 checks over the last 34 days, with 40s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Live predictions vs schedule
Arrival predictions ran a median 60s late versus the schedule, and stayed within 300s nine times in ten. They were on time (about a minute early to five late) 77.0% of the time. 100.0% of reported vehicle positions sat on or near the published route shape.
From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.
Clears the Google and Apple Maps four-week coverage bar. This feed has 28 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
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 69 / 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 33 / 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 62 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 93 / 100
- 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/metro-st-louis/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.