Monthly GTFS Quality Report
City of Ojai  ·  July 2023

This is a monthly report generated by the California Integrated Travel Project (Cal-ITP) and Caltrans. It summarizes progress towards the California Transit Data Guidelines, in addition to providing a snapshot of transit service characteristics such as service hours. 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.0
Days With No Service
66
Routes
1,310
Stops
Has RT Feed
This feed includes GTFS-Realtime (GTFS-RT). Realtime data contributes to a better rider experience by letting riders know exactly when their bus or train is coming, as well as detour and trip cancellation info. It also enables Cal-ITP to support transit agencies with analyses such as our California Transit Speed Maps, viewable by clicking the button below. Certain feeds may include RT data but not have a speed map available. To generate a speed map, we require GTFS-RT Vehicle Positions data that matches the rest of the GTFS feed. Additionally, we don't currently generate speed maps for rail service. Please contact us at [email protected] with any questions about GTFS-RT data or suggestions for analysis products.

About the Realtime Completeness Charts

  • These charts show the percentage of Scheduled Trips with at least one Trip Update or Vehicle Position message assigned to that trip.
  • High percentages with flat lines are best and indicate large amounts of realtime information for customers.
  • Short drops may indicate schedule inaccuracies, missed runs (buses not on schedule), or hardware failures.

Trip Updates Completeness by Day

Vehicle Positions Completeness by Day

About the Median Message Age Charts

  • These charts show the daily average age of the median message for Trip Updates and Vehicle Position messages over time.
  • The charts provides insights into how long it takes to get messages from the vehicles to riders. Lower latencies are better.
  • Higher latencies may indicate outdated hardware or technical failures.

Median Trip Update Message Age

Median Vehicle Positions Message Age

Source URLs

Note: Links may lead directly to downloads and/or to resources that require authentication


Technology Vendors

Microsoft
GTFS Static
GMV Syncromatics Inc
Realtime

About the July 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 July 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 July 01 to July 31


Consistency with the California Transit Data Guidelines

The following checks measure adherence to the GTFS Compliance (Schedule) and GTFS Compliance (Realtime) portions of the California Transit Data Guidelines.

The following symbols are used to denote each check's outcome on the given date:

  • Pass
  • Fail
  • Not applicable/data unavailable

Checks marked with an asterisk (*) are periodically performed manually. We can update these on request, so let us know if one of them looks off. For agencies participating in a regional GTFS feed, such as the Bay Area 511 feed, the "No errors in MobilityData GTFS Schedule Validator" check may show a Fail if there are any validation errors present in the regional feed, even if the single-agency feed contains no errors. We believe this is unlikely to impact the rider experience.

GTFS Schedule Compliance Check 2023-07-04 2023-07-18
A GTFS Schedule feed is listed
GTFS schedule feed downloads successfully
No errors in MobilityData GTFS Schedule Validator
GTFS Schedule feed is published at a stable URI (permalink) from which it can be “fetched” automatically by trip-planning applications*
Includes an open license that allows commercial use of GTFS Schedule feed*
GTFS Schedule feed ingested by Google Maps and/or a combination of Apple Maps, Transit App, Bing Maps, Moovit or local Open Trip Planner services*
GTFS RT Compliance Check 2023-07-04 2023-07-18
A Vehicle positions feed is listed
A Trip updates feed is listed
A Service alerts feed is listed
Vehicle positions RT feed is present
Trip updates RT feed is present
Service alerts RT feed is present
The Vehicle positions feed produces no errors in the MobilityData GTFS Realtime Validator
The Trip updates feed produces no errors in the MobilityData GTFS Realtime Validator
The Service alerts feed produces no errors in the MobilityData GTFS Realtime Validator
Vehicle positions feed is published at a stable URI (permalink) from which it can be “fetched” automatically by trip-planning applications*
Trip updates feed is published at a stable URI (permalink) from which it can be “fetched” automatically by trip-planning applications*
Service alerts feed is published at a stable URI (permalink) from which it can be “fetched” automatically by trip-planning applications*
Includes an open license that allows commercial use of Vehicle positions feed*
Includes an open license that allows commercial use of Trip updates feed*
Includes an open license that allows commercial use of Service alerts feed*
Realtime feeds ingested by Google Maps and/or a combination of Apple Maps, Transit App, Bing Maps, Moovit or local Open Trip Planner services*
MobilityData GTFS Schedule Validator notices observed (read more about the validator here)
Error Name Error Description Severity
unknown_file A file is unknown. INFO
leading_or_trailing_whitespaces The value in CSV file has leading or trailing whitespaces. WARNING
route_color_contrast A route's color and route_text_color should be contrasting. WARNING
route_short_name_too_long Short name of a route is too long (more than 12 characters). WARNING
route_short_and_long_name_equal A single route has the same values for route_short_name and route_long_name. WARNING
missing_recommended_field The given field has no value in some input row, even though values are recommended. WARNING
stop_without_stop_time A stop in stops.txt is not referenced by any stop_times.stop_id, so it is not used by any trip. WARNING
fast_travel_between_consecutive_stops A transit vehicle moves too fast between two consecutive stops. The speed threshold depends on route type. WARNING
stops_match_shape_out_of_order Two stop entries in stop_times.txt are different than their arrival-departure order as defined by the shape in the shapes.txt file. WARNING
stop_too_far_from_shape_using_user_distance A stop time entry that is a large distance away from the location of the shape in shapes.txt as defined by shape_dist_traveled values. WARNING
missing_feed_info_date Even though feed_info.start_date and feed_info.end_date are optional, if one field is provided the second one should also be provided. WARNING
same_name_and_description_for_route The GTFS spec defines routes.txt route_desc as: 'Description of a route that provides useful, quality information. Do not simply duplicate the name of the route.' WARNING
decreasing_or_equal_stop_time_distance When sorted by stop_times.stop_sequence, two consecutive entries in stop_times.txt should have increasing distance, based on the field shape_dist_traveled. If the values are equal, this is considered as an error. ERROR
equal_shape_distance_diff_coordinates When sorted by shape.shape_pt_sequence, the values for shape_dist_traveled must increase along a shape. Two consecutive points with equal values for shape_dist_traveled and different coordinates indicate an error. ERROR
equal_shape_distance_same_coordinates When sorted by shape.shape_pt_sequence, the values for shape_dist_traveled must increase along a shape. Two consecutive points with equal values for shape_dist_traveled and the same coordinates indicate a duplicative shape point. WARNING