Feed status · checked 2026-08-01
Fresno Area Express (FAX)
Based on the feed this agency publishes
Service mode Bus
down 2.2 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 77 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 with a validity window that reaches at least 60 days out.Likely your export tool
Service data runs out in 8 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
⏱ One export setting.worth about +72 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
1503 of 1503 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
3300 of 3300 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
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 runs out in 8 day(s).
- Next action
- Re-export with a validity window that reaches at least 60 days out.
- 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
- 1503 of 1503 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
- 3300 of 3300 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 with a validity window that reaches at least 60 days out. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
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 8 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- 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
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
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 1165 instances (0 error, 1165 warning, 0 informational).
Service data runs out in 8 day(s). Publish an updated feed soon or riders will lose trip planning.
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
5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (28, 34, 35, 39, 45).
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.
1352 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("NE Brawley - Shields", "SE Shaw - Brawley", "SW Shaw - West", 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 1503 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.
- 01 (teal)
- 03 (black)
- 09 (yellow)
- 12 (red)
- 20 (blue)
- 22 (teal)
- 26 (green)
- 28 (pink)
- 29 (teal)
- 32 (red)
- 33 (orange)
- 34 (purple)
- 35 (purple)
- 38 (teal)
- 39 (brown)
- 41 (pink)
- 45 (yellow)
- 58 (green)
- 58E (pink)
| Route | Type | Line color |
|---|---|---|
| 01 FAX Q | Bus | teal |
| 03 Herndon | Bus | black |
| 09 Shaw | Bus | yellow |
| 12 Brawley / Inspiration Park | Bus | red |
| 20 Hughes/Mckinley | Bus | blue |
| 22 West Ave/Tulare | Bus | teal |
| 26 Palm/Butler | Bus | green |
| 28 DSS/Manchester/West Fresno | Bus | pink |
| 29 Church | Bus | teal |
| 32 Fresno St | Bus | red |
| 33 Belmont | Bus | orange |
| 34 First Street | Bus | purple |
| 35 Olive | Bus | purple |
| 38 Cedar | Bus | teal |
| 39 Fyi/Clinton | Bus | brown |
| 41 Malaga/Shields/Chestnut | Bus | pink |
| 45 Ashlan | Bus | yellow |
| 58 NE Fresno | Bus | green |
| 58E Childrens Hospital | Bus | pink |
List every stop
- SE Shaw - Cedar
- Sierra Station
- Barstow Station
- Ashlan Station
- Griffith Station
- Weldon Station
- Belmont Station
- NW M ST - MARIPOSA
- NE E ST - TUOLUMNE
- NE E ST - STANISLAUS
- 1755 E ST SB
- NW EL DORADO - E ST
- SW TRINITY - EL DORADO
- NW TRINITY - B ST
- NW TRINITY - STANISLAUS
- SW TRINITY - STROTHER
- NE EDEN - MODOC
- SW THORNE - EDEN
- NW Thorne - California
- NW California - Fruit
- NW California - Court
- SW TEILMAN - WOODWARD
- NW EDEN - TEILMAN
- NE EDEN - WEST
- NE EDEN - SUNSET
- NE EDEN - CRYSTAL
- NE CRYSTAL - STROTHER
- SE MARTIN LUTHER KING - CHESTER
- SE MARTIN LUTHER KING- JOLSON
- NE MARTIN LUTHER KING - ANNADALE
- SE MARTIN LUTHER KING - VINE
- SE MARTIN LUTHER KING - CHURCH
- FRESNO - HERNDON
- NE MARTIN LUTHER KING - FLORENCE
- NE Pottle - California
- NE POTTLE - KERN
- SE FRESNO - POTTLE
- SW FRESNO - MAYOR
- SE FRESNO - FULTON MALL
- SE FRESNO - N ST
- SE FRESNO - P ST
- SE FRESNO - R ST
- NE FRESNO - McKENZIE
- FRESNO - SHAW
- SE FRESNO - BELMONT
- SE FRESNO - FWY 180
- NE FRESNO - OLIVE
- SE FRESNO - HEDGES
- SE FRESNO - McKINLEY
- SE FRESNO - WELDON
- SE FRESNO - BERKLEY
- SW Fresno - Clinton
- NE FRESNO - PRINCETON
- NE FRESNO - CORNELL
- NE FRESNO - DAKOTA
- SW FRESNO - GRIFFITH
- NE FRESNO - ASHLAN
- NE FRESNO - ASHCROFT
- SE FRESNO - GETTYSBURG
- NE FRESNO - ALAMOS
- NE FRESNO - SAN JOSE
- NE FRESNO - BARSTOW
- SE FRESNO - BROWNING
- NE FRESNO - BULLARD
- NE FRESNO - ESCALON
- NE FRESNO - SIERRA
- NE FRESNO - PALO ALTO
- NE FRESNO - HOWARD
- SW Willow - Shaw
- NE FRESNO - ALLUVIAL
- NE FRESNO - EL PASO
- SW EL PASO - FRESNO
- SW FRESNO - ALLUVIAL
- SW FRESNO - HOWARD
- NW FRESNO - PALO ALTO
- SW FRESNO - SIERRA
- MLK - JENSEN
- SW FRESNO - ESCALON
- SW FRESNO - BULLARD
- SW FRESNO - BROWNING
- SW FRESNO - BARSTOW
- NW FRESNO - SAN JOSE
- SW FRESNO - ACACIA
- SW FRESNO - GETTYSBURG
- NW FRESNO - RICHERT
- SW FRESNO - ASHLAN
- NW North - Elm
- SW FRESNO - SAGINAW
- NW DAKOTA - FRESNO
- NE DAKOTA - DIANA
- SW FRESNO - SIMPSON
- NW FRESNO - PRINCETON
- NW Fresno - Berkley
- SW Fresno - Weldon
- SW FRESNO - McKINLEY
- SW FRESNO - HOME
- NW FRESNO - FWY 180
- SW FRESNO - BELMONT
- SW FRESNO - McKENZIE
- SW FRESNO - ILLINOIS
- NW FRESNO - R ST
- NW FRESNO - P ST
- NW FRESNO - O ST
- MLK - JENSEN
- NW TULARE - M ST
- NE FRESNO - BROADWAY
- NE FRESNO - B ST
- NE FRESNO - MAYOR
- SW POTTLE - FRESNO
- NW POTTLE - KERN
- SW Martin Luther King - California
- SW Martin Luther King - Florence
- NW MARTIN LUTHER KING - CHURCH
- SW MARTIN LUTHER KING - GROVE
- NW MARTIN LUTHER KING - VINE
- 2750 S MARTIN LUTHER KING SB
- SE ANNADALE - MARTIN LUTHER KING
- SE ANNADALE - IVY CENTER
- SW ANNADALE - ELM
- 2892 S ELM SB
- NE W NORTH - S NORTH
- NW FRESNO - OLIVE
- NE MARTIN LUTHER KING - NORTH
- SE BELMONT - FRUIT
- SE BELMONT - WEBER
- SW BELMONT - FERGER
- SW BELMONT - ECHO
- SW BELMONT - FULTON
- SE BELMONT - VAN NESS
- NW Fresno - Clinton
- SE BELMONT - SAN PABLO
- SE BELMONT - DIANA
- SE BELMONT - VALERIA
- SE BELMONT - FRESNO
- SE BELMONT - ANGUS
- SE BELMONT - FOURTH
- FRESNO - SHAW
- SW BELMONT - SIXTH
- SW BELMONT - NINTH
- SE BELMONT - CEDAR
- SE BELMONT - BARTON
- SW MAPLE - MCKENZIE
- NW MAPLE - TULARE
- SW MAPLE - HUNTINGTON BLVD
- FRESNO - HERNDON
- SE MAPLE - HUNTINGTON BLVD
- NE MAPLE - TULARE
- SE MAPLE - MCKENZIE
- 4467 E BELMONT WB
- NW BELMONT - CEDAR
- NW BELMONT - NINTH
- NE BELMONT - MILLBROOK
- NE BELMONT - FOURTH
- NW BELMONT - ANGUS
- NE BELMONT - FRESNO
- NE BELMONT - CLARK
- NW BELMONT - DIANA
- NW BELMONT - BLACKSTONE
- NW BELMONT - SAN PABLO
- NE BELMONT - VAN NESS
- NW BELMONT - FULTON
- NW BELMONT - ECHO
- NE BELMONT - FERGER
- NW BELMONT - PALM
- BELMONT - DELNO
- NE BELMONT - HARRISON
- NW BELMONT - FRUIT
- NE BELMONT - DELNO
- NW JENSEN - LOTUS
- NE ELM - JENSEN
- NE ELM - CHURCH
- NE ELM - REV CHESTER RIGGINS
- BELMONT - ABBY
- NE C St - Ventura
- NE C ST - I NYO
- SE C ST - MARIPOSA
- SE C ST - FRESNO
- SW M ST - TULARE
- M Street Station
- NE FIRST - HUNTINGTON
- SE FIRST - TULARE
- BELMONT - FIRST
- NE FIRST - McKENZIE
- NE FIRST - BELMONT
- NE FIRST - TYLER
- NE FIRST - OLIVE
- NE FIRST - FLORADORA
- NE FIRST - McKINLEY
- SE FIRST - WELDON
- NE FIRST - CLINTON
- NE FIRST - PRINCETON
- MAPLE - BELMONT
- SE FIRST - REDLANDS
- NE FIRST - LANSING
- NE FIRST - ASHCROFT
- NE FIRST - GETTYSBURG
- NE FIRST - RIALTO
- NE FIRST - SAN JOSE
- NE FIRST - BARSTOW
- NE FIRST - ROBERTS
- NW Maple - El Monte
- SE FIRST - ESCALON
- NE FIRST - SIERRA
- 6592 N FIRST
- SE WARNER - FIRST
- 1177 E WARNER
- SE Herndon - Millbrook
- SE CEDAR - ELEVENTH
- MAPLE - BUTLER
- NE MILLBROOK - SPRUCE
- SE MILLBROOK - MINARETS
- NW FIRST - WARNER
- SE Church - Maple
- SW FIRST - ELLERY
- SW FIRST - ESCALON
- SW FIRST - ROBERTS
- SW FIRST - BARSTOW
- SW FIRST - SAN JOSE
- NW FIRST - HOLLAND
- NW FIRST - DAKOTA
- SW FIRST - DAYTON
- SW FIRST - PRINCETON
- SW FIRST - CLINTON
- SW FIRST - YALE
- SW FIRST - UNIVERSITY
- SW FIRST - McKINLEY
- NW FIRST - FLORADORA
- SW FIRST - HEDGES
- SW FIRST - OLIVE
- NW Shaw - Cedar
- NE Maple - Kings Canyon
- SW FIRST - CLAY
- SW FIRST - BELMONT
- SW FIRST - McKENZIE
- SW FIRST - TULARE
- SW FIRST - HUNTINGTON
- NW Ventura - Hazelwood
- NW Ventura - P St
- B SHELTER
- NW FRESNO - F ST
- SW C ST - FRESNO
- BELMONT - MAPLE
- NW C ST - TULARE
- SW C ST - KERN
- SW C ST - MONO
- SW B St - Ventura
- SW ELM - GENEVA
- SW ELM - REV CHESTER RIGGINS
- BELMONT - FIRST
- SW CHERRY - CHURCH
- and 1253 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — down 2.2 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 42.6 | first check |
| 2026-07-30 | 40.5 | down 2.1 |
| 2026-07-31 | 40.1 | down 0.4 |
| 2026-08-01 | 37.9 | down 2.2 |
What changed since your last check
- Correctness down 4.0
- Freshness down 1.7
- Rider experience no change
What changed in this feed
Overall score fell 2.2 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)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
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)
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
14 findings, ordered by severity.
Show every finding
- Warning3300 instances
3300 of 3300 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)
- Warning3300 instances
3300 of 3300 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)
- Warning1503 instances
1503 of 1503 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)
- Warning1088 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)
- Warning71 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some route lines list the same point twice in a row.
Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)
Finding code: equal_shape_distance_same_coordinates · 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 30 days.
If a new feed isn't published before it ends, trip planners will drop your agency and riders will see no service.
Fix: Schedule a feed re-export now so the new calendar is live well before the current one ends. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date30_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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
Service data runs out in 8 day(s).
When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)
Finding code: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info1086 instances
About 1086 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Needs attention
This feed is close to NTD-ready. Service data runs out in 8 days; renew before you certify.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Needs attention
- Service data runs out in 8 days; renew before you certify.
- 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 3300 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 runs out in 8 days; renew to qualify. 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 runs out in 8 days; renew to qualify.
- 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.
At risk for the Google and Apple Maps four-week coverage bar. This feed has 8 days of service left. Maps needs at least four weeks (28 days) of upcoming service, so your agency will fall out of trip planners soon. Re-export with a longer calendar.
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 (4 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.
- Meets Produce no critical errors in the MobilityData GTFS Validator
Passes validation with no errors.
- 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.
- Gap Designate a technical contact in feed_info.txt's feed_contact_email
feed_info.txt has no feed_contact_email or feed_contact_url.
- 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 3300 trips have a shape in shapes.txt.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- Correctness 60 / 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 13 / 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 27 / 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/fresno-area-express-fax/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.