Feed status · checked 2026-08-01
Connect Transit
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 79 minutes 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
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 1492 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
Review the rule documentation for 'invalid_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid url (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points in its category
Add the required column named in the finding to the flagged file.Likely your export tool
A file is missing a column that GTFS requires. Apps may reject the whole file, so riders could lose the affected routes or stops.
⏱ Often an export setting; ask your vendor if it recurs.worth about +12 points in its category
Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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 1492 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
- Invalid url (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'invalid_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
- A file is missing a column that GTFS requires.
- Next action
- Add the required column named in the finding to the flagged file.
- 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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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.
Review the rule documentation for 'invalid_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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 required column named in the finding to the flagged file. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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 1492 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
- 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 Trillium a fix request
This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. 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 10 kinds of issue across 224 instances (5 error, 170 warning, 49 informational).
Service data ended 1492 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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (106, 108, 102).
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.
1146 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Grand & 6th Street", "Grand & Orange", "37th St E & Baker Dr", 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 1195 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.
- 102 (teal)
- 106 (pink)
- 103 (blue)
- 104 (gray)
- 101 (red)
- 105 (teal)
- 107 (yellow)
- Angleton (purple)
- Freeport (red)
- Regional (yellow)
- Clute/Lake Jackson (green)
- Lake Jackson/Clute (teal)
- 108 (yellow)
| Route | Type | Line color |
|---|---|---|
| 102 La Marque South | Bus | teal |
| 106 Texas City Express | Bus | pink |
| 103 Texas City North | Bus | blue |
| 104 Texas City South | Bus | gray |
| 101 La Marque North | Bus | red |
| 105 Dickinson | Bus | teal |
| 107 Bacliff/San Leon | Bus | yellow |
| Angleton | Bus | purple |
| Freeport | Bus | red |
| Regional | Bus | yellow |
| Clute/Lake Jackson | Bus | green |
| Lake Jackson/Clute | Bus | teal |
| 108 La Marque Saturday | Bus | yellow |
List every stop
- Grand & 6th Street
- Grand & Orange
- UTMB
- 37th St E & Baker Dr
- California Ave & 37th St E
- FM 517 & 24th St
- Yellowstone Street & Ave H
- Ave G & Wharton St
- Ave G & Terry St
- Quintana St & Ave F
- Ave F & Old River St
- Perry & Gulf Blvd
- 2nd & W. Park
- 4th & Navigation
- 6th & Navigation
- Hwy 332 & Liberty
- Lake Rd. & Plum Circle
- Lake Rd. @ Kohl`s
- This Way @ Carriage Inn
- Orange @ BC Health Clinic
- Peach & Parrish
- Hwy 332 @ Top China
- 288B at the Parker Hotel
- Oak Drive at DR Park
- Lake Rd @ Lake Road Offices
- Lake Road at Academy Sports
- TDECU
- Oak Drive and Circle Way
- Loganberry Street at The Gateway
- Garland & Hwy 332
- Garland Dr & Heather Ln
- Plantation Drive at BC Justice of Peace
- Oak Park Drive at Aston Oaks Apts
- Yellowstone Street & Ave H
- Orange @ BC Health Clinic
- Anderson Street and Rice Street
- Walmart
- Hwy 35 & BC Courthouse East Annex SB
- Downing Street and Cedar Street
- Pecan Street at HEB
- FM 517 & Nevada St
- FM 517 & Sweeny Dr.
- FM 646 @ Chevron
- FM 517 & Timber St
- FM 517 & Birch Dr.
- FM 517 & Oak Dr
- FM 517 & Yupon St.
- FM 517 & Termini St.
- FM 517 @ Dickinson BBQ
- FM 517 & Spruce Dr
- FM 517 @ Carwash
- FM 517 & Hansen Dr.
- FM 646 @ Crowder
- FM 517 & Drake Run Ln
- Hobby Lobby @ Outer edge
- I-45 @ Garden Center
- FM 646 & Misty Bay Dr.
- FM 517 & Lobit Dr
- FM 517 @ Vellejo Apts
- FM 517 & Cedar Dr.
- Wal Mart @ Outer edge
- FM 517 & Kellner Rd.
- 23rd St. & Colorado Ave
- California Ave. & Abbie Ln.
- SH 3 @ Citgo
- Vauthier St. & Taylor St.
- I - 45 @ Big League
- FM 646 & Lowes
- FM 646 & Brookport Rd.
- Texas Ave. & 25th St.
- Walker @ Victory Apts.
- I-45 @ Boot Barn
- Deats & Timber Dr
- FM 517 & Dove Meadows Dr.
- Deats & Oak Dr
- FM 646 & High Point
- I-45 @ Shipley`s
- I - 45 @ Freddy`s
- FM 517 & Video St.
- 30th St. & Kansas St.
- Colorado Ave. & 34th St.
- FM 646 & Diamond Bay Dr.
- I-45 Feeder & Calder Dr.
- Deats St. & Ave. D
- I - 45 @ Memorial Herman
- Walker St. & Kessler
- Deats St. & Ohio Ave.
- FM 517 @ Kroger
- FM 1765 & Durox St.
- FM 646 & Bay Colony Dr
- SH 3 @ 29th St.
- League City P&R
- Deats St. & Bayou Animal
- JC Penny @ Outer edge
- FM 517 & Bordens Gully Dr
- California Ave. & Allsseitz
- FM 646 @ 2251 Strip Center
- FM 1765 & Algeria St.
- FM 517 & Kansas Ave
- SH 3 @ 30th St
- 30th St. & Galveston
- 23rd St. & Missouri Ave.
- Goodwill @ Outer edge
- Ave. G & 30th St
- Best Buy @ Outer edge
- Deats St. & MLK Ave
- Vauthier St. @ La Marque H.S.
- FM 1765 & Albert St.
- 30th St. & California Ave.
- Walker St. & Jag Hollow
- Deats & Richards Dr.
- FM 1765 & Vauthier St.
- Colorado Ave. & 32nd St.
- FM 517 & Texas Ave
- FM 517 @ Medical Park
- W. League City @ Shell
- 27th St. & Colorado Ave.
- I - 45 @ Wells Fargo
- FM 646 & Diamond Bay Dr.
- Colorado Ave. & 40th St.
- Colorado Ave. & 28th St.
- FM 517 & Elm Dr.
- 30th St. & Texas Ave.
- Deats & Maple Dr
- FM 517 & Nichols Ave.
- Colorado Ave. & 36th St.
- FM 517 & Pabst Dr
- Ave. G & 29th St.
- FM 517 @ Chevron
- FM 646 & Cross Colony Dr.
- McKinney St. & So. Heights St
- FM 1765 & Crockett St
- FM 517 & Rau Dr.
- FM 1765 & Cobb St.
- FM 646 & Bay Creek Dr
- Durox St. @ Westridge Apts.
- FM 1765 & Washington St.
- FM 646 @ Target
- 30th St. & Houston Ave.
- Newman St. & Hoover St.
- I - 45 @ Chili`s
- Mc Kinney St. & Feeder IH-45
- FM 517 & St. Elizabeth
- Deats & Timber Ln.
- 23rd St. & Houston Ave.
- FM 517 & Evergreen Dr
- FM 1765 & Bell St.
- Vauthier St. & Virginia St.
- FM 646 & Bay Creek Dr.
- FM 1765 & Fulton St.
- FM 517 & Hill Ave.
- Deats & Spruce Dr.
- Colorado Ave. & 38th St.
- FM 1765 & Willis St.
- FM 517 & Chevron
- 30th St. & Missouri Ave.
- 30th St. & Colorado Ave.
- FM 517 & Hughes Ln
- I - 45 @ Cabella`s
- Deats & Ave G
- UTMB @ Outer edge
- Durox St. & McKinney St.
- Colorado Ave. & FM 517
- Deats & Ash Dr
- Deats & Hollister Apts
- Newman St. @ Prepatory
- FM 1765 & Bernice St.
- FM 646 & Misty Bay Dr.
- Vauthier St. & McKinney St
- Vauthier St. & Mar-Ann St.
- Texas Ave. & 27th St.
- Deats & Yupon Dr
- Vauthier St. & McArthur St
- Vauthier St. & Cedar St.
- Cedar St. @ U-Haul
- Cedar St. & Westward St.
- Cedar St. & Camp Circle St.
- Cedar & Veronica
- Cedar St. & Kirsten St.
- Cedar St. & Bowie St.
- Cedar St. & Foreman St.
- Cedar St. Bayou St.
- Cedar St. & Laurel St.
- Cedar St. & Howell St.
- Laurel St. & Estates St.
- Laurel St. @ USPS
- 1st St. & Elmo St.
- Laurel St. & Yupon St.
- Cedar St. @ Cedar Dr. Village
- SH 3 & Holly St.
- SH 3 & Ross St.
- SH 3 & Larcom St.
- SH 3 & Prune St.
- SH 3 & Pear St.
- SH 3 & Delmar St.
- SH 3 & Plum St.
- SH 3 & Orange St.
- SH 3 & 4th Ave.
- Main St. & 6th Ave.
- SH 3 & Hathaway St.
- Main St. & Glendale St.
- Main St. & Howell St.
- Main St. & 9th Ave.
- Main St. & 12th Ave.
- Main St. & 5th Ave.
- Bayou St. & Little St.
- Bayou St. & Oleander St.
- FM 1765 & Porter St.
- FM 1765 & Albert St.
- Bayou St. & Magnolia St.
- Cedar St. & Cora St.
- Lake St. & FM 1765
- Lake St. & Jackson St.
- Stewart St. & Nasby St.
- Nashby St. & Bayou St.
- Bayou St. & Neuman St.
- College of Mainland
- Lake St. & Kansas St.
- Westward & Woodrow
- Memorial @ Space Dialysis
- Lake St. & Thompson St.
- Cedar St. & Roosevelt St.
- Westward & Park
- COM/DPS
- Dogwood & 25TH Ave.
- 25th & Highway 3
- FM 1764 @ Retreat Apts.
- FM 1764 @ Gatsby
- FM 1764 @ Twelve Oaks
- FM 1764 @ Sand Castle
- FM 1764 @ Gal. Daily News
- FM 1764 @ Amburn Foodmart
- FM 1764 @ Peachtree
- FM 1764 @ Storage
- FM 1764 @ Office Depot
- FM 1764 @ Farmers Copper
- FM 1764 @ M.O.M.
- FM 1765 @ Highway Inn Suites
- Dollar Tree @ Gulfway Plaza
- Bayou @ Library
- FM 1765 & Newman St
- FM 1765 & Westward
- FM 1765 @ CVS
- Westward & Taylor
- FM 1764 @ JSC Bank
- FM 1765 & Willis
- FM 1764 @ Gamestop
- Westward & McArthur St.
- Bayou & Laura
- FM 1765 @ Byrd St.
- and 945 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 | 35.8 | first check |
| 2026-07-30 | 35.8 | no change |
| 2026-07-31 | 35.8 | no change |
| 2026-08-01 | 35.8 | 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
15 findings, ordered by severity.
Show every finding
- Error3 instances
Invalid url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error2 instances
A file is missing a column that GTFS requires.
Apps may reject the whole file, so riders could lose the affected routes or stops.
Fix: Add the required column named in the finding to the flagged file. (Often an export setting; ask your vendor if it recurs.)
Finding code: missing_required_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Service data ended 1492 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)
- Warning1195 instances
1195 of 1195 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)
- Warning214 instances
214 of 214 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)
- Warning179 instances
179 of 214 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)
- Warning158 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.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning7 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)
- Warning3 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
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date7_days · 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
This feed describes flexible (demand-responsive) service but has no booking_rules.txt.
Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.
Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)
Finding code: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info37 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.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info9 instances
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)
- Info3 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · 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.
Flex zones are published but no booking_rules.txt is present.
Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. 2 validator errors to resolve. Service data expired 1492 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 2 validator errors to resolve.
- Current Not ready
- Service data expired 1492 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 214 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. 2 validator errors to resolve. Service data expired 1492 days ago. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 2 validator errors to resolve.
- Current Not yet
- Service data expired 1492 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 158 of 1195 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.
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. The feed also carries 5 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
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 48 / 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 47 / 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/connect-transit/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.