Feed status · checked 2026-08-01
City of Madera
Based on the feed this agency publishes
Service mode Bus
down 0.4 since 2026-07-31
Catalogued in California.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.
Checked for changes 1 hours ago; last changed 38 days ago.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
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 0 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
Review the rule documentation for 'invalid_phone_number' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid phone number (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.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
114 of 114 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 0 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
- Invalid phone number (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'invalid_phone_number' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
- 114 of 114 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. See this feed's finding-clearance log.
Review the rule documentation for 'invalid_phone_number' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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. See this feed's finding-clearance log.
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. See this feed's finding-clearance log.
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 today.
- 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 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 7 kinds of issue across 59 instances (1 error, 14 warning, 44 informational).
Service data ended 0 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.
1 accessibility depth signal
3 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Tozer Street and Sunrise Avenue DSS/DPH Complex", "4th Street and J Street - St Joachim's Catholic Church", "4th Street and I Street - St. Joachim's Elementary School").
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 114 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 (purple)
- Route 2 (red)
- Route 3 (green)
- Route 4 (teal)
| Route | Type | Line color |
|---|---|---|
| Route 1 Purple Line | Bus | purple |
| Route 2 Orange Line | Bus | red |
| Route 3 Green Line | Bus | green |
| Route 4 Blue Line | Bus | teal |
List every stop
- Madera Community College Center
- Intermodal Center Bus Station
- Stadium Road and Gary Lane (Alpha Elementary School)
- Granada Drive and Sandlewood Drive
- Cleveland Avenue and Schnoor Street
- Yosemite Avenue and Flume Street
- Madera Community Hospital
- Walgreens at Cleveland Avenue
- Sherwood Street and Country Club Drive - Camarena Urgent Care (Eastbound)
- Lake Street and Kennedy Street - Madera Garden Apartments (Southbound)
- Sherwood Street and Country Club Drive - Big Lots (Westbound)
- 9th Street and South C Street
- Yosemite Avenue and Flume Street
- Yosemite Avenue and O Street (Natural Vision)
- 9th Street and South D Street
- Road 28 and Lada Avenue (Cottonwood Creek Apartments)
- Granada Drive and Sandlewood Drive (Northbound)
- Adell Street at Las Brisas Apartments
- Yosemite Avenue and Elm Street - McDonald's
- South D Street and 7th Street (Frank Bergon Center)
- Yosemite Avenue and L Street
- Sonora Street and Adell Street (Eastbound)
- Sonora Street and Adell Street (Westbound)
- Yosemite Avenue and Fig Street
- Yosemite Avenue and A Street
- Sherwood Street and Philip Street
- Cleveland Avenue and Kadota Avenue
- Cleveland Avenue and Schnoor Street (Taco Bell)
- Cleveland Avenue and Malta Avenue - Madera Apartments
- Almond Avenue at Madera Early Childhood Education
- Avenue 13 and Concord Court
- Avenue 13 and Raymond Thomas Street (Eastbound)
- Yosemite Avenue and G Street - Courthouse Park
- Yosemite Avenue and G Street
- Yosemite Avenue and North K Street
- Sunrise Avenue and Lake Street
- Yosemite Avenue and Mace Street
- Stadium Road at Madison Elementary School (Southbound)
- Granada Drive and Pinewood Drive
- Granada Drive and Riverview Drive
- Howard Road and Amerine Avenue (U-Save)
- Avenue 13 and Raymond Thomas Street (Westbound)
- Olive Avenue and South N Street
- Stadium Road and Almond Avenue (Northbound)
- Almond Avenue and Emily Way
- Almond Avenue and Emily Way
- Stadium Road at Madison Elementary School (Northbound)
- Lake Street and Cleveland Avenue (Northbound)
- Lake Street and Cleveland Avenue (Soutbound)
- Cleveland Avenue and Malta Avenue - Madera Apartments
- Almond Avenue and Madera Avenue
- Yosemite Avenue and Fig Street at Yosemite Christian Church
- Stadium Road and Almond Avenue (Southbound)
- South M Street and Yosemite Avenue
- Pan-American Community Center (Southbound)
- Almond Avenue and Barnett Way
- Stadium Road and Avenue 13 - Madera High South
- Howard Road and Amerine Avenue (Zak's Security)
- Lake Street and Kennedy Street (Northbound)
- Stadium Road and Avenue 13 (Northbound)
- Tozer Street and Sunrise Avenue DSS/DPH Complex
- Cleveland Avenue and Sharon Avenue
- Cleveland Avenue and Columbia Street
- Cleveland Avenue and Austin Avenue
- Cleveland Avenue and Lake Street - Valero Gas Station
- Cleveland Avenue and Tulare Street
- Yosemite Avenue and A Street - Camarena Health
- Sunrise Avenue and Lake Street
- Roosevelt Avenue and Lake Street - McNally Park
- Roosevelt Avenue and A Street - Sierra Vista Elementary School
- Olive Avenue and Knox Street
- Madera County Department of Corrections
- Olive Avenue and Knox Street
- Roosevelt Avenue and A Street
- Roosevelt Avenue and Lake Street
- D Street and 7th Street - Camarena Health
- Cleveland Avenue and Lake Street - La Esperanza Food Center
- Cleveland Avenue and Austin Avenue
- Cleveland Avenue and Sonora Street
- Cleveland Avenue and Sharon Avenue - County Club Village
- Howard Road and Shannon Avenue - Lion's Town and County Park Avenue Inbound
- Howard Road and Fairview Avenue - Save Mart Supermarket
- Yosemite Avenue and O Street
- Almond Avenue and SR 99
- Tozer and Lada Avenue
- Clinton Street and Tozer Street
- Tozer Street and Clinton Street
- Tozer Street and Sunrise Avenue - Madera Tech
- Almond Avenue and SR 99
- Howard Road and Fairview Avenue
- Howard Road and Shannon Avenue - Lion's Town and County Park
- Cleveland Avenue and Schnoor Street - Valley Fitness
- Sunset Avenue and Accornero Street
- Sunset Avenue and Pine Street - Thomas Jefferson Middle School
- 4th Street and J Street - St Joachim's Catholic Church
- Avenue 13 and Concord Court
- Yosemite Avenue and O Street
- 4th Street and I Street - St. Joachim's Elementary School
- Sunset Avenue and Pine Street - Thomas Jefferson Middle School
- Sunset Avenue and Orchard Avenue - Church of Christ
- Cleveland Avenue and Schnoor Street - North Point Shopping Mall
- Sherwood Way and Austin Street - Sherwood Square Apartments
- Lake Street and Ellis Street
- Ellis Street and Owens Street - Ezequiel Tafoya Alvarado Academy
- Road 26 and Martin Street - Matilda Torres High School
- Road 26 and Martin Street - Trujillos Meat Market
- Ellis Street and Owens Street
- Lake Street and Ellis Street
- Sherwood Way and Austin Avenue - Pan American Community Center
- Sherwood Way and Sonora Street
- Road 26 and Avenue 19 - Amtrak Station
- Yosemite and P Street Yosemite Manor
- Elm Street and Santa Fe Street Rancho San Miguel
- Stadium Road and Gary Lane Alpha Elementary School
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 | 50.2 | first check |
| 2026-07-30 | 46.4 | down 3.8 |
| 2026-07-31 | 46.0 | down 0.4 |
| 2026-08-01 | 45.6 | 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.
New since 2026-07-31 (1 finding)
- Error1 instance
Service data ended 0 day(s) ago.
Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
No longer reported since 2026-07-31 (1 finding)
- Service data runs out in 1 day(s). (scorecard_feed_expiring_soon)
This records the later feed state. It does not establish who made a change or why.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
What changed over time
On 2026-07-25 this feed started at grade F. On 2026-08-01 feed expired. On 2026-08-01 the check no longer reported: service data runs out in 1 day(s). As of 2026-08-01 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-08-01 Feed expired.
- 2026-07-30 Score fell 4 points, freshness fell 8 points.
Everything we checked
12 findings, ordered by severity.
Show every finding
- Error1 instance
Invalid phone number (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_phone_number' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_phone_number · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Service data ended 0 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)
- Warning145 instances
145 of 145 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)
- Warning114 instances
114 of 114 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)
- Warning12 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)
- 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
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)
- 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)
- 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)
- Info2 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. 1 validator error to resolve. Service data expired 0 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 0 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 145 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 0 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 0 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.
- 12 of 114 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 1 validator error, 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.
In California, the published guideline is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.
California Minimum GTFS Guidelines checklist (3 of 6 measured items met)
The state's own Data Process Checklist, matched item by item to what this scorecard already measures. An item marked "not measured here" is real ground the checklist covers that this tool does not check; see the official checklist for the full picture.
- Meets Publish GTFS Schedule at a stable, automatically-fetchable URL
The published feed URL downloaded at the last check.
- Not measured here Implement required fields: Fares v2, text-to-speech stop names, shapes.txt, wheelchair_boarding, and Pathways where applicable
This scorecard measures wheelchair_boarding, shapes.txt coverage, fare data, and station pathways separately, below; it does not check the Fares v2 format specifically or text-to-speech stop names.
- Not measured here Achieve a passing score in every category of the MobilityData GTFS Grading Scheme v1
This scorecard automates a proxy for the Grading Scheme's rider-facing fields (see the standards crosswalk) rather than running the scheme itself, which grades by comparison to the real world by hand.
- Not measured here Publish changes to the base schedule at least one week ahead of every service change
This scorecard does not track a feed's publish history, so advance notice cannot be checked.
- Gap Produce no critical errors in the MobilityData GTFS Validator
1 validator error to resolve.
- Not measured here Publish Trip Updates, Vehicle Positions, and Alerts feeds
This scorecard checks realtime reachability and freshness overall; it does not check for all three feed types individually.
- Not measured here Update Trip Updates and Vehicle Positions at least every 20 seconds
This scorecard samples realtime freshness; it does not check this specific 20-second cadence.
- Not measured here Publish information for at least 99% of vehicles in service
This scorecard measures the share of scheduled trips represented in TripUpdates, a related but different figure than vehicle coverage.
- Not measured here Keep 100% of trip_ids consistent between Schedule and Realtime
This scorecard does not currently check trip_id consistency between the Schedule and Realtime feeds.
- Not measured here Produce no critical errors in the Center for Urban Transportation Research realtime validator
This scorecard does not run the CUTR realtime validator.
- Not measured here Publish accessible feed links on the agency or regional partner website
This scorecard does not check the agency's own website.
- Not measured here Register GTFS and GTFS-Realtime feeds with transit.land and the Mobility Database
This scorecard does not currently check aggregator registration for this section.
- Meets Designate a technical contact in feed_info.txt's feed_contact_email
feed_info.txt states a technical contact.
- Gap wheelchair_boarding stated on stops and trips
States wheelchair access on 0% of stops and 0% of trips.
- Meets shapes.txt with a shape for every trip
All 145 trips have a shape in shapes.txt.
- Gap Fare data published, or the service marked fare-free
No fare data is published.
- Correctness 72 / 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 45 / 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/city-of-madera/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.