Feed status · checked 2026-08-01
Yuma County Intergovernmental Public Transportation Authority (YCIPTA)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Arizona.
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 65 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
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
427 of 427 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
174 of 174 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
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.
174 of 174 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 +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
- 427 of 427 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
- 174 of 174 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
- Feed evidence
- 174 of 174 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
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. 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.
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. 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 153 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.
Score by category
The MobilityData validator flagged 5 kinds of issue across 182 instances (0 error, 8 warning, 174 informational).
Service data covers the next 153 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
392 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Castle Dome Avenue @ Yuma Palms Parkway", "Redondo Center Drive @ 16th Street", "Redondo Center Drive @ Plaza Circle", 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 427 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 (orange)
- 95 (yellow)
- 4 (green)
- 6A (blue)
- 8 (yellow)
- 9 (gray)
- 5 (blue)
- 3 (brown)
- 10 (teal)
- 4A (green)
| Route | Type | Line color |
|---|---|---|
| 2 Orange Route 2 - East Yuma/Colleges | Bus | orange |
| 95 Yellow Route 95 - Highway 95 South | Bus | yellow |
| 4 Green Route 4 - Central Yuma Circulator via Pacific Avenue | Bus | green |
| 6A Purple Route 6A - Avenue A/Cocopah Reservations | Bus | blue |
| 8 Gold Route 8 - Interstate 8/Wellton | Bus | yellow |
| 9 Silver Route 9 - South County AWC Connector | Bus | gray |
| 5 Blue Route 5 - Quechan Shuttle | Bus | blue |
| 3 Brown Route 3 - Fortuna Foothills Shuttle | Bus | brown |
| 10 Turquoise Route 10 - Interstate 8/El Centro/Yuma | Bus | teal |
| 4A Green Route 4A - Central Yuma Circulator via Avenue B | Bus | green |
List every stop
- 24th Street @ Tamarack Center
- 24th Street @ Otondo Drive
- 24th Street @ Vista De Castillo Drive
- Avenue 9E @ 24th Street
- Avenue 9E @ 28th Street
- Avenue 9E @ 31st Street
- 32nd Street @ Avenue 8E
- South Frontage Road @ Desert Air Boulevard
- South Frontage Road @ Avenue 9E
- South Frontage Road @ Westwind Boulevard
- South Frontage Road @ Fortuna Road
- South Frontage Road Across Avenue 8 1/2E
- 32nd Street @ Avenue 8E
- Avenue 9E @ 31st Street
- Avenue 9E @ 28th Street
- 24th Street @ Avenue 9E
- 24th Street Across Vista De Castillo Avenue
- 24th Street @ Yuma Education Consortium Yard
- 24th Street @ Otondo Drive
- 24th Street @ Desert Mesa Elementary And Avenue 7 1/2E
- 24th Street @ Gila Ridge High And College Avenue
- Pacific Avenue @ 16th Street - after Starbucks Coffee
- Pacific Avenue @ 20th Street
- 24th Street @ Arizona Avenue
- 23rd Avenue @ 28th Street
- 21st Drive Across from Yuma County Library Main Branch
- Avenue B @ 32nd Street
- US Highway 95 @ Patricia Lane
- US Highway 95 @ County 15th Street
- Cocopah Casino Main Entrance
- US Highway 95 @ Avenue C
- Main Street Somerton Across from Cholla Avenue
- Main Street Somerton @ Columbia Avenue
- Main Street Somerton @ Somerton Avenue
- Main Street Somerton @ State Avenue
- Main Street Somerton @ Carliste Avenue
- Main Street Somerton @ Cesar Chavez Boulevard
- US Highway 95 @ Housing Department
- Main Street Gadsen @ 1st Avenue
- Main Street Gadsen @ 4th Avenue
- Main Street Gadsen @ 6th Avenue
- Juan Sanchez Boulevard @ Main Street
- Main Street @ Juan Sanchez Boulevard
- US Highway 95 @ Lakin Drive
- US Highway 95 @ Estibella Drive
- US Highway 95 @ Piceno Avenue
- US Highway 95 @ Walmart Driveway
- Main Street Gadsden @ County 19th Street
- Main Street @ 5th Avenue
- Main Street @ 1st Avenue
- US Highway 95 Across from Housing Deptartment
- Main Street Somerton @ Cesar Chavez Avenue
- Main Street Somerton @ Federal Avenue
- Main Street Somerton Across State Avenue
- Main Street Somerton @ Somerton Avenue
- Main Street Somerton @ Bingham Avenue
- Main Street Somerton @ Cholla Avenue
- US Highway 95 @ Avenue C
- US Highway 95 @ County 15th Street
- US Highway 95 @ Patricia Lane
- 32nd Street @ Avenue B
- 21st Drive @ Yuma County Library Main Branch
- 21st Drive @ Yuma Catholic High School
- 4th Avenue @ 24th Street
- 4th Avenue @ 22nd Street
- 4th Avenue @ 20th Street
- 4th Avenue @ 18th Street
- Pacific Avenue @ 24th Street
- Pacific Avenue @ San Marcos Drive
- Pacific Avenue @ Palo Verde Street
- Pacific Avenue @ Walmart
- 32nd Street @ Pacific Avenue
- 32nd Street @ Fortuna Avenue
- 32nd Street @ Chiquita Drive
- 32nd Street @ Arizona Avenue
- 32nd Street @ Catalina Drive
- 4th Avenue Extension @ 32nd Street
- 32nd Street @ 4th Avenue
- 32nd Street @ 8th Avenue
- Avenue A @ 32nd Street
- Avenue A Across from Kofa High School
- Avenue A @ 28th Street
- Avenue A @ Westridge Drive
- Avenue A @ Southwest Medical Center
- 24th Street @ Avenue B
- 24th Street @ 34th Drive
- 24th Street @ 37th Avenue
- Avenue C @ 24th Street
- Avenue C @ 21st Lane
- Avenue C @ 20th Street
- Avenue C @ 18th Street
- 16th Street @ Avenue C
- 16th Street @ 31st Drive
- 16th Street @ Arcadia Lane
- Avenue B @ 16th Street
- Avenue B @ 12th Street
- Avenue B @ Del Valle Mobile Home Park
- Avenue B @ 8th Street
- Avenue B @ Immaculate Conception Church And School
- Avenue B Across 5th Street
- 3rd Street @ 24th Avenue
- 3rd Street @ 20th Avenue
- 3rd Street @ 17th Avenue
- 3rd Street @ 15th Avenue
- 3rd Street @ 13th Avenue
- 3rd Street @ Avenue A
- 3rd Street @ 8th Avenue
- 3rd Street @ 6th Avenue
- Giss Parkway @ 4th Avenue
- Giss Parkway @ 7th Street
- Castle Dome Avenue @ Yuma Palms Parkway (Near Kneaders)
- Castle Dome Avenue Across from Shilo Inn
- Chapay Street @ Quail Run Loop
- Strand Avenue @ Chapay Street
- Cocopah Drive @ Broadmore
- Avenue C @ 4th Place
- Avenue C @ Amador Lane
- Cottonwood Loop @ Salt Cedar Avenue
- Cottonwood Loop @ Head Start School
- Cottonwood Park Loop @ Cottonwood Loop
- Cottonwood Loop @ Salt Cedar Avenue
- Veterans Way @ Cocopah Tribe Administration
- Veterans Drive @ Veterans Way
- Centre Avenue - Across Hava Street/Community Center
- Centre Avenue @ Steamboat Street
- County 16th Street - Across from Rincon de Eslana
- County 16th Street @ Paso Descanso
- County 16th Street @ Avenue B
- 12th Street Behind Harkins Theatre
- Avenue A @ 24th Street
- Avenue A @ 22nd Street
- Avenue A @ 20th Street
- Avenue A @ 18th Street
- Avenue A @ 16th Street
- Avenue A @ 14th Street
- Avenue A @ 12th Street
- Pacific Avenue Across from 14th Street
- Avenue A @ 10th Street
- 8th Street @ 12th Avenue
- 8th Street @ 14th Avenue
- 8th Street @ Magnolia Avenue
- 8th Street @ Dora Avenue
- 8th Street @ Avenue B
- 8th Street @ Clifford Way
- 8th Street @ May Avenue
- 8th Street @ Palm Avenue
- 16th Street In front of Panda Express
- Chapay Way @ Levee Road
- Avenue I @ Cocopah Vocational Training Center
- Veterans Way - Across From Cocopah Tribal Police
- Redondo Center Drive @ 16th Street
- Yuma County Library Foothills Branch
- Wellton Jack in the Box
- Arizona Avenue @ William Street
- Arizona Avenue @ Fresno Street
- Dome Street @ San Jose Avenue
- Dome Street @ Los Angeles Street
- Los Angeles Street @ Fresno Street
- Los Angeles Street @ William Street
- Redondo Center Drive @ Plaza Circle
- Los Angeles Street @ Center Street
- Arizona Avenue @ Los Angeles Street
- Arizona Avenue @ Maybelle Street
- Arizona Avenue @ William Street
- South Frontage Road @ Fortuna Road
- Redondo Center Drive @ Furniture Row
- Araby Road @ 24th Street
- Juan Sanchez Boulevard @ 4th Avenue
- Juan Sanchez Boulevard @ 6th Avenue
- Juan Sanchez Boulevard - Across from 7th Avenue
- 8th Avenue @ Juan Sanchez Boulevard
- 8th Avenue - Across from America Street
- AWC San Luis Center @ Main Office
- 8th Avenue @ America Street
- Juan Sanchez Boulevard @ 8th Avenue
- Juan Sanchez Boulevard @ 9th Avenue
- 3rd Street @ Gila Street (Downtown Yuma Transit Center)
- Araby Road @ 32nd Street
- Araby Road @ 32nd Street
- Juan Sanchez Boulevard @ 9th Street
- Juan Sanchez Boulevard @ 8th Avenue
- Juan Sanchez Boulevard @ 7th Avenue
- Juan Sanchez Boulevard @ 6th Avenue
- Steamboat Street @ Orange Grove Way
- Gila Street @ 1st Street
- Ligurta Station @ US Highway 80
- US Highway 95 @ Avenue D
- US Highway 95 @ Avenue D
- Across Quechan Community Center @ San Pasqual School Road
- Baseline Road @ San Pasqual School Road
- 1st Street @ Main Street
- Ironwood Drive @ Ironwood Terrace
- Arnold Road @ Cocopah Road
- Arnold Road @ Baseline Road
- Ironwood Drive @ Ironwood Terrace
- 1st Street @ 1st Avenue
- Winterhaven Dr @ Jimbo's Towing
- Quechan Casino Resort @ Main Entrance
- Castle Dome Avenue @ Yuma Palms Parkway
- Winterhaven Dr @ Sans End RV Park (2209 Winterhaven Dr)
- Winterhaven Dr @ 2nd Avenue
- 1st Street @ 4th Avenue
- 1st Street @ 1st Avenue
- Agnes Road @ Indian Hill Road
- Agnes Road @ Quechan Drive
- Giss Parkway @ Gila Street
- 16th Street @ Sunridge Drive
- US Highway 95 @ County 20 1/2 Street
- 1st Street @ 3rd Street / City Hall
- 2nd Street @ 1st Avenue
- 2nd Street @ Main Street
- Paradise Casino @ Agnes Road
- Redondo Center Drive Across from Furniture Row
- Redondo Center Drive Across From Social Security
- Gila Street @ 3rd Street (Downtown Yuma Transit Center)
- Quechan Casino Resort @ Employee Entrance
- Quechan Drive @ Indian Hill Road
- 24th Street @ Pacific Avenue
- 24th Street @ Olivia Avenue
- 24th Street @ Kennedy Lane
- 16th Street Across Redondo Center Drive
- Riverside Drive @ Hope Way
- Avenue F @ San Pedro Street
- Avenue F @ Olivos Drive
- YCAT Office @ 14th Street
- Castle Dome Avenue @ 12th Street
- Winterhaven Drive @ Railroad Avenue
- Quechan Drive @ Sapphire Lane
- Somerton Avenue @ 14th Street
- Somerton Avenue @ Patricia Street
- Somerton Avenue @ Garvin Street
- Somerton Avenue @ Joshua Street
- Somerton Avenue @ Crane Street
- Somerton Avenue @ Eucalyptus Street
- 4th Avenue @ 1st Street
- 32nd Street @ Araby Road
- 32nd Street @ Avenue 6E
- 32nd Street @ Blue Diamond RV Park
- 32nd Street @ Avenue 5 1/2 E
- 32nd Street @ Avenue 5E
- 32nd Street @ Soar Avenue
- 32nd Street @ Avenue 4E
- 32nd Street @ Avenue 3 1/2 E
- 4th Avenue @ 3rd Street
- 32nd Street @ Shortway
- Avenue 3E @ 32nd Street
- Avenue 3E - Across Palo Verde St
- 24th Street @ Avenue 3E
- 24th Street @ Avenue 2 5/10
- 24th Street @ Yuma Community Food Bank
- and 177 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 | 69.3 | first check |
| 2026-07-30 | 69.3 | no change |
| 2026-07-31 | 69.3 | no change |
| 2026-08-01 | 69.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
10 findings, ordered by severity.
Show every finding
- Warning427 instances
427 of 427 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)
- Warning174 instances
174 of 174 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)
- Warning174 instances
174 of 174 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)
- Warning4 instances
Some service calendars have no days of the week switched on.
Trips tied to these calendars never run; they are dead data that can mask real schedule problems.
Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)
Finding code: service_has_no_active_day_of_the_week · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · 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
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Finding code: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Finding code: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info174 instances
Unsorted stop times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unsorted_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: unsorted_stop_times · See MobilityData GTFS Validator rules (opens the validator rules 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 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 153 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 174 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 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 153 days.
- 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 153 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 83 / 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 85 / 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 38 / 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/yuma-county-intergovernmental-public-transportation-authority-ycipta/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.