City of Tracy (TRACER)

What changed since the last check

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

Top three things to fix

1. Correct feed_end_date in feed_info.txt. Set it to 2022-09-30, the last day in your calendar, or to the last day your schedule is reliable.

   feed_info.txt says this feed ends on 2022-07-31. Your service calendar runs to 2022-09-30. The GTFS standard tells apps to trust a feed only up to its end date. So apps may stop showing your service on the earlier date, even though the calendar goes on.

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

   Effort: One field in feed_info.txt, often an export setting.

2. Review the rule documentation for 'fare_transfer_rule_without_transfer_count' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Fare transfer rule without transfer count (flagged by the MobilityData validator). See the linked rule for what this affects.

   This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

   Effort: Varies.

3. Write every amount with the decimals its currency takes, and check that currency_type is the right ISO code.

   A fare amount has the wrong number of decimals for its currency. Apps may reject the amount or show a price off by a factor of ten. US dollars take two decimals, so 2.5 is wrong where 2.50 is meant.

   This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

   Effort: A quick edit of the fare file.

Ready to send to the agency

Hi City of Tracy (TRACER) team, feed_info.txt says this feed ends on 2022-07-31. Your service calendar runs to 2022-09-30. The GTFS standard tells apps to trust a feed only up to its end date. So apps may stop showing your service on the earlier date, even though the calendar goes on. The fix is usually one export setting: Correct feed_end_date in feed_info.txt. Set it to 2022-09-30, the last day in your calendar, or to the last day your schedule is reliable. Your feed is produced by Trillium, so the quickest path is usually forwarding this to your Trillium contact. This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/city-of-tracy-tracer/

Copy this note from the full scorecard.

NTD GTFS readiness: Not ready

Resolve this before you certify on the D-10. 5 validator errors to resolve. Service data expired 1553 days ago, so FTA would find the link out of date.

Published Ready

Published at a public URL.

Valid Needs attention

5 validator errors to resolve.

Current Not ready

Service data expired 1553 days ago, so FTA would find the link out of date.

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

The bar this score answers to

The published guideline in California is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.

Key facts

Feed URL

https://data.trilliumtransit.com/gtfs/tracy-ca-us/tracy-ca-us.zip

Last checked

2026-10-31

Service window

Feed has expired. Last service date 2022-09-30.

Feed version

UTC: 28-Sep-2021 20:17

Location

California