Feed status · checked 2026-08-01
Lake County Connection
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 1 days ago; last changed 38 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
507 of 507 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
193 of 193 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 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
- 507 of 507 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
- 193 of 193 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
- 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.
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 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. 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 60 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
- No fare information is published in the feed.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send your vendor a fix request
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 2 kinds of issue across 14 instances (0 error, 14 warning, 0 informational).
Service data covers the next 60 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 not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (27).
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.
494 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Citizens Blvd & Citizens Blvd", "U.S 27 & Sunshine Ave", "U.S 27 & Center St", 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.
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 507 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 1 (teal)
- 1A (orange)
- 2 (purple)
- 27 (red)
- 3 (teal)
- 4 (red)
- 50 (brown)
- 55 (teal)
- SLX (yellow)
| Route | Type | Line color |
|---|---|---|
| 1 Leesburg to Eustis | Bus | teal |
| 1A Summerfield to Leesburg | Bus | orange |
| 2 Leesburg Circular | Bus | purple |
| 27 Express Leesburg to Clermont | Bus | red |
| 3 Mount Dora Circular | Bus | teal |
| 4 Altoona to Zellwood | Bus | red |
| 50 Mascotte to Winter Garden | Bus | brown |
| 55 Four Corners Circular | Bus | teal |
| SLX Clermont to Four Corners | Bus | yellow |
List every stop
- Cagan Stop
- Paige Pl & Main St
- U.S 441 & Avenida Central
- U.S 441 & Rolling Acres
- U.S 441 & Fennell Blvd
- U.S 441 & Teague Trail
- U.S 441 & Guava
- U.S 441 & Lemon St
- U.S 441 & Lady Lake
- U.S 441 & W Lakeview St
- U.S 441 & Griffin View
- U.S 441 & Orange
- U.S 441 & Longview Ave
- U.S 441 & Hartsock Sawmill
- U.S 441 & Temple Hill
- U.S 441 & Eagles Nest
- U.S 441 & Phillips GMC Buick
- U.S 441 & S Grays Airport Rd
- U.S 441 & Spring Lake
- U.S 441 & Fair Oaks Dr
- U.S 441 & Cooke St
- N Dixie Ave & Shiloh St
- N Dixie Ave & W Miller St
- N Dixie Ave & Fountain St
- Berckman St & Lime St
- Mirror Lake Dr & Mirror Lake Manor
- Fruitland St & Seminole Ave
- S Dixie Ave & Forest St
- S Dixie Ave & Urick St
- Thomas Ave & Siver Pointe Apart.
- MLK & U.S 441
- U.S 441 & Indian Tr
- U.S 441 & Picciola Rd
- U.S 441 & Tally
- U.S 441 & Bealls & Rural King
- U.S 441 & Akron
- U.S 441 & U.S HWY 27/441
- U.S 441 & Griffin Rd
- U.S 27 & Williams St
- Citizens Blvd & Citizens Blvd
- U.S 441 & Griffin Rd
- U.S 441 & Hess/North Shore
- U.S 441 & Bealls
- U.S 441 & Picciola
- U.S 441 & Eureka Ave
- US 442 & Indian Tr
- MLK & Walmart
- MLK & Sennet Drive
- Thomas Ave & Silver Pointe
- S Dixie Ave & Palm St
- S Dixie Ave & Forest St
- W Fruitland St & Gardenia Ave
- Mirror Lake Dr & Mirror Lake Manor
- Fruitland Park Library
- Berckman St & Lime St
- S Dixie Ave & Fountain St
- N Dixie Ave & W Miller St
- N Dixie Ave & Shiloh St
- U.S 441 & Register Rd
- U.S 441 & Fair Oaks Dr
- U.S 441 & American Ln
- U.S 441 & S Grays Airport
- U.S 441 & Shadow Hill
- U.S 441 & Eagles Nest
- U.S 441 & Sunrise Rd
- U.S 441 & Cove Apts
- U.S 441 & Edwards Rd
- U.S 441 & Griffin View Dr
- U.S 441 & E Lakeview
- U.S 441 & E Lady Lake
- U.S 441 & Hermosa
- U.S 441 & Water Oaks Blvd
- U.S 441 & Fennel Blvd
- U.S 441 & Rolling Acres
- U.S 441 & Rolling Acres
- US 441 & Griffin Ave
- Spanish Springs Golf Cart Bridge
- US 441 & Bella Cruz Dr
- Walmart Summerfield
- US441 & SE 109th Ave
- VIllages Hospital
- US 441 & Lagarde Blvd
- US 441 & Plaza Blvd
- U.S 441 & Newman Dr
- U.S 441 & Perkins St
- U.S 441 & 3rd St
- U.S 441 & Palmetto St
- U.S 441 & Canal St
- Lake St & U.S 441
- Lake St & Magnolia St
- Lake St & Dixie Ave
- E Dixie Ave & Manatee Dr
- E Dixie Ave & Lake Port Blvd
- E Dixie Ave & Baker St
- E Dixie Ave & Main St
- U.S 441 & Nichols Dr
- U.S 441 & Michigan Ave
- U.S 441 & Ice Cream
- U.S 441 & Fern Dr
- U.S 441 & Brittany
- U.S 441 & Tomato Hill
- U.S 441 & Sleepy Hollow
- U.S 441 & Professional Dr
- U.S 441 & Comcast
- U.S 441 & Airport View
- U.S 441 & Tavares Ave
- U.S 441 & Wilco Dr
- U.S 441 & Echo Dr
- U.S 441 & College Dr
- U.S 441 & Crofton Dr
- U.S 441 & Skinner Ave
- U.S 441 & Radio Rd
- U.S 441 & Haven Ct
- U.S 441 & Kinne Pearce Rd
- U.S 441 & CR 473
- U.S 441 & Blanton Ln
- U.S 441 & Hiltop Rd
- SR 19 & Lake Ave
- W Main St & S Lake Ave
- W Main St & N Pulsifer Ave
- W Main St & Texas Ave
- W Main St & Rockingham Ave
- Dora Ave & Terrace St
- Dora Ave & Greenway Ave
- Dora Ave & Mt. Homer Rd
- Dora Ave & Smith Ave
- David Walker & Classique Ln
- David Walker & U.S 441
- U.S 441 & David Walker
- E Burleigh Blvd & Huffstetler Dr
- Huffstetler Dr & David Walker Dr
- Huffstetler Dr & Dillard Rd
- Dillard Rd & Huffstetler Dr
- Kurt St & Clay Blvd
- W Lakeview & South St
- W Lakeview & Morin St
- S Bay St & Doanne Ave
- S Bay St & Norton Ave
- S Grove St & E Key Ave
- S Grove St & E Lemon Ave
- S Grove St & Orange Ave
- N Center St & Magnolia Ave
- E McDonald Ave & Hawley St
- E McDonald Ave & Salem St
- N Prescott & Clifford Ave
- N Prescott St & Hazzard Ave
- Bates Ave & Exeter St
- Bates Ave & Reddick St
- Bates Ave & Gould St
- Palmetto St & Rose Ln
- Getford Rd & Selleen Dr
- Getford Rd & Louis Ct
- Wall St & Harlem Ave
- Wall St & Suanee Ave
- Wall St & Bates Ave
- Orange Ave & Cardinal St
- Orange Ave & Pine St
- Orange Ave & Morningview Dr
- Orange Ave & Center St
- Bay St & Citrus Ave
- Bay St & Ward Ave
- Bay St & Woodward Ave
- Bay St & Herrick Ave
- Bay St & Stevens Ave
- Bay St & Lakeview Ave
- Bay St & Mills Ave
- Bay St & Taylor Ave
- Bay St & St. Louis Ave
- Bay St & Chesley Ave
- Bay St & Seminole Ave
- Ardice Ave & Ruleme St
- U.S 441 & T.H Poole Sr
- U.S 441 & David Walker Dr
- U.S 441 & Nightingale Ln
- E Burleigh Blvd & Lake Eustis Dr
- E Burleigh Blvd & El Red Dr
- St. Clair Abrams Ave & E Burleigh Blvd
- St. Clair Abrams Ave & Lake Frances Bv
- St. Clair Abrams Ave & Clifford St
- St. Clair Abrams Ave & Esther St
- St. Clair Abrams Ave & Caroline St
- St. Clair Abrams Ave & Maud St
- W Main St & N Pulsifer Ave
- FL 19 & Wells Ave
- S Duncan Dr & Citrus Ave
- S Duncan Dr & Birch Blvd
- S Duncan Dr & Woodlea Rd
- Woodlea Rd & Capt. Haynes Rd
- Captain Haynes Rd & Woodlea Bv
- Dead River Rd & Capt. Haynes Rd
- Dead River Rd & Woodview Dr
- Dead River Rd & Holly Dr
- FL 19 & Maud St
- W Burleigh Blvd & Old U.S 441
- U.S 441 & Hilltop Rd
- U.S 441 & Blanton Ln
- U.S 441 & 7th St
- W Burleigh Blvd & CR 473
- US HWY 441 & Kinne Pearce Rd
- U.S 441 & Lakes Blvd
- U.S 441 & Radio Rd
- U.S 441 & Blossom Ln
- U.S 441 & Skinner Ave
- U.S 441 & Lake Harris
- U.S 441 & Tavares Ave
- U.S 441 & Comcast
- U.S 441 & Professional Dr
- U.S 441 & CR 44
- E Main St & Pat's Pawn
- U.S 441 & Tomato Hill
- U.S 441 & Waters Edge Dr
- E Main St & Ice Cream Rd
- U.S 441 & N Lake Ave
- Newell Hill Rd & Bentley Rd
- Bentley Rd & Yorktown Dr
- Bentley Rd & Weston Rd
- Mills St & E Line St
- U.S 441 & East St
- U.S 441 & Lake St
- U.S 441 & Canal St
- North Blvd & 3rd St
- U.S 441 & Perkins St
- U.S 27 & Sunshine Ave
- U.S 27 & Center St
- U.S 27 & High St
- U.S 27 & Yellow Jacket Way
- U.S 27 & SR 44 (Dixie Ave)
- U.S 27 & Bryant St
- U.S 27 & Emerson St
- Southside Shopping Center
- U.S 27 & Fairfax St
- U.S 27 & Colfax St
- W Dixie Ave & McKenzie St
- W Dixie Ave & Marietta St
- W Dixie Ave & 6th St
- W Dixie Ave & Dozier Cir
- W Dixie Ave & Rambo St
- S Lake St & Pine St
- S Lake St & Magnolia St
- Magnolia St & Palmetto St
- Magnolia St & 7th St
- E Main St & 13th St
- South St & Hood Ave
- South St & Hickory Ave
- South St & Lone Oak Dr
- South St & Coach N Four Dr
- South St & Caballo Rd
- South St & Royal Oak Estates
- South St & Southwind Cove Way
- CR 468 & Main St
- and 257 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 | 77.4 | first check |
| 2026-07-30 | 77.4 | no change |
| 2026-07-31 | 77.4 | no change |
| 2026-08-01 | 77.4 | 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
6 findings, ordered by severity.
Show every finding
- Warning507 instances
507 of 507 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)
- Warning193 instances
193 of 193 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)
- Warning44 instances
44 of 193 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)
- Warning9 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)
- Warning5 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)
- 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)
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 60 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 193 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 60 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 60 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 90 / 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 42 / 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/lake-county-connection-2255/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.