Monthly GTFS Quality Report
San Joaquin Regional Transit District
 · 
August 2022
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
01-28-2023
0.0
44
861
​
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 GTFS Minimum Guidelines
Do the following files/fields exist? | 2022-08-04 | 2022-08-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 | |
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 | |
duplicate_route_name | All routes should have different routes.route_long_name - if two routes.route_long_name are the same, and the two routes belong to the same agency, a notice is generated. | 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 |