Cal-ITP

Monthly GTFS Quality Report
Marin Transit  ·  Dec 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

03-12-2022
Feed End Date
0
Days With No Service
27
Routes
550
Stops

Aggregated metrics for  Dec

  • Service hours per day in the active feed:

Changes from Dec 01 to Dec 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-12-05 2021-12-19
Visual display shapes.txt
Navigation levels.txt
pathways.txt
Fares fare_leg_rules.txt
fare_rules.txt
Technical contacts feed_info.txt
Cal-ITP validation errors observed Number of errors
Error Name Error Description 2021-12-05 2021-12-19
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. 17 15
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 111
duplicate_route_name All routes of the same route_type with the same agency_id should have unique combinations of route_short_name and route_long_name. 2 2
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_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. 2 2
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). 92 92