← All agencies

Feed status · checked 2026-10-31

City of Tracy

Based on the feed source on file; publisher ownership is not verified

Service mode Bus

FDCBA

80.5 / 100

unchanged since 2026-10-30

Cataloged in California.

Covers 62 daysAccessibility gapsFlexible service

Source feed: https://data.trilliumtransit.com/gtfs/tracy-ca-us/tracy-ca-us--flex-v2.zip

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.4, validator 8.0.1.

Checked for changes 80 minutes ago; last changed 128 days ago.

Measured 4 of 4 score categories from the feed URL on file (publisher not verified).

How we measured this

Confidence in this measurement: high.

All four score categories were measured this run.
Realtime was sampled in one bounded window of 9 snapshots.
The feed was downloaded from the configured feed URL. Publisher ownership of that URL is not verified.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

About this feed

City of Tracy’s published feed lists 2 bus routes and 7 scheduled trips. Its service dates run from 2026-06-24 through 2027-01-01. It publishes realtime trip updates, vehicle positions and service alerts; when we checked, all of them answered. The published file last changed on 2026-06-24.

Top things to fix

Fix 01

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.

Fixing this covers all 7 trips in the feed.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Fix 02

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 have no headsign, the text that tells riders where the bus is going. A trip counts when it has trip_headsign or a stop_headsign at every stop. When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

Fixing this covers all 7 trips in the feed.

⏱ Usually one value per route pattern in your scheduling source.worth about +15 points in its category

Fix 03

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.

The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

This one is about the feed as a whole, so there is no share of it to count.

⏱ A small file for most flat-fare systems.worth about +15 points in its category

Riders and need behind these fixes

This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
California as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-10-26.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

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.

Finding: Fix 01 in Top things to fix: its feed evidence and the requested change.
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

Agency: City of Tracy
Finding: scorecard_wheelchair_accessible_unknown
Feed evidence: 7 of 7 trips don't say whether the vehicle is wheelchair accessible.
Why it matters: Even with accessible stops, riders need to know the bus itself can take them.
Requested change: 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.
Evidence: https://gtfsscorecard.org/agency/city-of-tracy/?finding=scorecard_wheelchair_accessible_unknown#finding-handoff

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.

Fix 01 · Read the fix guide for scorecard_wheelchair_accessible_unknown
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. See this feed's finding-clearance log.
Fix 02 · Read the fix guide for scorecard_missing_headsigns
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. See this feed's finding-clearance log.
Fix 03 · Read the fix guide for scorecard_no_fare_data
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. See this feed's finding-clearance log.

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 62 days.
Published accessibility data: Accessibility information is stated for 0% of trips; Stop coverage is not known. This measures published data, not whether stops or vehicles are physically usable.
Fare information: No fare information is published in the feed.
Realtime information: One or more realtime feeds were reachable; live-arrival coverage is not known.

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.

Hi,

