Monthly GTFS Quality Report
City and County of San Francisco
·
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
06-09-2023
5.0
68
3292
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 | |
| unknown_file | A file is unknown. | INFO | |
| unused_trip | Trips should be referred to at least once in stop_times.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 | |
| fast_travel_between_consecutive_stops | A transit vehicle moves too fast between two consecutive stops. The speed threshold depends on route type. | WARNING | |
| unusable_trip | A trip must visit more than one stop in stop_times.txt to be usable by passengers for boarding and alighting. | 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 | |
| feed_expiration_date7_days | The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days. | WARNING | |
| duplicate_fare_rule_zone_id_fields | The combination of fare_rules.route_id, fare_rules.origin_id, fare_rules.contains_id and fare_rules.destination_id fields should be unique in GTFS file fare_rules.txt. | ERROR | |
| feed_expiration_date30_days | At any time, the GTFS dataset should cover at least the next 30 days of service, and ideally for as long as the operator is confident that the schedule will continue to be operated. | WARNING | |