Cal-ITP

Monthly GTFS Quality Report
MTC 511  ·  November 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

None
Feed End Date
0
Days With No Service
656
Routes
21943
Stops
  • This feed appears to be missing feed_info.txt.
  • Including feed info is important to help data users easily find technical contacts.
  • Please reach out to our help desk at [email protected] with any questions.

About the November 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 November 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 November 01 to November 30

Consistency with the California GTFS Minimum Guidelines

Do the following files/fields exist? 2021-11-07 2021-11-21
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
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. ERROR
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. 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
invalid_url A field contains a malformed URL. ERROR
more_than_one_entity A file that is expected to have only one row has more than one row. WARNING
number_out_of_range The values in the given column of the input rows are out of range. ERROR
route_short_and_long_name_equal Short and long name should not be identical. WARNING
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. 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