Feed status · checked 2026-08-01
City of Tracy
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 16 hours ago; last changed 38 days ago.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
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
0 of 0 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
7 of 7 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.
7 of 7 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
Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- 0 of 0 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
- 7 of 7 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
- 7 of 7 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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. 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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. 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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. 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
- No fare information is published in the feed.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send Trillium a fix request
This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 3 kinds of issue across 32 instances (0 error, 0 warning, 32 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 not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
Not scored yet. Nothing here counts against the grade.
Routes and stops
This feed has no located stops.
| Route | Type | Line color |
|---|---|---|
| Paratransit | Bus | green (no shape in feed) |
| TRACER Plus | Bus | brown (no shape in feed) |
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 72.6 | first check |
| 2026-07-30 | 72.6 | no change |
| 2026-07-31 | 72.6 | no change |
| 2026-08-01 | 72.6 | 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
9 findings, ordered by severity.
Show every finding
- Warning7 instances
7 of 7 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)
- Warning7 instances
7 of 7 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)
- 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)
- Warning0 instances
0 of 0 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)
- Info21 instances
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info8 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
This feed includes flexible (demand-responsive) service, and riders are told how to book it.
Dial-a-ride and zone service are described for trip planners, not just fixed routes.
Fix: No action needed. (None.)
Finding code: scorecard_flex_service
- Info0 instances
About 0 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)
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 Not ready
- No trips in this feed have a shape_id linked to a row in shapes.txt. Add shapes.txt with a shape_id for each trip's path, and set trips.shape_id to match. Reduced, Rural, and Tribal NTD reporters need this in their published GTFS starting Report Year 2026; Full Reporters needed it in Report Year 2025.
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 98 / 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 15 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/city-of-tracy/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.