Monthly GTFS Quality Report
Amtrak  ·  March 2023

This is a monthly report generated by the California Integrated Travel Project (Cal-ITP) and Caltrans. It summarizes progress towards the California Transit Data Guidelines, in addition to providing a snapshot of transit service characteristics such as service hours. This report is available for viewing by the general public to support continuous improvement of GTFS data and the experience of transit passengers.

Current GTFS Feed Info

Feed End Date
Days With No Service
No RT Feed
This feed doesn't seem to include GTFS-Realtime (GTFS-RT). Realtime data contributes to a better rider experience by letting riders know exactly when their bus or train is coming, as well as detour and trip cancellation info. It also enables Cal-ITP to support transit agencies with useful analysis tools. Please contact us at [email protected] for guidance on how to offer a GTFS-RT feed, or let us know if you're already publishing one that we aren't aware of.

Source URLs

Note: Links may lead directly to downloads and/or to resources that require authentication

Technology Vendors

No vendor information available

About the March Daily Service Level Charts

  • These charts show the total hours of transit service described by the active feed for each day.
  • Since service levels often vary by the day of the week, it is split into three charts for weekdays, Saturdays, and Sundays.
  • Flat lines indicate consistent levels of service throughout the month.
  • Short drops may indicate temporary reduced service, such as for holidays, gaps in feed publishing, or potential inaccuracies.
  • Please reach out to our help desk at [email protected] with any questions.

Service hours per weekday in the active feed

Service hours per Saturday in the active feed

Service hours per Sunday in the active feed

About the March Identifier Change Charts

  • These charts show the percentage of stop and route IDs that have changed since the previous month.
  • Stop and route IDs are important identifiers for GTFS feed consumers to correctly parse feeds.
  • It is a GTFS Best Practice to keep these consistent between feed versions whenever possible.
  • More than 5% being new or dropped is a cause for attention, especially if there hasn't been a major service or route change.
  • Please reach out to our help desk at [email protected] with any questions.

Changes from March 01 to March 31

Consistency with the California Transit Data Guidelines

The following checks measure adherence to the GTFS Schedule Compliance portion of the California Transit Data Guidelines.

The following symbols are used to denote each check's outcome on the given date:

  • Pass
  • Fail
  • Not applicable/data unavailable

Checks marked with an asterisk (*) are periodically performed manually. We can update these on request, so let us know if one of them looks off.

GTFS Schedule Compliance Check 2023-03-04 2023-03-18
A GTFS Schedule feed is listed
GTFS schedule feed downloads successfully
No errors in MobilityData GTFS Schedule Validator
GTFS Schedule feed is published at a stable URI (permalink) from which it can be “fetched” automatically by trip-planning applications*
Includes an open license that allows commercial use of GTFS Schedule feed*
GTFS Schedule feed ingested by Google Maps and/or a combination of Apple Maps, Transit App, Bing Maps, Moovit or local Open Trip Planner services*
MobilityData GTFS Schedule Validator notices observed (read more about the validator here)
Error Name Error Description Severity
missing_timepoint_column The timepoint column should be provided. WARNING
unused_shape All records defined by GTFS shapes.txt should be used in trips.txt. WARNING
same_stop_and_route_url A stop should not have the same stop.stop_url as a record from routes.txt. WARNING
same_stop_and_agency_url A stop should not have the same stops.stop_url as a record from agency.txt. WARNING
same_route_and_agency_url A route should not have the same routes.route_url as a record from agency.txt. WARNING
missing_recommended_field The given field has no value in some input row, even though values are recommended. WARNING
fast_travel_between_far_stops A transit vehicle moves too fast between far consecutive stops (more than in 10 km apart). WARNING
stop_without_stop_time A stop in stops.txt is not referenced by any stop_times.stop_id, so it is not used by any trip. WARNING
fast_travel_between_consecutive_stops A transit vehicle moves too fast between two consecutive stops. The speed threshold depends on route type. WARNING
unusable_trip A trip must visit more than one stop in stop_times.txt to be usable by passengers for boarding and alighting. WARNING
stop_has_too_many_matches_for_shape A stop entry that has many potential matches to the trip's path of travel, as defined by the shape entry in shapes.txt. WARNING
stop_too_far_from_shape Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. WARNING
stops_match_shape_out_of_order Two stop entries in stop_times.txt are different than their arrival-departure order as defined by the shape in the shapes.txt file. WARNING
missing_feed_info_date Even though feed_info.start_date and feed_info.end_date are optional, if one field is provided the second one should also be provided. WARNING