Fix log: Centro
A dated record of every data issue this feed has cleared since tracking began. Each entry keeps its own link, so a specific fix can be cited in a board packet, a grant report, or an NTD narrative.
7 verified fixes
- Stops match shape out of order (flagged by the MobilityData validator). (stops_match_shape_out_of_order) Reported through 2026-07-05; the 2026-07-06 check verified it gone. Link
- Some stops sit far from the route line they belong to. (stop_too_far_from_shape) Reported through 2026-07-05; the 2026-07-06 check verified it gone. What this finding means. Link
- feed_info.txt is missing its start/end dates (the file itself is absent) (scorecard_missing_feed_info_dates) Reported through 2026-07-05; the 2026-07-06 check verified it gone. What this finding means. Link
- Missing timepoint value (flagged by the MobilityData validator). (missing_timepoint_value) Reported through 2026-07-05; the 2026-07-06 check verified it gone. What this finding means. Link
- A recommended GTFS file (usually feed_info.txt) is missing. (missing_recommended_file) Reported through 2026-07-05; the 2026-07-06 check verified it gone. What this finding means. Link
- Some scheduled trips travel implausibly fast between stops. (fast_travel_between_consecutive_stops) Reported through 2026-07-05; the 2026-07-06 check verified it gone. What this finding means. Link
- Two or more routes share the same name. (duplicate_route_name) Reported through 2026-07-05; the 2026-07-06 check verified it gone. Link
Verified means the daily check stopped reporting the finding. A finding that returns and clears again appears as a separate entry.
This log is the end of the guided fix loop: you make a change, republish, and the next run verifies it and records it here as linkable proof for a board packet or NTD narrative.