Monthly GTFS Quality Report
Foothill Transit
·
April 2023
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
09-30-2023
0.0
39
1804
About the April 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 April 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 April 01 to April 30
Consistency with the California GTFS Minimum Guidelines
| Do the following files/fields exist? | 2023-04-04 | 2023-04-18 | |
|---|---|---|---|
| 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 | |
| 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 | |
| unused_shape | All records defined by GTFS shapes.txt should be used in trips.txt. | WARNING | |
| more_than_one_entity | The file is expected to have a single entity but has more (e.g., "feed_info.txt"). | 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 | |
| stop_too_far_from_shape | Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. | 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 | |
| same_name_and_description_for_stop | The GTFS spec defines stops.txt stop_description as:'Description of the location that provides useful, quality information. Do not simply duplicate the name of the location.' | WARNING | |
| 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 | |