Monthly GTFS Quality Report
Amtrak
·
May 2024
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
06-06-2024
0.0
60
665
Technology Vendors
About the May 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 May 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 May 01 to May 31
Consistency with the California Transit Data Guidelines
The following checks measure adherence to the GTFS Compliance (Schedule) and GTFS Compliance (Realtime) portions 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. For agencies participating in a regional GTFS feed, such as the Bay Area 511 feed, the "No errors in MobilityData GTFS Schedule Validator" check may show a Fail if there are any validation errors present in the regional feed, even if the single-agency feed contains no errors. We believe this is unlikely to impact the rider experience.
| GTFS Schedule Compliance Check | 2024-05-04 | 2024-05-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* | | | |
| GTFS RT Compliance Check | 2024-05-04 | 2024-05-18 | |
| A Vehicle positions feed is listed | | | |
| A Trip updates feed is listed | | | |
| A Service alerts feed is listed | | | |
| Vehicle positions RT feed is present | | | |
| Trip updates RT feed is present | | | |
| Service alerts RT feed is present | | | |
| The Vehicle positions feed produces no errors in the MobilityData GTFS Realtime Validator | | | |
| The Trip updates feed produces no errors in the MobilityData GTFS Realtime Validator | | | |
| The Service alerts feed produces no errors in the MobilityData GTFS Realtime Validator | | | |
| Vehicle positions feed is published at a stable URI (permalink) from which it can be “fetched” automatically by trip-planning applications* | | | |
| Trip updates feed is published at a stable URI (permalink) from which it can be “fetched” automatically by trip-planning applications* | | | |
| Service alerts 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 Vehicle positions feed* | | | |
| Includes an open license that allows commercial use of Trip updates feed* | | | |
| Includes an open license that allows commercial use of Service alerts feed* | | | |
| Realtime feeds 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 | |
| stop_too_far_from_shape | Stop too far from trip shape. | WARNING | |
| missing_recommended_field | A recommended field is missing. | WARNING | |
| unused_shape | Shape is not used in GTFS file `trips.txt`. | WARNING | |
| same_stop_and_route_url | Same `stops.stop_url` and `routes.route_url`. | WARNING | |
| same_stop_and_agency_url | Same `stops.stop_url` and `agency.agency_url`. | WARNING | |
| same_route_and_agency_url | Same `routes.route_url` and `agency.agency_url`. | WARNING | |
| missing_recommended_column | A recommended column is missing in the input file. | WARNING | |
| feed_expiration_date7_days | Dataset should be valid for at least the next 7 days. | WARNING | |
| fast_travel_between_far_stops | A transit vehicle moves too fast between two far stops. | WARNING | |
| fast_travel_between_consecutive_stops | A transit vehicle moves too fast between two consecutive stops. | WARNING | |
| stop_time_timepoint_without_times | `arrival_time` or `departure_time` not specified for timepoint. | ERROR | |
| missing_feed_info_date | One of `feed_start_date` or `feed_end_date` is specified, but not both. | WARNING | |
| expired_calendar | Dataset should not contain date ranges for services that have already expired. | WARNING | |
| stops_match_shape_out_of_order | Two stop entries are different than their arrival-departure order defined by `shapes.txt`. | WARNING | |
| mixed_case_recommended_field | This field has customer-facing text and should use Mixed Case (should contain upper and lower case letters). | WARNING | |
| missing_feed_contact_email_and_url | Best Practices for `feed_info.txt` suggest providing at least one of `feed_contact_email` and `feed_contact_url`. | WARNING | |