Feed status · checked 2026-08-01
Greater Peoria Mass Transit (CityLink)
Based on the feed this agency publishes
Service mode Bus
down 0.4 since 2026-07-31
Catalogued in Illinois.
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 76 minutes ago; last changed 15 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
884 of 884 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
4451 of 4451 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
- 884 of 884 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
- 4451 of 4451 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 35 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 8 kinds of issue across 321 instances (0 error, 166 warning, 155 informational).
Service data covers the next 35 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
10 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 3, 4, 7, 13, 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.
188 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Richwoods Apts/CWTC", "3200 Dries/CWTC", "Parkway/Dunham's", 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 884 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)
- 10 (pink)
- 11 (purple)
- 12 (red)
- 13 (yellow)
- 14 (green)
- 15 (purple)
- 17 (orange)
- 18 (orange)
- 2 (teal)
- 20 (gray)
- 23 (orange)
- 3 (yellow)
- 4 (pink)
- 5 (teal)
- 7 (yellow)
- 8 (brown)
- 99 (green)
| Route | Type | Line color |
|---|---|---|
| 1 University | Bus | teal |
| 10 Forrest Hill | Bus | pink |
| 11 Western | Bus | purple |
| 12 Heights | Bus | red |
| 13 South Adams | Bus | yellow |
| 14 Wisconsin | Bus | green |
| 15 Lincoln | Bus | purple |
| 17 Pekin North | Bus | orange |
| 18 Pekin South | Bus | orange |
| 2 North Adams | Bus | teal |
| 20 ICC Express | Bus | gray |
| 23 Peoria to Pekin | Bus | orange |
| 3 Northwest Peoria | Bus | yellow |
| 4 Sheridan | Bus | pink |
| 5 West Peoria | Bus | teal |
| 7 John Gwynn | Bus | yellow |
| 8 East Peoria | Bus | brown |
| 99 Special Airport and Cty Jail | Bus | green |
List every stop
- Sterling Towers
- Rochelle and Kiva
- Richwoods Apts/CWTC
- Richwood and Molleck
- Molleck and Dorchester
- Molleck and Baskin Ridge
- Lexington Hills Apts
- Forest Hill and Woodbine
- Forest Hill and Renwood
- Forest Hill and Gale
- Forest Hill and Easton
- 3200 Dries/CWTC
- Wal-Mart on University
- Parkway/Dunham's
- Hamilton and Monroe/US Courthouse
- Parkway/Payless
- Wal-Mart on Parkway Drive
- 3200 Dries/Landmark
- Koch and 4th
- Woodrow Wilson Primary School
- Forest Hill and El Vista
- Forest Hill @ Store
- Forrest Hill and Victoria Ave.
- Sterling Bazaar/IL Secretary of State
- Molleck & Woodhill
- Molleck and Dorchester
- Molleck and Richwoods
- Rochelle and Richwoods/Sharon Willows
- Rochelle and Reservoir
- 2400 Reservoir/Proctor Place
- Reservoir and Rockwood
- Koch and Southmoor
- 279 Koch St. @KMI
- 5th and Derby
- Wal-Mart on Allen
- MLK and Ligonier
- Western and Ann
- Western and Millman
- Western and Martin
- Western and Callender
- Western and Moss
- Blaine and Smith
- Smith and Warren
- Steubenville and Smith
- Steubenville and Hurlburt
- Hurlburt and Charlton
- Hurlburt and McArthur
- John Gwynn and MacArthur
- Parkway and Stadium Dr.
- John Gwynn and Richard Pryor
- Crittenton Center
- Gwynn and Hightower/Red Cross
- Gwynn and Kumpf
- Gwynn and Hightower/Red Cross
- Crittenton Center
- John Gwynn and Richard Pryor
- John Gwynn and MacArthur
- Hurlburt and MacArthur
- Hurlburt and Charlton
- Hurlburt and Steubenville
- Steubenville and Johnson
- Martin and Steubenville
- Martin and Dusable
- Martin and Warren
- Martin and Blaine
- Martin and Western
- Western and Moss
- Western and Sherman
- Western and Callender
- Parkway @ Pizza Hut
- Western and Rohman
- Western and Martin
- Western and Millman
- Western and Ann
- MLK and Ligonier
- University @ Richwoods Apts
- University and Kingsway/Pioneer Sq Shopp
- Court and Olt Ave.
- University and Jeth/Jeth Court Apts
- 7300 N University
- University and Northmoor/Richwoods HS
- University and Miramar
- University and Daytona
- University and Willow Wood
- University and Arbor Loop/ICC North
- EP!C/Peoria Production
- Sterling and Scenic/Walgreens
- Glen and Renwood
- Glen and Glen Court
- Glen and Dawn/Concordia school
- Glen Willows Apts
- Glen and University
- Metro Centre/Schnucks
- Glen and Fairview
- Glen and Sheridan
- Glen and Edgebrook Walgreens
- Glen and Idlewood
- Glen and Knoxville
- Glen and Knoxville
- Glen and Longview/Peoria Heights Middle
- Glen and Glen Elm
- Glen and Bellevue/Peoria Heights Public
- Glen and Clarendon
- Glen and Prospect
- Prospect and Seiberling
- Prospect and Marietta
- Prospect and Lake
- Prospect and Divison
- Prospect and Hazard
- Prospect and London
- Prospect and Tripp
- Prospect and Richwoods
- Prospect and Elmhurst
- Prospect and Maywood
- Prospect & Wilcox
- Prospect and Gift
- Prospect and McClure
- Prospect and Arcadia/Peoria Zoo/Glen Oak
- Prospect and Frye
- Abington and Monroe
- Jefferson and St Giles
- Jefferson and Cornhill
- Jefferson and Caroline
- Jefferson and Spring
- Jefferson and Morton
- Jefferson and Morgan
- Jefferson and Green
- Jefferson and Bryan
- Jefferson and Hamilton
- Abington and Monroe
- Adams and Fulton
- Abington and Prospect
- Adams and Hamilton
- Prospect and Arcadia/Peoria Zoo/Glen Oak
- Prospect and Gift
- Adams and Green
- Prospect and Wilcox
- Adams and Wayne
- Prospect and Maywood
- Adams and Evans
- Prospect and Forest Hill
- Adams and Spring
- Prospect and Richwoods
- Adams and Caroline
- Prospect and Wilson
- Adams and Cornhill
- Prospect & Paris
- Prospect and Northcrest
- Prospect and Harzard
- Prospect and Lake
- Prospect and Marietta
- Prospect and Seiberling
- Glen and Prospect
- Glen and Bellevue
- Glen and Glen Elm
- Glen and Longview/Peoria Heights Middle
- Glen and Roberts
- Glen and Knoxville
- Glen and Knoxville
- Glen and Endres
- Glen and Sheridan
- Glen & Everts
- Glen and Isabell
- Glen and Sherwood
- Glen and University
- Glen and Melody
- Glen and Glen Park
- Glen and Dawn
- Glen and Woodview
- Glen and Ronald
- Glen and Renwood
- Sterling and Eugenia
- 8900 N University/Tac Shack
- Laramie and Malone/SouthSide Mission
- Laramie and Latrobe
- Laramie and Freemont
- Laramie and Grinnell
- Laramie and Krause
- Laramie and Farrow
- Laramie and Trewyn
- Montana and Idaho
- Montana and Oregon
- Oregon and Trewynn
- Oregon and Meidroth
- Oregon and Krause
- Metec
- Adams and Lydia
- Adams and Easton
- Adams and Edmund
- Adams and Lincoln
- Adams and Pecan
- Adams and Persimmon
- Adams and Elm
- Jefferson and Elm/IL Dept of Employment
- Jefferson and Richard Pryor/Persimmon
- Jefferson and River West
- Jefferson and MacArthrur
- Jefferson and Linden
- Jefferson and George
- Jefferson and Olive
- Jefferson and Cass
- Jefferson and Brown
- Adams and Easton
- Adams and Lydia
- Adams and Krause
- Adams and Stanley
- Griswold and Montana
- Laramie and Grinnell
- Laramie and Fremont
- Laramie and Latrobe
- University and St James
- Laramie and Starr
- Moss and Moss Terrace
- University and Gale/Parkview Cemetery
- Moss and Union Hill
- University and Nebraksa
- MLK and Shipman
- University and Colombia Terrace
- Adams and Olive
- 8600 N University/Clubs at River City
- 4500 Brandywine
- 4400 Brandywine/UHaul
- 4200 Brandywine/Econo Lodge
- Seven Oaks/Brandywine Crossing
- Lake and Lakecrest
- Lake and Hollyridge
- Lake and Knoxville
- Lake and Gate Ridge
- Lake and Boulvard
- Lake and Monroe
- Monroe and Cox
- Monroe and War Memorial
- War Memorial and Boulevard
- California and War Memorial
- California and Embert
- California and Pasadena
- Forest Hill and California
- Forest Hill and Indiana
- Wisconsin and Forest Hill
- Wisconsin and Corrington
- Wisconsin and Seneca
- Wisconsin and Gift
- Wisconsin and McClure
- Wisconsin and Archer/Kroger
- Wisconsin and Thrush
- Wisconsin and Frye
- Wisconsin and Nebraska
- Wisconsin and Ravine
- Wisconsin and Belaire
- Wisconsin and Glen Oak
- and 634 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — down 0.4 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 55.9 | first check |
| 2026-07-30 | 53.8 | down 2.1 |
| 2026-07-31 | 53.4 | down 0.4 |
| 2026-08-01 | 53.0 | down 0.4 |
What changed since your last check
- Correctness no change
- Freshness down 1.7
- Rider experience no change
What changed in this feed
Overall score fell 0.4 points 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
12 findings, ordered by severity.
Show every finding
- Warning4451 instances
4451 of 4451 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)
- Warning884 instances
884 of 884 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)
- Warning118 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)
- Warning18 instances
Same name and description for route (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_name_and_description_for_route' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: same_name_and_description_for_route · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning17 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning9 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)
- Warning2 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)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · 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)
- Info155 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Finding code: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 35 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 4451 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 35 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 9 of 884 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 35 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 61 / 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 58 / 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/greater-peoria-mass-transit-citylink-2208/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.