Cal-ITP

Monthly GTFS Quality Report
Union City Transit  ·  Apr 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.


Feed Published
20221231
Feed End Date
0
Days With No Service
5
Routes
159
Stops

Aggregated metrics for  Apr

  • Service hours per day in the active feed:

Changes from Apr 01 to Apr 30

  • 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-04-03 2022-04-17
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
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
route_short_and_long_name_equal Short and long name should not be identical. WARNING
same_name_and_description_for_route The GTFS spec requires that a route_description is distinct from both the route short and long names. ERROR
Cal-ITP validation errors observed Number of errors
Error Name Error Description 2022-04-03 2022-04-17
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. 6
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
route_short_and_long_name_equal Short and long name should not be identical. 5
same_name_and_description_for_route The GTFS spec requires that a route_description is distinct from both the route short and long names. 4