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 74 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 2294 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
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
450 of 452 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
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
⏱ A small file for most flat-fare systems.worth about +15 points in its category
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- Service data ended 2294 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
- 450 of 452 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
- The feed contains no fare information.
- Next action
- Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Re-export 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. 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_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.
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 was 2294 days ago.
- Published accessibility data
- Accessibility information is stated for 0.4% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- No fare information is published in the feed.
- Realtime information
- 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.
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 5 kinds of issue across 20 instances (0 error, 20 warning, 0 informational).
Service data ended 2294 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 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 (50E).
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.
452 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("E Myers Blvd/S Sunset Ave", "E Myers Blvd/Putnam St", "E Myers Blvd/Blett 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 452 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 (blue)
- 1A (pink)
- 2 (green)
- 3 (orange)
- 4 (teal)
- 50W (brown)
- 50E (blue)
| Route | Type | Line color |
|---|---|---|
| 1 Route 1 | Bus | blue |
| 1A Route 1A | Bus | pink |
| 2 Route 2 | Bus | green |
| 3 Route 3 | Bus | orange |
| 4 Route 4 | Bus | teal |
| 50W Route 50W | Bus | brown |
| 50E Route 50E | Bus | blue |
List every stop
- Paige Pl/Main St
- US-441 S/Avenida Central
- US-441 S/Rolling Acres Rd
- US-441 S/Teague Trail
- US-441 S/W Gauva St
- US-441 S/Lemon St
- US-441 S/W Lady Lake Blvd
- US-441 S/W Lakeview St
- US-441 S/Griffin View Dr
- US-441 S/Orange St
- US-441 S/Morningside Ave
- US-441 S/Hartstock Sawmill Rd
- US Hwy 441/Temple Hill Rd
- US Hwy 441/Eagles Nest Rd
- US Hwy 441/S Grays Airport Rd
- US Hwy 441/S Grays Airport Rd
- US Hwy 441/American Ln
- US-441 S/Fair Oaks Dr
- US-441 S/Cook St
- N Dixie Ave/Shiloh St
- N Dixie Ave/W Miller St
- N Dixie Ave/Fountain St
- W Berckman St/Lime St
- E Mirror Lake Dr/Railroad St
- Seminole Ave/W Fruitland St
- S Dixie Ave/Forest St
- Thomas Ave/Silver Point Cir
- Dr Martin Luther King Jr Blvd/Citrus Blvd
- Citrus Blvd/Indian Trail
- US-441 S/Picciola Rd
- Citrus Blvd/Tally Rd
- Citrus Blvd/Akron Dr
- N 14th St/Akron Dr
- N 14th St/Griffin Rd
- N 14th St/Hill St
- N 14th St/William St
- Citizens Blvd/N 14th St
- N 14th St/Griffin Rd
- N 14th St/N Shore Dr
- US-441 S/Florida Ave
- US-441 S/Georgia Ave
- US-441 S/Eureka Ave
- Citrus Blvd/Indian Trail
- Dr Martin Luther King Jr Blvd/US-441 S
- Dr Martin Luther King Jr Blvd/Sennet Dr
- Thomas Ave/Silver Pointe Cir
- S Dixie Ave/Forest St
- W Fruitland St/Gardenia Ave
- E Mirror Lake Dr/Railroad St
- W Berckman St/Lime St
- N Dixie Ave/E Berckman St
- N Dixie Ave/E Catawba St
- N Dixie Ave/Shiloh St
- US-441 S/Register Rd
- Citrus Blvd/American Ln
- US Hwy 441/American Ln
- US Hwy 441/S Grays Airport Rd
- US Hwy 441/Arbor Ridge Blvd
- US Hwy 441/Eagles Nest Rd
- US-441 S/Sunrise Rd
- US-441 S/Morningside Ave
- US-441 S/Edwards Rd
- US-441 S/Oak Hill Rd
- US-441 S/E Lakeview St
- US-441 S/E Lady Lake Blvd
- US-441 S/W Hermosa St
- US 441 S/Water Oak Blvd
- US 441 S/Fennel Blvd
- US-441 S/Rolling Acres Rd
- US-441 S/Rolling Acres Rd
- US 441 S/Avenida Central
- US-441 S/Avenida Central
- US-441 S/Main St
- North Blvd W/Perkins St
- W NBlvd/Perkins St
- North Blvd/N 3rd St
- North Blvd W/N Palmetto St
- N Lake St/E Main St
- S Lake St/E Main St
- S Lake St/Douglas St
- E Dixie Ave/Jordan St
- E Dixie Ave/June Dr
- E Dixie Ave/Baker St
- E Dixie Ave/Crosby St
- North Blvd E/Nichols Dr
- E Main St/Michigan Ave
- E Main St/Fern Dr
- E Main St/Waterside Edge Dr
- US-441/Tomato Hill Rd
- E Main St/Sleepy Hollow Rd
- US-441 S/Professional Dr
- US-441 S/FL-44
- US-441 S/Airport View
- US-441 S/Wilco Dr
- US-441 S/College Dr
- US-441 S/College Dr
- US-441 S/Crofton Dr
- US-441 S/Skinner Ave
- US-441 S/Mapache Ln
- US-441 S/Haven Ct
- US-441 S/Kinne Pearce Rd
- US-441 S/Bluegill Ave
- US-441 S/7th Sunfish St
- US-441 S/Blanton Ln
- US-441 S/Hilltop Rd
- N Duncan Dr/N Lake Ave
- W Main St/S Lake Ave
- W Main St/N Pulsifer Ave
- W Main St/N Texas Ave
- E Main St/N Rockingham Ave
- Dora Ave/Terrace St
- Dora Ave/Greenway Ave
- Dora Ave/Mt Homer Rd
- Dora Ave/Smith Ave
- David Walker Dr/Classique Ln
- David Walker Dr/US-441 S
- US-441 S/David Walker Dr
- Huffstetler Dr/David Walker Dr
- Huffstetler Dr/Dillard Rd
- Huffstetler Dr/Kurt St
- Kurt St/Clay Blvd
- W Lakeview Ave/Titcomb St
- W Lakeview Ave/Morin St
- S Bay St/E Doane Ave
- Paul Brown Pkwy/E Badger Ave
- S Grove St/E Key Ave
- S Grove St/E Lemon Ave
- S Grove St/E Orange Ave
- E Magnolia Ave/N Center St
- E McDonald Ave/N Hawley St
- E McDonald Ave/N Salem St
- N Prescott St/E Clifford Ave
- N Prescott St/E Hazzard Ave
- N Prescott St/N Exeter St
- Bates Ave/Reddick St
- Bates Ave/Gould St
- Palmetto Rd/Bates Ave
- Getford Rd/Selleen Dr
- Getford Rd/Louis Ct
- Wall St/Harlem Ave
- Wall St/Suanee Ave
- Wall St/Bates Ave
- E Orange Ave/Cardinal St
- E Orange Ave/Pine St
- N Center St/E Orange Ave
- W Ardice Ave/Oak Lynn St
- US-441 S/Dillard Rd
- US-441 S/David Walker Dr
- US-441 S/Mt Homer Rd
- US-441 S/Huffstetler Dr
- Huffstetler Dr/US-441 S
- US-441 S/Huffstetler Dr
- N St Clair Abrams/E Burleigh Blvd
- N St Clair Abrams Ave/Lake Frances Blvd
- N St Clair Abrams Ave/E Clifford St
- N St Clair Abrams Ave/E Caroline St
- N St Clair Abrams Ave/E Maud St
- W Main St/N Pulsifer Ave
- S Duncan Dr/Wells Ave
- S Duncan Ave/Palm Ave
- S Duncan Ave/Birch Blvd
- S Duncan Dr/Woodlea Rd
- Woodlea Rd/Captain Haynes Rd
- Dead River Rd/E Rosewood Ln
- Dead River Rd/Woodview Dr
- Dead River Rd/Fern Ave
- N Duncan Dr/W Maud St
- US-441/N Lakeshore Blvd
- US-441/Hilltop Rd
- W Burleigh Blvd/Hilltop Rd
- US-441 S/7th Sunfish St
- US-441 S/Lakes Blvd
- US-441 S/Radio Rd
- US-441/Blossom Ln
- US-441 S/Skinner Ave
- US-441/Crofton Dr
- US-441/Wilco Dr
- US-441/Tavares Ave
- FL-44/US-441
- US-441/Tomato Hill Rd
- US-441/Tomato Hill Rd
- US-441/Waterside Edge Dr
- US-441/Ice Cream Rd
- US-441/Nebraska Ave
- Newell Hill Rd/Bentley Rd
- Bentley Rd/Mills St
- Mills St/E Line St
- US-441 S/N East St
- US-441 S/Shore Acres Dr
- N 14th St/Sunshine Ave
- N 14th St/Center St
- N 14th St/High St
- N 14th St/W Main St
- S 14th St/Yellow Jacket Way
- S 14th St/W Dixie Ave
- S 14th St/Emerson St
- S 14th St/Gunston St
- S 14th St/Fairfax St
- S 14th St/Bryant St
- W Dixie Ave/Pasa Del Norte St
- W Dixie Ave/S 12th St
- W Dixie Ave/S 6th St
- E Dixie Ave/Dozier Cir
- E Dixie Ave/Rambo St
- S Lake St/Pine St
- S Lake St/E Magnolia St
- E Main St/S Palmetto St
- W Main St/12th St
- South St/Hood Ave
- South St/Hickory Dr
- South St/Florida Ave
- South St/S Lone Oak Dr
- South St/Coach N Four Dr
- South St/Royal Oak Blvd
- South St/Southwinds Cove Way
- CR-468/W Main St
- CR 468/Montclair Rd
- CR-468/Lisa Dare Dr
- Griffin Rd/Cabin St
- Griffin Rd/Pioneer Trail
- Griffin Rd/Thomas Ave
- Griffin Rd/Thomas Ave
- Griffin Rd/Thomas Ave
- Griffin Rd/Tuskegee St
- Griffin Rd/Red Raider Rd
- Pamela St/Griffin Rd
- Susan St/Birchwood Cir
- Hill St/Penn St
- Ardice Ave/Ruleme St
- US-441 S/Lake Park Ct
- US-441 S/Eudora Rd
- US-441 S/Eudora Rd
- US-441/Citrus Ct
- US-441/Morningside Dr
- US-441 S/E Crooked Lake Dr
- US-441 S/Gables Dr
- N Donnely St/Waterman Ave
- N Donnelly St/W Jackson Ave
- N Donnelly St/Jackson Ave
- Lincoln Ave/N Baker St
- Lincoln Ave/N Grandview St
- Lincoln Ave/N Highland St
- Lincoln Ave/N Wardell St
- Wardell St/Grant Ave
- Limit Ave/Orange St
- Donnelly St/11th Ave
- N Donnelly St/7th Ave
- E 5th Ave/N Baker St
- E 5th Ave/N Grandview St
- E 5th Ave/N Clayton St
- and 202 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 | 49.6 | first check |
| 2026-07-30 | 49.6 | no change |
| 2026-07-31 | 49.6 | no change |
| 2026-08-01 | 49.6 | 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
10 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 2294 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)
- Warning450 instances
450 of 452 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)
- Warning11 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)
- Warning6 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)
- Warning1 instance
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
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
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
feed_info.txt is missing its start/end dates
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Finding code: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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)
- 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 Not ready
Resolve this before you certify on the D-10. Service data expired 2294 days ago, so FTA would find the link out of date. agency.txt has no nonblank agency_id. Every RY2026 NTD GTFS submission needs a stable value unique among the reporters represented in the feed, crosswalked to each reporter's NTD ID on the P-50 form.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- Service data expired 2294 days ago, so FTA would find the link out of date.
- agency_id provided Not ready
- agency.txt has no nonblank agency_id. Every RY2026 NTD GTFS submission needs a stable value unique among the reporters represented in the feed, crosswalked to each reporter's NTD ID on the P-50 form.
- shapes.txt covers your trips Ready
- All 153 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed is close to the conformance mark. Service data expired 2294 days ago. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 2294 days ago.
- Accessible Not yet
- States wheelchair access on 0% of stops and 100% 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.
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.
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 76 / 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 52 / 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/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.