Feed status · checked 2026-08-02
Cache Valley Transit District
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Utah.
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.
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
336 of 336 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
674 of 674 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 feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool
feed_info.txt is missing its start/end dates Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
⏱ Two fields, set once in export settings.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
- 336 of 336 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
- 674 of 674 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
- feed_info.txt is missing its start/end dates
- Next action
- Add feed_info.txt with feed_start_date and feed_end_date to your export.
- 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 feed_info.txt with feed_start_date and feed_end_date to your export. · 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 states that service is published through 2099-12-31. This may be intentional or a placeholder; confirm current service with the transit operator.
- 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 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 12 kinds of issue across 289 instances (0 error, 284 warning, 5 informational).
Service is published through 2099-12-31. It may be intentional, but confirm the end date before treating the feed as maintained.
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.
2 accessibility depth signals
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (8).
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.
59 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("296 East Center St", "2470 North Main St, N Logan", "150 East 500 North - Route 11 & 16", 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.
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 336 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.
- 1 (orange)
- 2 (red)
- 3 (red)
- 5 (pink)
- 6 (purple)
- G (gray)
- B (teal)
- 11 (green)
- 16 PM (teal)
- 15 (purple)
- 12 (red)
- 16 AM (green)
- 8 (gray)
- 7 (blue)
- 9 (green)
| Route | Type | Line color |
|---|---|---|
| 1 Route 01 | Bus | orange |
| 2 Route 02 | Bus | red |
| 3 Route 03 | Bus | red |
| 5 Route 05 | Bus | pink |
| 6 Route 06 | Bus | purple |
| G LOOP - Green | Bus | gray |
| B LOOP - Blue | Bus | teal |
| 11 Route 11 | Bus | green |
| 16 PM Route 16 - PM Weekday ONLY | Bus | teal |
| 15 Route 15 | Bus | purple |
| 12 Route 12 | Bus | red |
| 16 AM Route 16 - AM Weekday ONLY | Bus | green |
| 8 Route 08 | Bus | gray |
| 7 Route 07 | Bus | blue |
| 9 Route 09 | Bus | green |
List every stop
- 150 East 500 North - Route 7 (700)
- 150 East 500 North - Route 8 (800)
- 649 North 200 West
- 450 E 800 S Preston ID
- 1042 North 1000 West
- 650 North 800 East
- 574 East 200 North (Temp Stop)
- 285 West 1700 South (Temp Stop)
- 150 East 500 North - Route 1
- 1574 East 1500 North
- 1521 North 800 East
- 150 East 500 North - Route 2
- 1111 North 800 East
- 150 East 500 North - Route 3
- 296 East Center St
- 2470 North Main St, N Logan
- 150 East 500 North - Route 5
- 2810 N Wolf Pack Way, N Logan
- 2371 North 400 East, N Logan
- 150 East 500 North - Route 12
- 100 E 1600 N
- 36 West 1200 South
- 181 East 400 North
- 75 West 400 North
- 225 North 200 West
- 600 West 400 South
- 520 West 400 South
- 395 South 300 West
- 190 South 400 West
- 90 South 400 West
- 186 North 400 West
- 224 North 200 West
- 50 West 400 North
- 150 East 500 North - Route 11 & 16
- 3155 South 500 West
- 185 South State, Franklin
- 202 East 300 North
- 320 East 300 North
- 255 North 400 East
- 351 East 200 North
- 175 North 300 East
- 49 North 100 East
- 430 East Center St
- 60 North 500 East
- 590 East Canyon Rd
- 771 East Canyon Rd
- 275 North Crocket Ave
- 115 North Riverside Dr
- 27 North Riverside Dr
- 589 East Center St
- 485 East Center St
- 369 East Center St
- 240 North 100 East
- 31 South 100 East, Preston
- 150 East 500 North - Route 15
- 157 West 600 South (Richmond)
- 539 South State, Richmond
- 319 South State (Richmond)
- 193 South State, Richmond
- 39 S State, Richmond
- 124 S Hwy 91, Richmond
- 453 West 100 North
- 950 South Main St
- 355 North Main
- 55 North Main
- 359 South Main
- 449 South Main
- 995 South Main
- 520 West 100 North
- 670 South Main St
- 354 South Main St
- 50 North Main St
- 280 North Main St
- 3235 S Hwy 165, Nibley
- 3665 South Hwy 165
- 3835 South Hwy 165
- 387 North 800 East, Hyrum
- 79 North 800 East, Hyrum
- 725 East Main St, Hyrum
- 465 East Main St, Hyrum
- 75 East Main St, Hyrum
- 90 West Main St, Hyrum
- 46 North 200 West, Hyrum
- 186 North 200 West , Hyrum
- 380 North 200 West, Hyrum
- 220 West 400 North, Hyrum
- 375 North 400 West, Hyrum
- 275 North 400 West, Hyrum
- 45 North 400 West, Hyrum
- 83 W Main St, Hyrum
- 289 South Center St, Hyrum
- 190 East 300 South, Hyrum
- 424 East 300 South, Hyrum
- 608 East 300 South, Hyrum
- 850 East 300 South, Hyrum
- 270 South 1300 East, Hyrum
- 102 South 1300 East, Hyrum
- 959 East Hwy 101, Hyrum
- 923 E Highway 101, Hyrum
- 310 N 800 E, Hyrum
- 3806 South Hwy 165, Millville
- 3604 South Hwy 165, Millville
- 3230 S Hwy 165, Millville
- 1235 S Hwy 165
- 2620 South Hwy 165
- 2835 South Hwy 165
- 2850 South Hwy 165, Millville
- 2520 South Hwy 165, Millville
- 1300 S Hwy 165, Providence
- 341 South 100 East
- 640 South 100 East
- 715 South Gateway Drive
- 357 North Gateway Drive
- 45 West 1200 South
- 1305 South Talon Dr
- 443 West 1700 South
- 1771 Hyclone Dr
- 1129 West 1800 South
- 1776 South 1280 West
- 1260 West 1610 South
- 1776 South 1200 West
- 1118 West Nibley Park Ave
- 860 West Nibley Park Ave
- 740 West 2600 South
- 2639 South 600 West
- 2775 South 600 West
- 2963 South 600 West
- 625 West 3200 South
- 965 West 3200 South
- 2930 South 1000 West
- 2710 South 1000 West
- 2560 South 1000 West
- 1129 West Nibley Park Ave
- 1285 W Nibley Park Ave
- 410 West 1700 South
- 1556 South Talon Drive
- 1250 South Talon Drive
- 1240 South Legrand St
- 358 North Gateway Dr
- 760 South Gateway Dr
- 690 South 100 East
- 290 South 100 East
- 10 South 100 East
- 1559 South Talon Dr
- 31 South 300 East
- 280 South 300 East
- 813 West 200 South
- 444 North 1000 West
- 150 East 500 North - Route 9
- 390 West 1800 North
- 250 West 1800 North
- 1711 North 200 West
- 1425 North 200 West
- 1331 North 200 West
- 1197 North 200 West
- 987 North 200 West
- 62 West 500 North
- 61 West 500 North
- 566 North 200 West
- 740 North 200 West
- 928 North 200 West
- 1185 North 200 West
- 1320 North 200 West
- 285 West 1400 North
- 450 West 1400 North
- 1420 North 600 West
- 560 West 1800 North
- 310 East 500 North
- 508 East 500 North
- 890 North 1200 East
- 1110 North 1200 East
- 1210 East 1400 North
- 1450 East 1500 North
- 251 West 400 North
- 239 North 400 West
- 100 North 600 West
- 125 South 600 West
- 730 North 1000 West
- 1330 North 1000 West
- 750 West 1400 North
- 1301 North 600 West
- 941 North 600 West
- 675 North 600 West
- 542 West 400 North
- 428 West 400 North
- 272 West 400 North
- 1295 North 1600 East
- 1225 North 1600 East
- 1075 North 1600 East
- 989 North 1500 East
- 1500 East Maple Drive
- 489 East 500 North
- 285 East 500 North
- 115 W Golf Course Rd
- 290 West Golf Course Rd
- 679 South 300 West
- 206 South 100 West
- 50 South 100 West
- 32 North 100 West
- 50 West 200 North
- 51 West 200 North
- 45 North 100 West
- 280 South 100 West
- 755 South Main
- 1450 North 1200 East
- 1680 North 1200 East, N Logan
- 2046 N 1200 E, N Logan
- 1121 East 2100 North, N Logan
- 2230 North 800 East, N Logan
- 2480 North 800 East, N Logan
- 2740 North 800 East, N Logan
- 670 South 250 East, Hyde Park
- 220 South 250 East, Hyde Park
- 104 South 100 East, Hyde Park
- 67 E Hyde Park Lane, Hyde Park
- 185 West Hyde Park Lane, Hyde Park
- 655 West Hyde Park Lane, Hyde Park
- 4088 North Main, Hyde Park
- 850 S Main, Smithfield
- 50 East 600 South, Smithfield
- 170 East 600 South, Smithfield
- 486 S 250 E, Smithfield
- 210 South 300 East, Smithfield
- 115 East 100 South, Smithfield
- 51 East 100 North, Smithfield
- 180 North Main, Smithfield
- 454 North Main, Smithfield
- 640 North Main, Smithfield
- 604 North 200 East
- 704 North 200 East
- 918 North 200 East
- 1206 North 200 East
- 1360 North 200 East
- 330 East 1400 North
- 465 East 1400 North
- 1500 North 600 East
- 1750 North Research Pkwy
- 1800 North 600 East
- 1775 North 800 East
- 1380 North 800 East
- 1200 North 800 East
- 695 East 1000 North
- 1090 North 600 East
- 1320 North 600 East
- 545 East 1400 North
- 313 East 1400 North
- 1365 North 200 East
- 979 North 200 East
- 165 East 700 North
- 1201 North 200 East
- and 86 more (see the full list on the map or in the GeoJSON)
Over time
This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.
Everything we checked
17 findings, ordered by severity.
Show every finding
- Warning674 instances
674 of 674 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)
- Warning336 instances
336 of 336 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)
- Warning234 instances
234 of 674 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)
- Warning162 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)
- Warning52 instances
On some trips the stop distances run a little past the end of the route line.
The stop and shape distance values don't quite line up, so any math that uses them can drift.
Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning42 instances
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)
- Warning10 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)
- Warning10 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
Some values have extra spaces at the start or end.
A stray space can break a match, so a stop or route may fail to link across files.
Fix: Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this. (Usually one export setting.)
Finding code: leading_or_trailing_whitespaces · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt does not state when this feed starts and ends.
Without stated dates, apps can't warn anyone before your data goes stale; it just disappears one day.
Fix: Fill in feed_start_date and feed_end_date in feed_info.txt. (Two fields, likely set once in your export settings.)
Finding code: missing_feed_info_date · 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
Same name and description for stop (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_name_and_description_for_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: same_name_and_description_for_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates
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)
- 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)
- Info3 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
Service extends far in the future (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: service_extends_far_in_the_future · 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
- The published window is current, but its service end date is unusually distant; confirm that date is intentional.
- 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 674 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
- The published window is current, but its service end date is unusually distant; confirm that date is intentional.
- 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.
- 10 of 336 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.
Clears the Google and Apple Maps four-week coverage bar. This feed clears the four-week coverage window, but its service end date is unusually distant. Confirm that date is intentional before treating it as evidence of ongoing maintenance. 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 45 / 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 40 / 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/cache-valley-transit-district/2026-08-02.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-02. 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.