Monthly GTFS Quality Report
North County Transit District
·
October 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
None
0
45
1777
About the October 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 October 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 October 01 to October 31
Consistency with the California GTFS Minimum Guidelines
| Do the following files/fields exist? | 2022-10-04 | 2022-10-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_column | A column is unknown. | INFO | |
| 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 | |
| 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 | |
| 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 | |
| stop_without_zone_id | If fare_rules.txt is provided, and fare_rules.txt uses at least one column among origin_id, destination_id, and contains_id, then all stops and platforms (location_type = 0) must have stops.zone_id assigned. | ERROR | |
| equal_shape_distance_diff_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 different coordinates indicate an error. | ERROR | |
| 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 | |