Monthly GTFS Quality Report
MTC 511  ·  Oct 2021

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

Feed End Date
Days With No Service

Aggregated metrics for  Oct

  • Service hours per day in the active feed:

Changes from Oct 01 to Oct 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? 2021-10-03 2021-10-17 2021-10-31
Visual display shapes.txt
Navigation levels.txt
Fares fare_leg_rules.txt
Technical contacts feed_info.txt
Cal-ITP validation errors observed Number of errors
Error Name Error Description 2021-10-03 2021-10-17 2021-10-31
decreasing_or_equal_shape_distance Two consecutive points in shapes.txt should have increasing values for shape_dist_traveled. If the values are equal, this is considered as an error. 5624 5504 4754
decreasing_or_equal_stop_time_distance Two consecutive stop times in a trip should have increasing distance. If the values are equal, this is considered as an error. 113 113 113
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 3 4
invalid_url A field contains a malformed URL. 2 2 2
more_than_one_entity A file that is expected to have only one row has more than one row. 1 1 1
number_out_of_range The values in the given column of the input rows are out of range. 1 1 1
route_short_and_long_name_equal Short and long name should not be identical. 7 7 7
route_short_name_too_long Short name of a route is too long (more than 12 characters). Note that major trip planning applications start truncating short names after seven characters. 16 16 16
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. 158 194 194