Our GTFS feed (City of Tracy) scored B (80.5 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
   What: 7 of 7 trips don't say whether the vehicle is wheelchair accessible.
   Finding code: scorecard_wheelchair_accessible_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_accessible_unknown/

2. 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.
   What: 7 of 7 trips have no headsign, the text that tells riders where the bus is going. A trip counts when it has trip_headsign or a stop_headsign at every stop.
   Finding code: scorecard_missing_headsigns
   Guide: https://gtfsscorecard.org/fix/scorecard_missing_headsigns/

3. 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.
   What: The feed contains no fare information.
   Finding code: scorecard_no_fare_data
   Guide: https://gtfsscorecard.org/fix/scorecard_no_fare_data/

Full scorecard: https://gtfsscorecard.org/agency/city-of-tracy/

Score by category

Correctness98.0 / 100

The MobilityData validator flagged 3 kinds of issue across 32 instances (0 error, 0 warning, 32 informational).

Freshness100.0 / 100

Service data covers the next 62 days.

Rider experience25.0 / 100

This feed has no stops to state wheelchair accessibility for. Fare data is not published.

Accessibility0 / 100

States accessibility, not verified physical usability.

Realtime quality100.0 / 100

Sampled 9 times outside service hours: 3 of 3 configured feeds healthy; vehicle position plausibility was not measurable.

Routes and stops

This feed has no located stops.

Routes in City of Tracy's feed
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 30 checks — unchanged since 2026-10-30.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-10-02	80.5	first check
2026-10-03	80.5	no change
2026-10-04	80.5	no change
2026-10-05	80.5	no change
2026-10-06	80.5	no change
2026-10-07	80.5	no change
2026-10-08	80.5	no change
2026-10-09	80.5	no change
2026-10-10	80.5	no change
2026-10-11	80.5	no change
2026-10-12	80.5	no change
2026-10-13	80.5	no change
2026-10-14	80.5	no change
2026-10-15	80.5	no change
2026-10-16	80.5	no change
2026-10-17	80.5	no change
2026-10-18	80.5	no change
2026-10-19	80.5	no change
2026-10-20	80.5	no change
2026-10-21	80.5	no change
2026-10-22	80.5	no change
2026-10-23	80.5	no change
2026-10-24	80.5	no change
2026-10-25	80.5	no change
2026-10-26	80.5	no change
2026-10-27	80.5	no change
2026-10-28	80.5	no change
2026-10-29	80.5	no change
2026-10-30	80.5	no change
2026-10-31	80.5	no change

What changed since your last check

Correctness no change
Freshness no change
Rider experience no change
Realtime quality no change

Feed history

Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.

Feed history by published file
Checked	Published file	Service dates through	Grade at the time
2026-10-02 to 2026-10-31 (30 checks)	`5fa5aa624a3c`	2027-01-01	Current rubric: see the trend above
2026-07-25 to 2026-10-01 (65 checks)	`5fa5aa624a3c`	2027-01-01	B, 80.5 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-14 to 2026-07-24 (9 checks)	`5fa5aa624a3c`	2027-01-01	C, 72.6 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade
2026-06-24 to 2026-07-13 (20 checks)	`5fa5aa624a3c`	2027-01-01	C, 72.6 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade
2026-06-16 to 2026-06-23 (6 checks)	`9609edd05cf6`	2026-07-01	F, 49.1 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade

What changed in this feed

Overall grade and score held steady since 2026-10-30.

Same feed file as 2026-10-30; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.

Everything we checked

7 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning7 instances
7 of 7 trips have no headsign, the text that tells riders where the bus is going. A trip counts when it has trip_headsign or a stop_headsign at every stop.
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 for scorecard_missing_headsigns · 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 for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices 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 for unknown_column · 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 for unknown_file · 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 for service_window_outside_feed_period · 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

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 62 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

One requirement remains for this feed to earn the conformance mark. Accessibility completeness has not been measured.

Valid Met: Passes validation with no errors.
Current Met: Service data covers the next 62 days.
Accessible Not yet: Accessibility completeness has not been measured.

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.

Realtime reliability

The realtime feed responded on 100.0% of 200 checks in the 25 days to 2026-10-30, with 21s median lag.

Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment. The window ends at the newest observation, which is not always today: if the monitor stops, this window stops with it.

Clears the Google and Apple Maps four-week coverage bar. This feed has 62 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.

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 (3 of 5 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.
Meets Designate a technical contact in feed_info.txt's feed_contact_email
feed_info.txt states a technical contact.
Not measured here wheelchair_boarding stated on stops and trips
Accessibility completeness has not been measured.
Gap shapes.txt with a shape for every trip
No trips in this feed have a shape_id linked to a row in shapes.txt.
Gap Fare data published, or the service marked fare-free
No fare data is published.

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 25 / 100: GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality 100 / 100: GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Part of the California portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in California

Other scorecards in California, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

Badge HTML

<a href="https://gtfsscorecard.org/agency/city-of-tracy/"><img src="https://gtfsscorecard.org/agency/city-of-tracy/badge.svg" width="320" height="58" alt="City of Tracy: current GTFS data quality score from GTFS Scorecard"></a>

Badge Markdown

[![City of Tracy: current GTFS data quality score from GTFS Scorecard](https://gtfsscorecard.org/agency/city-of-tracy/badge.svg)](https://gtfsscorecard.org/agency/city-of-tracy/)

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-10-31.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-10-31. 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.

GTFS Scorecard. (2026). City of Tracy GTFS feed-quality record, dated 2026-10-31 (grade B (80.5/100), rubric v1.4, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 5fa5aa624a3c…). https://gtfsscorecard.org/data/artifacts/city-of-tracy/2026-10-31.json

@misc{gtfsscorecard-city-of-tracy-2026-10-31,
  title        = {City of Tracy GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/city-of-tracy/2026-10-31.json}},
  note         = {Checked 2026-10-31; rubric v1.4; gtfs-validator 8.0.1; reader archive profile raw-v1; grade B (80.5/100)}
}

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.