Monthly GTFS Quality Report
City of Redondo Beach
·
February 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
None
1
2
209
About the February 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 February 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 February 01 to February 28
Consistency with the California GTFS Minimum Guidelines
| Do the following files/fields exist? | 2023-02-04 | 2023-02-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 | |
| duplicate_key | The values of the given key and rows are duplicates. | ERROR | |
| block_trips_with_overlapping_stop_times | Trips with the same block id have overlapping stop times. | ERROR | |
| leading_or_trailing_whitespaces | The value in CSV file has leading or trailing whitespaces. | 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 | |
| fast_travel_between_far_stops | A transit vehicle moves too fast between far consecutive stops (more than in 10 km apart). | 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 | |
| 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 | |
| stop_time_with_arrival_before_previous_departure_time | For a given trip_id, the arrival_time of (n+1)-th stoptime in sequence must not precede the departure_time of n-th stoptime in sequence in stop_times.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 | |
| 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 | |