Feed status · checked 2026-08-01
Waukesha Metro Transit
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 3 hours ago; last changed 41 days ago.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
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 426 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
459 of 459 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
795 of 795 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
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 426 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
- 459 of 459 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
- 795 of 795 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
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.
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.
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. 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 426 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 8 kinds of issue across 66 instances (0 error, 21 warning, 45 informational).
Service data ended 426 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.
3 accessibility depth signals
3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (7/8, 15, 6).
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.
115 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("East Broadway & Oakland Avenue, Waukesha, WI, USA", "Bluemound/Moorland Rd", "Bluemound/Elm Grove Rd", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
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 459 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.
- 2/3 (green)
- 8 (orange)
- 15 (pink)
- 6 (pink)
- 3 (green)
- 1 (yellow)
- 2 (teal)
- 9 (purple)
- 4 (teal)
- 7/8 (orange)
- 5 (teal)
- 7 (blue)
| Route | Type | Line color |
|---|---|---|
| 2/3 | Bus | green |
| 8 | Bus | orange |
| 15 | Bus | pink |
| 6 | Bus | pink |
| 3 | Bus | green |
| 1 | Bus | yellow |
| 2 | Bus | teal |
| 9 | Bus | purple |
| 4 | Bus | teal |
| 7/8 | Bus | orange |
| 5 | Bus | teal |
| 7 | Bus | blue |
List every stop
- Delafield at Magnolia
- White Rock at Niagara
- 92nd at 800 N
- Sunset at Shoppes at Fox River
- East Broadway & Oakland Avenue, Waukesha, WI, USA
- Bluemound/Moorland Rd
- Bluemound/Elm Grove Rd
- Transit Center Bay F
- North St at Emily St
- Sunset at Sentry
- Sunset at CVS
- Transit Center Bay G
- Bluemound & Eastmoor
- Bluemound & Sunny Slope
- Bluemound & 16095
- Bluemound & 15901
- Bluemound & Moorland
- Bluemound & Westmoor
- Bluemound & Elmridge
- Bluemound & Bishops Way
- Bluemound & Elm Grove
- Bluemound & 12821
- Bluemound & Underwood
- Bluemound & N121
- Bluemound & N116
- Bluemound & N112
- Bluemound & Mayfair
- Bluemound & N104
- Bluemound & Milwaukee County Zoo
- N95 & N550
- N95 & Wisconsin
- 92nd & 800 N.
- Watertown Plank & N92
- Watertown Plank & 8900 BLK
- Watertown Plank & N87
- N87 & Connell
- N87 & Coffey
- Doyne & Coffey
- Coffey/Froedtert ER Entrance
- 87th St/Connell
- N87th/1100 N.
- Watertown Plank & 8948
- 92nd/1000 N.
- N92 & Wisconsin
- N92 & Wisconsin
- N95 & Wisconsin
- N95 & Bluemound
- Main St at Paramount Dr
- Main St at Planet Fitness
- Main at Manhattan
- Bluemound/97th St
- Bluemound/10000 W.
- Bluemound/104th St
- Bluemound/Mayfair Rd
- Bluemound/112st
- Bluemound/116th St
- Bluemound/121th St
- Bluemound/Underwood PKWY
- Bluemound/124th St
- Bluemound/12822 W.
- Bluemound/Bishops Way
- Bluemound/Sunny Slope Rd
- Bluemound/Vernon Pl
- Bluemound/Crystal Ln
- Bluemound/Terrace Dr
- Bluemound/124th St
- Stardust at Westbrook
- White Rock Ave @ Baxter St
- St Paul at Moreland
- St Paul at Moreland
- Sunset at Oakdale
- Nw Barstow Street at Bank Street
- W Main Street at N East Avenue
- E Main Street at Pleasant Avenue
- E Main Street at N Hartwell Avenue
- E Main Street at Aurora Street
- E Main Street at Genesee Street
- Main And Perkins
- 20900 Swenson Drive
- Swenson Drive at Crossroads Circle (East)
- Swenson Dr. @ Crossroads Circle (West)
- E. Main St. & Perkins Ave.
- E Main Street at Adams Street
- E Main Street at Aurora Ave
- E Main Street at N Hartwell Avenue
- E Main Street at White Rock Ave.
- E Main Street at N East Avenue
- E Main Street at N Barstow Street
- Nw Barstow Street at Bank Street
- Transit Center Bay L
- Manhattan Drive at E Moreland Boulevard
- Manhattan Drive at Greenway Terrace
- Butler Drive at Jennifer Lane
- 1701 Stardust Drive
- Stardust Drive at Rustic Way
- Stardust Drive at Sunnyside Drive
- Springdale Road at Rambling Rose Road
- Heritage Lane at Springdale Road
- Abbott Drive at Parklawn Drive
- Abbott Drive at Kossow Road
- Swenson Drive at Taco Bell
- Swenson Drive at Crossroads Circle
- Goerkes Corners Public Transit Station
- The Corners of Brookfield
- Aldi's-Brookfield
- Bluemound Road at Regency Court
- Bluemound Rd at Brookfield Rd.
- Bluemound Rd. at McDonald's
- Bluemound at Fiserv Dr.
- Bluemound Road at Corporate Drive
- Portillo's
- Bluemound at Calhoun
- The Plaza
- 16655 Bluemound Road (Squires Ii)
- Bluemound Road at Executive Drive
- Executive Dr at BMO Harris
- Brookfield Square
- E Moreland Boulevard at Jefferson Avenue
- E Moreland Boulevard at Waukesha Avenue
- Kohl's Department Store
- Westbrook Shopping Center
- Woodman's
- 1817 E Main Street
- E Main Street at Davidson Road
- Target Department Store
- Brookfield Square Drive at Executive
- 180 Exective Drive Brookfield
- Executive Drive at Bluemound
- Bluemound at Ruf Rd.
- Bluemound at Thomas Lane
- Brookfield Fashion Center
- Bluemound Road at Calhoun Rd.
- Brownstones Shopping Center
- Bluemound at Woelfel Rd.
- Bluemound Rd at Harvard Square
- Bluemound Rd. at Hobby Lobby
- Bluemound Road at Woodland Health Center
- W. Bluemound Rd. at Galleria Plaza
- Eble Park
- 19700 Bluemound Road
- Abbott Drive at Kossow Road
- Springdale Road at Rambling Rose Road
- Springdale Road at Hollidale Drive
- Stardust Drive at Rustic Way
- Stardust Drive at Wolf Road
- Butler Drive at Jennifer Lane
- Manhattan Drive at Greenway Terrace
- Manhattan Drive at E Moreland Boulevard
- E Moreland Boulevard at Highland Avenue
- E Moreland Boulevard at Jefferson Avenue
- White Rock Avenue at Elm Street
- E Main Street at Davidson Road
- 1810 E Main Street
- Dolphin Drive at Dolphin Court
- Arcadian Avenue at Pleasant Street
- Arcadian Avenue at N Hartwell Avenue
- Arcadian Avenue at Pleasant Street
- Transit Center Bay K
- Arcadian Avenue at Colton Street
- Arcadian Avenue at Aurora Street
- Arcadian Avenue at N Greenfield Avenue
- Arcadian Avenue at Perkins Avenue
- Arcadian Avenue at Blackstone Avenue
- Opp. 1604 Arcadian Avenue
- Aldi's-Waukesha (East)
- Nike Drive at Dolphin Drive
- Goodwill at Nike Drive
- Springdale Road at Bluemound Road
- Bluemound Road at Parklawn Road
- Bluemound Road at Kossow Road
- Menards at Kossow Road
- Bluemound Road at Parklawn Drive
- Springdale Road at Bluemound Road
- Ruben Drive at Springdale Road
- Arcadian Avenue at Anitol Ave.
- 1604 Arcadian Avenue
- Arcadian Avenue at Blackstone Avenue
- Arcadian Avenue at Perkins Avenue
- Arcadian Avenue at N Greenfield Avenue
- Arcadian Avenue at Aurora Street
- Arcadian Avenue at Colton Street
- Big Bend at Sunset
- Big Bend Road (Midblock)
- Big Bend Road at Garfield Avenue
- Big Bend Road at E Rivera Drive
- Big Bend Road at Cliff Alex Ct.
- S East Avenue at Garfield Avenue
- S East Avenue at E Sunset Avenue
- Opp 1320 S East Avenue
- Whittier Elementary School
- S East Avenue at E Roberta Avenue
- E Roberta Avenue at Westminster Drive
- South High School
- Roberta Avenue at Tenny
- U.S. Post Office
- E Broadway at N East Avenue
- N East Avenue at South Street
- Transit Center Bay A
- N Barstow Street at W Main Street
- N Barstow Street at South Street
- Wisconsin Avenue at N East Avenue
- E Broadway at Barney Street
- E Broadway at N Hartwell Avenue
- Tenny Avenue at E Roberta Avenue
- Tenny Avenue at Wedgewood Drive
- Tenny Avenue at Larchmont Drive
- Super Wal-Mart
- S West Avenue at Dodie Drive
- S West Avenue at Debbie Street
- S West Avenue at Richard Street
- S West Avenue at Freeman Street
- S West Avenue at W Sunset Avenue
- W Sunset Avenue (Mid-Block)
- S Grand Avenue at W Sunset Avenue
- S Grand Avenue at Ellsworth Place
- S Grand Avenue at Hoover Avenue
- S Grand Avenue at W Roberta Avenue
- S Grand Avenue at Estberg Avenue
- S Grand Avenue at Frame Avenue
- S Grand Avenue at Wilson Avenue
- S Grand Avenue at W Laflin Avenue
- S Grand Avenue at W College Avenue
- N East Avenue at Wright Street
- N East Avenue at Cook Street
- N East Avenue at E Broadway
- Transit Center Bay B
- N East Avenue at Cook Street
- N East Avenue at W College Avenue
- S Grand Avenue at Laflin Avenue
- S Grand Avenue at Wilson Avenue
- S Grand Avenue at Frame Avenue
- S Grand Avenue at Estberg Avenue
- S Grand Avenue at W Roberta Avenue
- S Grand Avenue at Hoover Avenue
- S Grand Avenue at Ellsworth Place
- S Grand Avenue at W Sunset Avenue
- S Grand Avenue at Baird Street
- S Grand Avenue at Debbie Street
- S Grand Avenue at Dodie Drive
- S Grand Avenue at Sentinel Drive
- Sentinel Drive at Madera Street
- Central Middle School
- Shoppes at Fox River
- Food Pantry
- S Prairie Avenue at Prairie Home Drive
- S Prairie Avenue at Luke Avenue
- 301 S Prairie Avenue
- W College Avenue at Franklin Avenue
- N West Avenue at W College Avenue
- N West Avenue at Dunbar Avenue
- and 209 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 | 51.6 | first check |
| 2026-07-30 | 51.6 | no change |
| 2026-07-31 | 51.6 | no change |
| 2026-08-01 | 51.6 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
14 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 426 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)
- Warning795 instances
795 of 795 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)
- Warning459 instances
459 of 459 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)
- Warning67 instances
67 of 795 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)
- Warning13 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)
- Warning3 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
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)
- Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info34 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)
- Info8 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)
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. Service data expired 426 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- Service data expired 426 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 795 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 426 days ago. 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 Not yet
- Service data expired 426 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.
- 13 of 458 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.
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 59 / 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/waukesha-metro-transit/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.