Cal-ITP

Monthly GTFS Quality Report
Mammoth Lakes Transit System  ·  May 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

01-01-2023
Feed End Date
0
Days With No Service
14
Routes
195
Stops

Aggregated metrics for  May

  • Service hours per day in the active feed:

Changes from May 01 to May 31

  • Percentage of stop and route IDs that have changed since the previous month.
  • More than 5% being new or dropped is a cause for attention.

Consistency with the California GTFS Minimum Guidelines

Do the following files/fields exist? 2022-05-01 2022-05-15 2022-05-29
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
duplicate_fare_rule_zone_id_fields Each of the following fields should be unique in fare_rules.txt: fare_rules.route_id, fare_rules.origin_id, fare_rules.contains_id and fare_rules.destination_id ERROR
feed_expiration_date At any time, the published GTFS dataset should be valid for at least the next 7 days, and ideally for as long as the operator is confident that the schedule will continue to be operated. If possible, the GTFS dataset should cover at least the next 30 days of service. WARNING
stop_time_timepoint_without_times Any record with stop_times.timepoint set to 1 should define a value for stop_times.arrival_time and stop_times.departure_time fields. WARNING
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
Cal-ITP validation errors observed Number of errors
Error Name Error Description 2022-05-01 2022-05-15 2022-05-29
duplicate_fare_rule_zone_id_fields Each of the following fields should be unique in fare_rules.txt: fare_rules.route_id, fare_rules.origin_id, fare_rules.contains_id and fare_rules.destination_id 41 41 41
feed_expiration_date At any time, the published GTFS dataset should be valid for at least the next 7 days, and ideally for as long as the operator is confident that the schedule will continue to be operated. If possible, the GTFS dataset should cover at least the next 30 days of service. 1
stop_time_timepoint_without_times Any record with stop_times.timepoint set to 1 should define a value for stop_times.arrival_time and stop_times.departure_time fields. 216 6 6
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). 1 3 3