Monthly GTFS Quality Report
City and County of San Francisco
·
August 2022
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
09-30-2022
0.0
64
3,273
Technology Vendors
In house activity
Trapeze Group
Cubic
About the August 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 August 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 August 01 to August 31
Consistency with the California Transit Data Guidelines
The following checks measure adherence to the GTFS Schedule Compliance portion 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.
| GTFS Schedule Compliance Check | 2022-08-04 | 2022-08-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* | | | |
| MobilityData GTFS Schedule Validator notices observed (read more about the validator here) | |||
| Error Name | Error Description | Severity | |
| unknown_file | A file is unknown. | INFO | |
| unused_shape | All records defined by GTFS shapes.txt should be used in trips.txt. | WARNING | |
| 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. | WARNING | |
| 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). | WARNING | |
| decreasing_or_equal_shape_distance | When sorted by shape.shape_pt_sequence, two consecutive shape points 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. | WARNING | |