Feed status · checked 2026-08-01
Sun Metro
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Texas.
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 41 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
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
1817 of 1817 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
4832 of 4832 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
Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign.
2137 of 4832 trips lack rider-facing destination or direction text. When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
⏱ Usually one value per route pattern in your scheduling source.worth about +7 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
- 1817 of 1817 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
- 4832 of 4832 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
- Feed evidence
- 2137 of 4832 trips lack rider-facing destination or direction text.
- Next action
- Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign.
- 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.
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.
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. 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. Self-check a feed before you publish.
Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. · 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. 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 is in 133 days.
- 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
- Fare information is published using GTFS Fares v1.
- 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.
Score by category
The MobilityData validator flagged 7 kinds of issue across 73 instances (0 error, 70 warning, 3 informational).
Service data covers the next 133 days.
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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
28 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (02, 07, 207, 32, 33, and more).
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.
238 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Alabama\Ft. Blvd.", "Alameda/Piedras", "5044 Doniphan/McClintock", 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.
Fares are applied to trips.
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 1817 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.
- 02 (blue)
- 07 (black)
- 10 (orange)
- 12 (orange)
- 14 (orange)
- 15 (orange)
- 16 (orange)
- 19 (orange)
- 205 (teal)
- 206 (yellow)
- 207 (purple)
- 208 (orange)
- 25 (red)
- 32 (green)
- 33 (green)
- 34 (green)
- 35 (brown)
- 43 (brown)
- 44 (brown)
- 46 (brown)
- 50 (blue)
- 500 (gray)
- 51 (blue)
- 52 (blue)
- 53 (blue)
- 59 (blue)
- 60 (purple)
- 61 (purple)
- 62 (purple)
- 63 (purple)
- 65 (purple)
- 67 (purple)
- 68 (purple)
- 69 (purple)
- 72 (blue)
- 74 (blue)
- 86 (purple)
- 89 (pink)
- 55 (blue)
- 41 (brown)
| Route | Type | Line color |
|---|---|---|
| 02 El Segundo Circulator | Bus | blue |
| 07 EPCC Connector | Bus | black |
| 10 Sunset Heights/Stanton | Bus | orange |
| 12 Doniphan | Bus | orange |
| 14 Westwind | Bus | orange |
| 15 Mesa | Bus | orange |
| 16 Upper Valley Circulator | Bus | orange |
| 19 Resler Circulator | Bus | orange |
| 205 Mesa BRIO | Bus | teal |
| 206 Alameda BRIO | Bus | yellow |
| 207 Dyer BRIO | Bus | purple |
| 208 Montana BRIO | Bus | orange |
| 25 Chelsea | Bus | red |
| 32 Copia | Bus | green |
| 33 Trowbridge | Bus | green |
| 34 Alabama | Bus | green |
| 35 Dyer | Bus | brown |
| 43 Montalvo Park Via Dyer | Bus | brown |
| 44 Sun Valley | Bus | brown |
| 46 North Hills Circulator | Bus | brown |
| 50 Montana | Bus | blue |
| 500 Streetcar UTL | Bus | gray |
| 51 RC Poe Via Edgemere | Bus | blue |
| 52 RC Poe Via Pebble Hills | Bus | blue |
| 53 Montwood | Bus | blue |
| 59 Eastside Connector | Bus | blue |
| 60 Socorro/Zaragoza Bridge | Bus | purple |
| 61 DTC Via Alameda | Bus | purple |
| 62 Lakeside | Bus | purple |
| 63 North Carolina | Bus | purple |
| 65 Valle Verde via Paisano | Bus | purple |
| 67 Yarbrough | Bus | purple |
| 68 Lee Trevino | Bus | purple |
| 69 George Dieter | Bus | purple |
| 72 Vista Del Sol | Bus | blue |
| 74 Gateway/Rojas | Bus | blue |
| 86 North Loop | Bus | purple |
| 89 Zaragoza Bridge Circulator | Bus | pink |
| 55 Zaragoza | Bus | blue |
| 41 Hondo Pass | Bus | brown |
List every stop
- 7921 North Loop
- 7849 North Loop\Alexander
- 7833North Loop\Emerson
- 7631North Loop\ Marmolejo Apt
- 7239 North Loop
- Montwood\Yarbrough\Brian Mooney
- Viscount\Viscount Village
- 9010 Viscount
- Montwood\Turrentine
- Montwood\Backus
- Montwood\McIntosh
- Montwood\Linum
- Montwood\Wedgewood
- Montwood\Woodfin
- Montwood\Cumbre Negra
- Montwood\Lomaland
- Montwood\Diciembre
- Montwood\Andalucia
- Lee Trevino\Amy Sue
- Lee Trevino\Anise
- Lee Trevino\George Archer
- Lee Trevino\Roy Pace
- Pebble Hills\Lee Trevino
- Pebble Hills\Roy Pace
- Montwood\George Dieter
- Pebble Hills\East Glen
- Pebble Hills\Schooner
- Montwood\Amy Sue
- Montwood\Bobby Jones
- Montwood\Tommy Aaron
- Montwood\Robert Wynn
- Montwood\Lake Omega
- Montwood\Trawood
- Montwood\Chris Scott
- Montwood\Piedra Roja
- Montwood\Ralph Janes
- Montwood\Saul Kleinfield
- Montwood\Polly Harris
- Montwood\Joe Battle
- Montwood\Desert Sun
- 7383 Alameda\Carolina
- Eastside Terminal Bay D
- Montwood\Desert Sun Dr.
- George Dieter\Trawood
- Montwood\Saul Kleinfield
- Montwood\Gus Moran
- Montwood\Lee Blvd.
- Montwood\Bay City Pl.
- Montwood\Estrada
- Montwood\Lake Omega
- Zaragoza\Saul Kleinfeld2
- Pebble Hills\Mclean
- Pebble Hills\Wayside
- Lee Trevino\Pebble Hills
- Lee Trevino\Gay Brewer
- Lee Trevino\Sam Snead
- Lee Trevino\Anise
- Vista Del Sol\George Dieter
- Montwood\George Dieter \Target Store
- Montwood\Robert Wynn
- Montwood\Mermaid
- Montwood\Bobby Jones
- Montwood\Anise
- Montwood\Noviembre
- Montwood\Enero
- Montwood\Cumbre Negra
- Montwood\Jonwood
- Montwood\Woodfin
- Montwood\Wedgewood
- Montwood\Camwood
- Montwood\McRae
- Montwood\Catnip
- Montwood\McFall
- Viscount\Montwood
- 8935 Viscount
- 368 Yarbrough\Tranquilo
- North Loop\Mauer
- North Loop\East
- North Loop\Center
- North Loop\West
- North Loop\Carolina
- North Loop\Atkinson
- North Loop\Hunter
- North Loop\Roselane
- North Loop\La Promesa
- Hawkins\Tony Lama
- 946 Hawkins\Merchant
- 1054 Hawkins\Commerce
- Eastside Terminal Bay A
- Viscount\Bellrose
- Diana\Meade
- Diana\Benning
- Diana\Hercules
- Diana\Tetons
- Diana\Wilmoth
- Diana\Blue Ridge
- Diana\Alps
- Diana\Marie Tobin
- Fred Wilson\Dyer
- 9700 Gateway North\Cohen Sta.
- 4700 Transmountain\Wal-Mart
- 9999 Kenworthy\Trans-Mt.
- 9849 Kenworthy
- Kenworthy\Cohen
- Diana\Stahala
- Diana\Stonewall
- 9447 Diana
- Diana\Camden
- Alameda/Piedras
- Diana\Hondo Pass
- Diana\Maxwell
- Diana\Pikes Peak
- Diana\Blue Ridge
- Diana\Guadalupe
- Diana\Tetons
- Diana\Hercules
- Diana\Titanic
- Diana\Vulcan
- Alameda\Carolina
- Alameda\Yarbrough
- 7300 Viscount\Catalpa
- 1045 Hawkins\Commerce
- 917 Hawkins\Merchant
- Hawkins\Tony Lama
- 7322 North Loop\Orgain
- Epcc Bay 2
- North Loop\Roselane
- North Loop\Hunter
- 7556 North Loop\Atkinson
- 7604 North Loop\Carolina
- 7720 North Loop\Franklin
- Corralitos\San Simon
- 7810 North Loop\East
- North Loop\Emerson
- North Loop\Wenda
- 8026 North Loop\Lafayette
- 425 Yarbrough\Big 8
- Yarbrough\Tranquilo
- San Antonio Transit Terminal
- 900 Magoffin\St.Vrain
- Magoffin\Octavia
- Magoffin\Brown
- Magoffin\Newman
- Magoffin\Cotton
- Magoffin\Lee St.
- Magoffin\Dallas
- 1900 Magoffin\Laurel
- Magoffin\Eucalyptus
- 2114 Magoffin\Walnut
- 2302 Magoffin\Palm
- Trowbridge\Howze
- Trowbridge\St. John
- 1204 Chelsea\Trowbridge
- 1504 Chelsea\Garry Owen
- Chelsea\Timberwolf
- Timberwolf\Edwards
- 5820 Timberwolf\Magruder
- Magruder\Hughey
- Hughey\Magruder
- Timberwolf\Magruder
- 5513 Timberwolf
- 1813 Chelsea\Timberwolf
- 1509 Chelsea\Garry Owen
- Northloop\Lomaland
- Chelsea\Olson
- 907 Chelsea\El Portal
- Chelsea\Yandell
- 501 Chelsea\Gateway West
- 209 Chelsea\Dailey
- Myrtle\Palm
- 2023 Myrtle\Willow
- 1931 Myrtle\Eucalyptus
- 1707 Myrtle\Williams
- Myrtle\Dallas
- Delta\Northloop
- Myrtle\Florence
- 600 Chelsea\Chelsea Plaza
- Valle Verde Campus Bay 1
- Trowbridge\Olson
- 5133 Trowbridge\St.John
- 4905 Trowbridge\Howze
- Santa Fe\Overland
- Paisano\Oregon
- Paisano\Mesa
- North Loop\Pendale
- 702 Paisano\Florence
- Paisano\Delta \St Vrain
- Paisano\Park
- 1400 Paisano\Nino Aguilera
- Paisano\Citrus
- 2000 Paisano\Eucalyptus
- Paisano\Piedras
- Paisano\Webber
- 4000 Paisano\Boone
- 223 Val Verde\Paisano
- 6811 Delta\Malaga
- Delta\Seville
- 6355 Delta\Ascarate
- 6125 Delta\Pecos
- 6021 Delta\Clark
- 5841 Delta\Collingsworth
- 5751 Delta\Medina
- Betel\Kernel
- 5625 Delta\Glenwood
- Delta\Buena Vista
- 4321 Delta\Tobin
- Delta\Boone
- 455 Yarbrough\North Loop
- 1001 Seventh\St.Vrain
- 801 Seventh\Ochoa
- Seventh\Florence
- 311 Seventh\Stanton
- 1212 Yarbrough\Vista Del Sol
- 2100 Yarbrough\Montwood
- Delta|Shelter
- Lee Trevino\Edgemere
- 5610 Delta\Buena Vista
- Delta\Glenwood
- 5800 Delta\Medina
- 5904 Delta\San Gabriel
- 6112 Delta\Clark
- 6208 Delta\Pecos
- 6314 Delta\Fonseca
- Delta\Ascarate
- 1906 Lee Trevino\Montwood
- Delta\Kirkin
- Delta\Malaga
- 201 Cortez\Pooley Apt.
- Blanco\De Vargas
- Blanco\Concepcion
- Val Verde\Paisano
- Lee Trevino\Vista Del Sol
- Paisano\Estrella
- 2121 Paisano\Piedras
- Paisano\Eucalyptus
- Paisano\Citrus
- 1315 Paisano\Nino Aguilera
- Paisano\St.Vrain
- Paisano\Florence
- Paisano\Stanton
- Delta\Concepcion
- Delta\Barcelona
- 5400 Delta\De Vargas
- Delta\Lisbon
- 121 George Orr\Peach Tree
- 147 George Orr \Pear Tree
- 7104 Granite \George Orr
- 800 Zaragoza\North Loop
- McCarthy\Gladys
- 301 McCarthy\Milby
- and 1567 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 | 71.3 | first check |
| 2026-07-30 | 71.3 | no change |
| 2026-07-31 | 71.3 | no change |
| 2026-08-01 | 71.3 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
11 findings, ordered by severity.
Show every finding
- Warning4832 instances
4832 of 4832 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)
- Warning2137 instances
2137 of 4832 trips lack rider-facing destination or direction text.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1817 instances
1817 of 1817 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)
- Warning42 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning20 instances
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning6 instances
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.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: 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 service calendars have no days of the week switched on.
Trips tied to these calendars never run; they are dead data that can mask real schedule problems.
Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)
Finding code: service_has_no_active_day_of_the_week · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 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
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · 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 Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make 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 133 days.
- 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 4832 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. 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 133 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 132 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 73 / 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 100 / 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 46 / 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/sun-metro/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.