Home
Directory
August 2022
Amtrak

Monthly GTFS Quality Report
Amtrak  ·  August 2022

This is a monthly report, generated by the California Integrated Travel Project (Cal-ITP), summarizing issues discovered by MobilityData’s GTFS Validator. 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

None
Feed End Date
0
Days With No Service
87
Routes
842
Stops
​
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.

About the August 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 August 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 August 01 to August 31

Consistency with the California GTFS Minimum Guidelines

Do the following files/fields exist? 2022-08-04 2022-08-18
Visual display shapes.txt ​ ​
Navigation levels.txt ​ ​
pathways.txt ​ ​
Fares fare_leg_rules.txt ​ ​
fare_rules.txt ​ ​
Technical contacts feed_info.txt ​ ​
Validation errors observed
Error Name Error Description Severity
unused_shape All records defined by GTFS shapes.txt should be used in trips.txt. 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_too_far_from_trip_shape Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. 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
stop_time_with_arrival_before_previous_departure_time For a given trip_id, the arrival_time of (n+1)-th stoptime in sequence must not precede the departure_time of n-th stoptime in sequence. ERROR
too_fast_travel As implemented in the original Google Python GTFS validator, the calculated speed between stops should not be greater than 150 km/h (42 m/s SI or 93 mph). WARNING