Feed status · checked 2026-08-01
Ryde Racine
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Wisconsin.
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 70 minutes ago; last changed 41 days ago.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 1492 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category
Add the required column named in the finding to the flagged file.Likely your export tool
A file is missing a column that GTFS requires. Apps may reject the whole file, so riders could lose the affected routes or stops.
⏱ Often an export setting; ask your vendor if it recurs.worth about +12 points in its category
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
730 of 730 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
Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- Service data ended 1492 day(s) ago.
- Next action
- Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- A file is missing a column that GTFS requires.
- Next action
- Add the required column named in the finding to the flagged file.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- 730 of 730 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
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Add the required column named in the finding to the flagged file. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date was 1492 days ago.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send Trillium a fix request
This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. Each fix names the validator notice and a guide link.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 10 kinds of issue across 61 instances (2 error, 16 warning, 43 informational).
Service data ended 1492 day(s) ago. Trip planners have likely already dropped this feed.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Route 4).
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.
103 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Drexel Avenue and Winthrop Ave", "Drexel Avenue and Winthrop Ave", "Hwy 32 and Durand Avenue", 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 730 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.
- Route 1 (red)
- Route 2 (brown)
- Route 3 (yellow)
- Route 4 (teal)
- Route 5 (pink)
- Route 7 (purple)
- Route 86 (orange)
- Route 20 (blue)
- Route 27 (green)
| Route | Type | Line color |
|---|---|---|
| Route 1 | Bus | red |
| Route 2 | Bus | brown |
| Route 3 | Bus | yellow |
| Route 4 | Bus | teal |
| Route 5 | Bus | pink |
| Route 7 | Bus | purple |
| Route 86 | Bus | orange |
| Route 20 | Bus | blue |
| Route 27 | Bus | green |
List every stop
- RCOC
- Knoll Place and Chicory Road
- Memorial Drive and Chicory Road
- Knoll Place and Chicory Road
- Knoll Place and Concord Drive
- Sheridan Road and Derby Avenue
- Knoll Place and Concord Drive
- Sheridan Road and Lakewood Avenue
- Knoll Place and Kenwood Drive
- Knoll Place and Kenwood Drive
- Taylor Avenue and Southwood Drive
- Olsen Industrial Park
- Taylor Avenue
- Sheridan Road and Richard Avenue
- Southwood Drive and Biscayne Avenue
- Knoll Place and Fleetwood Drive
- Knoll Place and Fleetwood Drive
- Taylor Avenue and Monarch Drive
- Sheridan Road and Enos Avenue
- Meachem Road and Taylor Avenue
- Southwood Drive and Admiralty Avenue
- Knoll Place and Rosalind Avenue
- Knoll Place and Rosalind Avenue
- Sheridan Road and Rosalind Avenue
- Emstan Hills Road and Southwood Drive
- Emstan Hills Road and Oakwood Drive
- Emstan Hills Road and Meachem Road
- Drexel Avenue and Maryland Avenue
- Sheridan Road and Maryland Avenue
- Meachem Road and Emstan Hills Road
- Drexel Avenue and Maryland Avenue
- Drexel Avenue and Delaware Avenue
- Drexel Avenue and Delaware Avenue
- Meachem Road and Maryland Avenue
- Sheridan Road and Larson Street
- Meachem Road and Maryland Avenue
- StH 32 and Larsen Street
- Meachem Road
- Meachem Road
- Drexel Avenue and Winthrop Ave
- Drexel Avenue and Winthrop Ave
- Durand Avenue WalMart
- Drexel Avenue and Durand Avenue
- Wood Road and Durand Avenue
- Drexel Avenue and Durand Avenue
- Durand Avenue and Meachem Road
- Durand Avenue and Oregon Street
- Durand Avenue and Kentucky Street
- Durand Avenue and Lathrop Avenue
- Durand Avenue and Cleveland Avenue
- Durand Avenue and Wheelock Drive
- Durand Avenue and West Boulevard
- Durand Avenue and Pritchard Drive
- Durand Avenue and Taylor Avenue
- Durand Avenue and Pritchard Drive
- Durand Avenue and Drexel Avenue
- Durand Avenue and Southwood Drive
- Durand Avenue and Hamlin Street
- Durand Avenue and Illinois farside
- Durand Avenue and Indiana Street
- Durand Avenue and Hickory Grove Avenue
- Durand Avenue and Orchard Street
- Durand Avenue and Phillips Avenue
- Durand Avenue and Hayes Avenue
- Durand Avenue and Packard Avenue
- Durand Avenue and Cleveland Avenue
- Durand Avenue and Lathrop Avenue
- Durand Avenue and Ohio Street
- Durand Avenue and West Boulevard
- Durand Avenue and Drexel Avenue
- Durand Avenue and Hamlin
- Durand Avenue and Wood Road
- Durand Avenue and Madison Street
- Durand Avenue and Wellington Drive
- Highway 32 and Durand
- Durand Avenue and Hamilton Avenue
- Durand Avenue and Roosevelt Avenue
- Durand Avenue and Wood nearside midblock
- Durand Avenue and Elwood Drive
- Durand Avenue and Regency Mall
- Durand Avenue and StH 31
- Durand Avenue and Green Bay nearside
- Durand Avenue and Storybook
- Lathrop Avenue and Durand Avenue
- Durand Avenue and Cozy Acres Road
- Durand Avenue and Storybook farside
- Durand Avenue and Cozy Acres Road
- Regency Mall
- Hwy 32 and Durand Avenue
- Drexel Avenue and Gillen Street
- Taylor Avenue and Gillen Street
- Taylor Avenue & Gillen Street
- Gillen Street and Drexel Avenue
- Target @ Front Entrance
- Target Store @ Service Road
- 2616 Lathrop Avenue
- Racine Street and 24th Street
- Roosevelt Avenue and Cinema VI
- Racine Street and 24th Street
- Taylor Avenue and Gilson Street
- Taylor Avenue and Gilson Street
- Regency Point D
- Lathrop Avenue south of Olive Street
- Taylor Avenue and Olive Street
- Racine Street and 22nd Street
- Racine Street and 22nd Street
- Taylor Avenue and Olive Street
- High Ridge Shopping Center
- Loni Lane
- Regency Point
- Roosevelt Avenue and 21st Street
- Racine Street and 21st Street
- 21st Street and Illinois Street
- 21st Street and Ohio Street
- 21st Street and Indiana Street
- 21st Street and Orchard Street
- 21st Street and Lathrop Avenue
- 21st Street and Cleveland Avenue
- 21st Street and Blaine Avenue
- 21st Street and West Boulevard
- 21st Street and Quincy Avenue
- 21st Street and Roosevelt Avenue
- 21st Street and Ashland Avenue
- 21st Street and Taylor Avenue
- 21st Street and Case Avenue
- 21st Street and Indiana Street
- 21st Street and Illinois Street
- 21st Street and Kearney Avenue
- 21st Street and Kentucky Street
- 21st Street and Ohio Street
- 21st Street and Cleveland Avenue
- 21st Street and Lathrop Avenue
- 21st Street and Blaine Avenue
- 21st Street and Quincy Avenue
- 21st Street and West Boulevard
- 21st Street and Racine Street
- Ohio Street and 21st Street
- 21st Street and Taylor Avenue
- 21st Street and Franklin Street
- 21st Street and Ashland Avenue
- 21st Street and Jerome Boulevard
- 21st Street and Case Avenue
- 21st Street and Phillips Avenue
- 21st Street and Howe Street
- 21st Street and Grand Avenue
- Phillips Avenue and 21st Street
- Racine Street and 21st Street
- Grand Avenue and 21st Street
- Lathrop Avenue and 21st Street
- Regency and Speedway and TJ Max
- 21st Street
- Taylor Avenue and 20th Street
- Taylor Avenue and Jerome Boulevard
- Phillips Avenue and 20th Street
- Racine Street and 20th Street
- Grand Avenue and 20th Street
- Phillips Avenue and 20th Street
- Racine Street and 20th Street
- Grand Avenue and 20th Street
- Lathrop Avenue and 20th Street
- Ohio Street and Republic Avenue
- Waxdale
- Taylor Avenue and Meachem Street
- Taylor Avenue and Nineteenth Street
- Phillips Avenue and DeKoven Avenue
- Lathrop Avenue & Nineteenth Street
- Racine Street and DeKoven Avenue
- Phillips Avenue and DeKoven Avenue
- Grand Avenue and DeKoven Avenue
- DeKoven Avenue and S Memorial Drive
- DeKoven Avenue and Holborn Street
- DeKoven Street and Mead Street
- DeKoven Avenue and Franklin Street
- DeKoven Avenue and Grand Avenue
- DeKoven Avenue and Wisconsin Avenue
- DeKoven Avenue and Park Avenue
- DeKoven Avenue and S Memorial Drive
- DeKoven Avenue and Holborn Street
- DeKoven Avenue and Racine Street
- DeKoven Avenue and Franklin Street
- DeKoven Avenue and Grand Avenue
- DeKoven Avenue and Park Avenue
- Racine Street and DeKoven Avenue
- Grand Avenue and DeKoven Avenue
- Wisconsin Avenue and DeKoven Avenue
- IMET Gandeway on Renaissance
- Lathrop Avenue and Republic Avenue
- Grand Avenue and 18th Street
- Ohio Street and Byrd Avenue
- Taylor Avenue and 18th Street
- Taylor Avenue and 18th Street
- Grand Avenue and 18th Street
- Ohio Street and Byrd Avenue
- Workforce Development
- Racine Street and 18th Street
- Racine Street and 18th Street
- Byrd Avenue and Sycamore Avenue
- Byrd Avenue & Ohio Street
- Byrd Avenue and Oakdale Avenue
- Byrd Avenue and Perry Avenue
- Byrd Avenue and Skyline Drive
- StH 31 and Byrd Avenue
- Lathrop Avenue and 17th Street
- Taylor Avenue and 17th Street
- Taylor Avenue and 17th Street
- Wisconsin Avenue and 17th Street
- Grand Avenue and 17th Street
- Grand Avenue and 17th Street
- Wisconsin Avenue and 17th Street
- Ohio Street and 16th Street
- 16th Street and Ostergaard Avenue
- 16th Street and Ostergaard Avenue
- 16th Street and Oakdale Avenue
- Lathrop Avenue and 16th Street
- 16th Street and Oakdale Avenue
- 16th Street and StH 31
- Taylor Avenue and 16th Street
- 16th Street and Ohio Street
- 16th Street & Racine Street
- 16th Street and Illinois Street
- 16th Street and Orchard Street
- 16th Street and Perry Avenue
- 16th Street & Lathrop Avenue
- 16th Street and Cleveland Avenue
- 16th Street and Illinois Street
- 16th Street and Blaine Avenue
- Wisconsin Avenue and 16th Street
- 16th Street and Indiana Street
- 16th Street and West Boulevard
- Grand Avenue and 16th Street
- 16th Street and Orchard Street
- 16th Street and Quincy Avenue
- 16th Street and Ohio Street
- 16th Street and Grange Avenue
- 16th Street & Lathrop Avenue
- 16th Street and Holmes Avenue
- 16th Street and Morton Avenue
- 16th Street and Cleveland Avenue
- 16th Street and Phillips Avenue
- 16th Street and S Memorial Drive
- 16th Street and Blaine Avenue
- 16th Street and West Boulevard
- 16th Street and Quincy Avenue
- 16th Street and Grange Avenue
- 16th Street and Holmes Avenue
- 16th Street and Perry Avenue
- 16th Street and Junction Avenue
- 16th Street and Taylor Avenue
- 16th Street & Racine Street
- Waxdale Main Gande
- and 480 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 | 45.3 | first check |
| 2026-07-30 | 45.3 | no change |
| 2026-07-31 | 45.3 | no change |
| 2026-08-01 | 45.3 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-31.
Same feed file as 2026-07-31; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
15 findings, ordered by severity.
Show every finding
- Error2 instances
A file is missing a column that GTFS requires.
Apps may reject the whole file, so riders could lose the affected routes or stops.
Fix: Add the required column named in the finding to the flagged file. (Often an export setting; ask your vendor if it recurs.)
Finding code: missing_required_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Service data ended 1492 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning730 instances
730 of 730 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)
- Warning550 instances
550 of 550 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)
- Warning322 instances
322 of 550 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)
- Warning11 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)
- Warning3 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed describes flexible (demand-responsive) service but has no booking_rules.txt.
Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.
Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)
Finding code: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info29 instances
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info9 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
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)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
Flex zones are published but no booking_rules.txt is present.
Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. 1 validator error to resolve. Service data expired 1492 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 1 validator error to resolve.
- Current Not ready
- Service data expired 1492 days ago, so FTA would find the link out of date.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
- agency_id equals your NTD ID (optional) Not checked yet
- This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
- shapes.txt covers your trips Ready
- All 550 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. 1 validator error to resolve. Service data expired 1492 days ago. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Not yet
- Service data expired 1492 days ago.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 11 of 730 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks. The feed also carries 2 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
- Correctness 67 / 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 51 / 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/ryde-racine/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.