Feed status · checked 2026-08-01
Fresno County Rural Transit Agency (FCRTA)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
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 29 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
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
83 of 83 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
Add 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.
12 of 40 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.
⏱ Usually one value per route pattern in your scheduling source.worth about +4 points in its category
Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras.
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.
⏱ A quick look at the flagged files.
This feed is built with National RTAP's GTFS Builder. Your staff can usually make these changes in the GTFS Builder spreadsheets and republish, and National RTAP's help desk supports that at no cost.
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
- 83 of 83 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
- 12 of 40 trips lack rider-facing destination or direction text.
- Next action
- 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.
- 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
- Some files contain columns that are not part of the GTFS spec.
- Next action
- Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras.
- 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. This feed is built with National RTAP's GTFS Builder. Your staff can usually make these changes in the GTFS Builder spreadsheets and republish, and National RTAP's help desk supports that at no cost.
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 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. · Read the fix guide
Make the change. This feed is built with National RTAP's GTFS Builder. Your staff can usually make these changes in the GTFS Builder spreadsheets and republish, and National RTAP's help desk supports that at no cost.
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.
Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. · Read the fix guide
Make the change. This feed is built with National RTAP's GTFS Builder. Your staff can usually make these changes in the GTFS Builder spreadsheets and republish, and National RTAP's help desk supports that at no cost.
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 152 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 100% 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 your vendor a fix request
This feed comes from National RTAP's GTFS Builder, so your own staff can usually make these changes in the GTFS Builder spreadsheets and republish. If a consultant maintains it for you, forward this to them. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 2 kinds of issue across 31 instances (0 error, 0 warning, 31 informational).
Service data covers the next 152 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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
8 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Selma (E&V Flowers)", "Fresno Downtown (Amtrak/Greyhound Station Bus Shelter)", "Sanger (North Ave Bus Shelter)", 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 83 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.
- Huron Transit (green)
- Coalinga Transit (green)
- Southeast Transit (green)
- Westside Transit (green)
- Orange Cove Transit (green)
- Kingsburg-Reedley (green)
- Sanger Express (green)
| Route | Type | Line color |
|---|---|---|
| Huron Transit | Bus | green |
| Coalinga Transit | Bus | green |
| Southeast Transit | Bus | green |
| Westside Transit | Bus | green |
| Orange Cove Transit | Bus | green |
| Kingsburg-Reedley | Bus | green |
| Sanger Express | Bus | green |
List every stop
- Coalinga Regional Medical Center
- Coalinga (Tractor Supply Co.)
- Coalinga (Reel Time Entertainment)
- Fresno (Downtown Van Ness Bus Shelter)
- Sanger (Davita Dialysis Center)
- Selma (E&V Flowers)
- Firebaugh (Family Dollar Bus Shelter)
- Mendota (Chevron)
- Kerman (Walmart Bus Shelter)
- Firebaugh (Bench at Firebaugh Supermarket)
- Mendota (Ramon's Tire Shop)
- Firebaugh Senior Center
- Firebaugh (Hacienda and Mobile Home Park)
- Latino Market
- Mendota (Washington Elementary School Bus Shelter)
- Mendota (Quickeroo Bus Shelter)
- Mendota (Across from 76 Gas Station)
- Mendota (76 Gas Station)
- Kerman (Me-n-Ed's Bus Shelter)
- Kerman (Bench at Round Table Pizza)
- Fresno Downtown (Amtrak/Greyhound Station Bus Shelter)
- Fresno (Courthouse Park - FAX Bus Shelter L)
- Fresno Community Hospital
- Fresno (Bus Shelter across from County Social Services)
- Fresno (County Social Services)
- Sanger Hospital Bus Shelter
- Sanger (Kings River High School)
- Sanger City Hall Bus Shelter
- Sanger (Across from Community Center)
- Sanger (Community Center Bus Shelter)
- Sanger (North Ave Bus Shelter)
- Parlier (Across from Martinez Elementary School)
- Parlier (Martinez Elementary School)
- Parlier City Hall Bus Shelter
- Parlier City Hall Bus Shelter
- Parlier (United Health Center)
- Parlier (Across from UnitedHealth Center)
- Reedley College (Manning Ave) - Shelter west of driveway to Parking Lot B on E Manning Ave
- Reedley College
- Reedley Community Center
- Reedley (Princess Institute of Beauty)
- Orange Cove (AC Market Bus Shelter)
- Orange Cove (JO Eaton Memorial Park)
- Orange Cove (Los Amigo Market)
- Orange Cove (Bus Shelter Across from Library)
- Kingsburg (Coffee Pot Park Bus Shelter)
- Selma (Bench at Family HealthCare Network)
- Selma (Selma Station Shopping Center)
- Selma (Selma Station Shopping Center)
- Fowler (Bus Shelter - 7th St & Merced St)
- Fresno Yosemite International Airport Bus Shelter
- Easton (Easton Market)
- Easton (Electrical Power Source)
- Fresno (Across from GLW Service Auto and Truck Repair)
- Fresno (GLW Service Auto and Truck Repair)
- Raisin City (Across from Raisin City Market)
- Caruthers (Across from Valley Foods Supermarket)
- Caruthers (Valley Foods Supermarket)
- Caruthers (Caruthers Raisin Packing Co)
- Caruthers (Valero)
- Caruthers (Elkhorn Market)
- Caruthers (Across from Elkhorn Market)
- Riverdale (BMO Bank)
- Riverdale (BMO Bank)
- Lanare (Mt. Whitney Minimart)
- Lanare (Across from Mt. Whitney Minimart)
- Five Points (Five Points Liquor store)
- Five Points (Across from Five Points Liquor store)
- Five Points (Five Star Market)
- Huron (Rhino Liquor Market)
- Huron (West American Bank)
- Coalinga (Downtown Parking Lot Bus Shelter)
- Coalinga (I-5/HWY 198 Starbucks)
- Coalinga (Shell Station at Harris Ranch)
- Coalinga (Shell Station at Harris Ranch)
- Huron Post Office
- Coalinga (West Hills College)
- Reedley (Brooks Ranch)
- Fresno (Chevron)
- B Shelter
- Fowler (Adventist Health/Valley Children's Bus Shelter)
- Sanger (North Ave Bus Shelter)
- B Shelter
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 90.2 | first check |
| 2026-07-30 | 90.3 | up 0.1 |
| 2026-07-31 | 90.3 | no change |
| 2026-08-01 | 90.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
4 findings, ordered by severity.
Show every finding
- Warning83 instances
83 of 83 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
12 of 40 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)
- Info26 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)
- Info5 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)
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 152 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 40 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 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 152 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 152 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 99 / 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 100 / 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 70 / 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/fcrta/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.