Feed status · checked 2026-08-01
LeeTran
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Florida.
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 9 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
1550 of 1550 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
2522 of 2522 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
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool
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.
⏱ Often a bulk fix in your scheduling software.worth about +8 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
- 1550 of 1550 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
- 2522 of 2522 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
- Some rider-facing names are in ALL CAPS or all lowercase.
- Next action
- Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
- 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.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · 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 109 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 1580 instances (0 error, 1580 warning, 0 informational).
Service data covers the next 109 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
17 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (10, 100, 110, 120, 130, 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.
1515 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("EDISON MALL DR @ SOLOMON BLVD", "WNKLR AVE @ BROADWAY AVE", "WNKLR AVE @ CENTRAL AVE", 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 1550 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.
- 10 (green)
- 100 (pink)
- 110 (brown)
- 120 (pink)
- 130 (teal)
- 140 (pink)
- 15 (pink)
- 20 (teal)
- 240 (brown)
- 30 (purple)
- 40 (green)
- 410 (gray)
- 490 (pink)
- 5 (teal)
- 50 (brown)
- 515 (white)
- 590 (gray)
- 595 (orange)
- 60 (white)
- 600 (teal)
- 70 (purple)
- 80 (brown)
| Route | Type | Line color |
|---|---|---|
| 10 Route 10 | Bus | green |
| 100 Route 100 | Bus | pink |
| 110 Route 110 | Bus | brown |
| 120 Route 120 | Bus | pink |
| 130 Route 130 | Bus | teal |
| 140 Route 140 | Bus | pink |
| 15 Route 15 | Bus | pink |
| 20 Route 20 | Bus | teal |
| 240 Route 240 | Bus | brown |
| 30 Route 30 | Bus | purple |
| 40 Route 40 | Bus | green |
| 410 Route 410 | Bus | gray |
| 490 Route 490 | Bus | pink |
| 5 Route 5 | Bus | teal |
| 50 Route 50 | Bus | brown |
| 515 Route 515 | Bus | white |
| 590 Route 590 | Bus | gray |
| 595 Route 595 | Bus | orange |
| 60 Route 60 | Bus | white |
| 600 Route 600 | Bus | teal |
| 70 Route 70 | Bus | purple |
| 80 Route 80 | Bus | brown |
List every stop
- EDISON MALL TRANSFER CTR
- EDISON MALL DR @ SOLOMON BLVD
- WNKLR AVE @ BROADWAY AVE
- WNKLR AVE @ CENTRAL AVE
- WNKLR AVE@ EVANS AVE-EB
- WNKLR AVE @ THE PALM APTS
- WNKLR AVE @ CENTER POINTE DR
- WNKLR AVE @ METRO PKWY
- WNKLR AVE @ METRO PKWY-EB1
- FORD ST EXT @ WNKLR AVE EXT
- FORD ST EXT @ KERNEL CIR
- WNKLR AVE @ SCHOOLHOUSE RD-EB1
- WNKLR AVE @ SHOEMAKER BLVD
- Winkler Ave @ Aria Landings
- WNKLR AVE @ PROVINC PK BLVD
- COLONIAL BLVD @ WNKLR AVE
- WNKLR AVE @ SCHOOLHOUSE RD-EB2
- WNKLR AVE @ METRO PKWY-WB
- WNKLR AVE @ CENTER POINTE DR 1
- WNKLR AVE @ CENTER POINTE DR 2
- WNKLR AVE@ EVANS AVE-WB
- EVANS AVE @ WNKLR AVE 1
- EVANS AVE @ WNKLR AVE 2
- EVANS AVE@ PARK WINDSOR DR 1-NB
- EVANS AVE@ PARK WINDSOR DR 2-NB
- EVANS AVE @ CARRELL RD
- FOWLER ST @ CARRELL RD
- FOWLER ST@ HUNTER ST-NB
- FOWLER ST@ MORENO AVE-NB
- FOWLER ST@ HANSON ST-NB
- FOWLER ST@ MAPLE AVE-NB
- FOWLER ST @ CANAL ST
- FOWLER ST@ STELLA ST-NB
- FOWLER ST@ FRANKLIN ST-NB
- EDISON AVE @ ROYAL PALM AVE
- EDISON AVE @ JACKSON ST 1
- JACKSON ST @ CRAWFORD ST
- ROSA PARKS TRANSPORTATION CTR
- MLK BLVD @ EVANS AVE-EB
- MLK BLVD @ CRANFORD AVE-EB
- MLK BLVD @ PALM AVE-EB1
- SOLOMON BLVD @ WNKLR AVE
- S TAMIAMI TRL @ COMMONS WAY
- S TAMIAMI TRL @ COUNTY RD
- S TAMIAMI TRL @ LORDS WAY ST
- STARS COMPLEX-EB
- EDISON AVE@ WRIGHT ST-EB
- EDISON AVE@ FORD ST-EB
- EDISON AVE@ HENDERSON AVE-EB
- S TAMIAMI TRL @ JACK RABBIT RUN
- S TAMIAMI TRL @ HICKORY DR
- SHOEMAKER BLVD @ DALE ST 2
- SHOEMAKER BLVD @ B ST
- SHOEMAKER BLVD@ MICHIGAN AVE-NB
- MICHIGAN AVE @ BERT DR
- MICHIGAN AVE@ DIEGO ST-EB
- S TAMIAMI TRL @ SANIBEL BLVD
- SANTA BARB BLVD @ AVIATION PKWY
- MICHIGAN AVE LINK @ A ST
- LEE BLVD @ OLYMPIA POINTE BLVD
- MICHIGAN AVE LINK @ MARSH AVE
- HEALTH DEPT.-WB
- MICHIGAN AVE@ DIEGO ST-WB
- SHOEMAKER BLVD@ MICHIGAN AVE-SB
- SHOEMAKER BLVD @ DALE ST 1
- LEE BLVD @ SILVER BIRCH WAY
- EDISON AVE@ HENDERSON AVE-WB
- EDISON AVE@ FORD ST-WB
- EDISON AVE@ WRIGHT ST-WB
- STARS COMPLEX-WB
- TAMIAMI TRL @ SHADOW CREEK BLVD
- S TAMIAMI TRL @ OLD US 41
- MLK BLVD @ CRANFORD AVE-WB
- MLK BLVD @ LEE ST
- HEALTH DEPT.-EB
- EDISON AVE @ JACKSON ST 2
- FOWLER ST@ FRANKLIN ST-SB
- FOWLER ST @ SOUTH ST
- FOWLER ST@ STELLA ST-SB
- FOWLER ST@ MAPLE AVE-SB
- FOWLER ST@ HANSON ST-SB
- FOWLER ST@ MORENO AVE-SB
- FOWLER ST@ HUNTER ST-SB
- CARRELL RD @ FOWLER ST
- CARRELL RD @ EVANS AVE
- EVANS AVE@ PARK WINDSOR DR 1-SB
- EVANS AVE@ PARK WINDSOR DR 2-SB
- S TAMIAMI TRL @ OLD US 41-NB
- EVANS AVE @ WNKLR AVE
- WNKLR AVE @ FOWLER ST 2
- SHMKR @ LORA ST
- MCGREGOR BLVD @ VIRGINIA AVE
- W FIRST ST @ MCGREGOR BLVD
- W FIRST ST @ WILNA ST
- W FIRST ST @ BAYSIDE PKWY
- W FIRST ST @ HENLEY PL
- HEITMAN ST @ BAY ST-NB
- METRO PKWY @ 6 MILE CYPRESS
- LEE ST @ MLK BLVD
- MLK BLVD @ PALM AVE-EB2
- MLK BLVD @ BROWN ST
- MLK BLVD @ PAULDO ST
- MLK BLVD @ DAVIS ST
- MLK BLVD @ HIGHLANDS AVE
- MLK BLVD @ BARKER BLVD
- MLK BLVD @ TOWLES ST-EB
- MLK BLVD @ FLINT DR-EB
- MLK BLVD @ ROCKFILL RD-EB
- MARSH AVE @ MICHIGAN AVE
- MARSH AVE @ EUGENIA AVE-NB
- MARSH AVE @ BALLARD RD-NB
- MARSH AVE @ NEW YORK AVE-NB
- MARSH AVE @ ARLINGTON AVE-NB
- MARSH AVE @ MADISON AVE
- MARSH AVE @ WOODSIDE AVE-NB
- MARSH AVE @ GREENWOOD AVE-NB
- MARSH AVE @ GLENWOOD AVE-NB
- MARSH AVE @ PALM BEACH
- MARSH AVE @ GLENWOOD AVE-SB
- MARSH AVE @ GREENWOOD AVE-SB
- MARSH AVE @ WOODSIDE AVE-SB
- MARSH AVE @ ARLINGTON AVE-SB
- MARSH AVE @ NEW YORK AVE-SB
- MARSH AVE @ BALLARD RD-SB
- MARSH AVE @ EUGENIA AVE-SB
- MARSH AVE @ MICHIGAN AVE-SB
- MARSH AVE @ MICHIGAN AVE LINK
- MLK BLVD @ JACKSONVILLE ST
- MLK BLVD @ ROCKFILL RD-WB
- VICTORIA AVE @ GRAND AVE
- MLK BLVD @ FLINT DR-WB
- MLK BLVD @ TOWLES ST-WB
- MLK BLVD @ NELSON TILLIS BLVD
- METRO PKWY @ DIAMOND CENTRE CT
- MLK BLVD @ STARNES AVE
- MLK BLVD @ DAVIS BLVD
- MLK BLVD @ FOUNTAIN ST
- Fort Myers Dream Center - MLK BLVD @ FORD ST-WB
- MLK BLVD @ HIGH ST
- MLK BLVD @ VELASCO ST
- MLK BLVD @ PALM AVE-WB
- MLK BLVD @ EVANS AVE-WB
- LEE ST @ EDWARDS DR
- METRO PKWY @ ALLIANCE LN
- W FIRST ST @ HENLEY PL
- W FIRST ST @ CLIFFORD ST
- VICTORIA AVE @ HEITMAN ST
- VICTORIA AVE @ BROADWAY-EB1
- Daniels Pkwy @ Bell Tower Dr
- COLLEGE PKWY @ S CLEVELAND AVE
- COLLEGE PKWY @ KENWOOD LN-WB
- COLLEGE PKWY @ S PROVINCE BLVD-EB
- COLLEGE PKWY @ UNIVERSITY DR-EB
- COLLEGE PKWY @ SUMMERLIN RD
- FSW - COLLEGE PKWY @ WHISKEY CREEK DR
- COLLEGE PKWY @ RIVERWALK PK BLVD-EB1
- COLLEGE PKWY @ RIVERWALK PK BLVD-EB2
- COLLEGE PKWY @ PREMIERE BLVD-EB 2
- COLLEGE PKWY @ COLLEGE POINTE CT-WB
- COLLEGE PKWY @ MCGREGOR BLVD-WB
- CC PWKY @ SE 17TH PL-WB
- CC PWKY @ SE 15TH AVE
- CC PWKY @ VINCENNES BLVD
- CC PWKY @ SE 10TH PL
- CAPE CORAL TRANSFER CENTER
- CC PWKY @ CORONADO PKWY
- CC PWKY @ TRITON CT E
- CC PWKY @ PALM TREE DR
- CC PWKY @ LUCAYA DR
- CC PWKY @ SE 2ND CT
- CC PWKY @ SANTA BARBARA BLVD-WB
- CC PWKY @ SW 2ND AVE-WB
- CC PWKY @ PELICAN BLVD-WB
- CC PWKY @ SW 5TH PL-WB
- CC PWKY @ SKYLINE BLVD-EB
- SKYLINE BLVD @ SW 47TH TER-NB1
- SKYLINE BLVD @ SW 47TH ST-NB
- SKYLINE BLVD @ SW 43RD LN
- SKYLINE BLVD @ SW 43RD TER
- SKYLINE BLVD @ SW 47TH TER-NB2
- MOHAWK PKWY @ SKYLINE BLVD-WB
- CAPE CORAL LIBRARY -WB
- MOHAWK PKWY @ SW 13TH AVE
- MOHAWK PKWY @ SW 15TH PL-WB
- CHIQUITA BLVD S @ BEACH PKWY
- CHIQUITA BLVD S @ SW 44TH TER-SB
- CHIQUITA BLVD S @ SW 48TH TER
- Camelot Isles - SW 49TH TER @ SW 16TH PL
- SW 17TH PL @ SW 49TH TER
- CHIQUITA BLVD S @ SW 47TH TER-SB
- CHIQUITA BLVD S @ SW 44TH TER-NB
- CHIQUITA BLVD S @ SW 43RD ST
- MOHAWK PKWY @ SW 15TH PL-EB
- MOHAWK PKWY @ SW 12TH PL
- CAPE CORAL LIBRARY -EB
- MOHAWK PKWY @ SKYLINE BLVD-EB
- SKYLINE BLVD @ SW 40TH TER
- SKYLINE BLVD @ SW 42ND TER
- SKYLINE BLVD @ SW 44TH ST
- CC PWKY @ SKYLINE BLVD-WB
- CC PWKY @ SW 5TH PL-EB
- CC PWKY @ PELICAN BLVD-EB1
- CC PWKY @ PELICAN BLVD-EB2
- CC PWKY @ SW 2ND AVE-EB
- CC PWKY @ SANTA BARBARA BLVD-EB
- CAPE CORAL PKWY @ SE 6 AVENUE
- CC PWKY @ LUCAYA DR
- CC PWKY @ SUNSET CT
- CC PWKY @ TARPON CT
- CC PWKY @ LEONARD ST
- CC PWKY @ VINCENNES ST
- CC PWKY @ DEL PRADO BLVD S
- CC PWKY @ WAIKIKI AVE
- CC PWKY @ CAPE CORAL BRIDGE RD
- COLLEGE PKWY @ MCGREGOR BLVD-EB
- COLLEGE PKWY @ COLLEGE POINTE CT-EB
- COLLEGE PKWY @ SOUTH POINTE BLVD
- COLLEGE PKWY @ PREMIERE BLVD-EB 1
- FLORIDA SW STATE COLLEGE-WB
- COLLGE PKWY @ RIVERWLK PARK BLVD
- COLLEGE PKWY @ WATERFORD CIR
- COLLEGE PKWY @ FSW PKWY
- COLLEGE PKWY @ UNIVERSITY DR-WB
- COLLGE PKWY @ QUEEN ELIZABETH WY
- COLLEGE PKWY @ S PROVINCE BLVD-WB
- COLLEGE PKWY @ KENWOOD LN-EB1
- COLLEGE PKWY @ KENWOOD LN-EB2
- CORALWOOD MALL @ SE 22ND LN
- COUNTRY CLUB BLVD @ SE 24TH ST-NB
- COUNTRY CLUB BLVD @ SE 22ND TER
- COUNTRY CLUB BLVD @ SE 21ST TER
- COUNTRY CLUB BLVD @ SE 20TH ST
- COUNTRY CLUB BLVD @ SE 19TH TER-NB
- COUNTRY CLUB BLVD @ SE 18TH ST
- COUNTRY CLUB BLVD @ SE 16TH TER
- COUNTRY CLUB BLVD @ SE 14TH ST
- COUNTRY CLUB BLVD @ SE 9TH TER
- SE 13TH CT @ SE 8TH TER
- DEL PRADO BLVD S @ SE 6TH ST
- DEL PRADO BLVD S @ SE 4TH ST
- DEL PRADO BLVD S @ SE 2ND ST
- DEL PRADO BLVD @ HANCK BRDG PKWY
- DEL PRADO BLVD N @ NE 2ND ST
- DEL PRADO BLVD N @ NE 2ND TER
- DEL PRADO BLVD N @ NE 3RD TER
- DEL PRADO BLVD N @ NE 6TH TER
- PINE ISLAND RD @ DEL PRADO BLVD
- PINE ISLAND RD @ NE 15TH AVE
- PINE ISLAND RD @ NE 10TH PL
- PINE ISLAND RD @ ANDALUSIA BLVD
- and 1300 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 | 66.6 | first check |
| 2026-07-30 | 66.7 | up 0.1 |
| 2026-07-31 | 66.7 | no change |
| 2026-08-01 | 66.7 | 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
11 findings, ordered by severity.
Show every finding
- Warning2522 instances
2522 of 2522 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)
- Warning1565 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)
- Warning1550 instances
1550 of 1550 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)
- Warning4 instances
Some route lines list the same point twice in a row.
Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)
Finding code: equal_shape_distance_same_coordinates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
Some values have extra spaces at the start or end.
A stray space can break a match, so a stop or route may fail to link across files.
Fix: Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this. (Usually one export setting.)
Finding code: leading_or_trailing_whitespaces · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 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)
- Warning2 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)
- Warning2 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)
- Info1491 instances
About 1491 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 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 109 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 2522 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 109 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 109 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 68 / 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 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/leetran/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.