Monthly GTFS Quality Report
San Diego Metropolitan Transit System  ·  January 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
Feed End Date
0
Days With No Service
109
Routes
4461
Stops
Has RT Feed
This feed includes GTFS-Realtime (GTFS-RT). Realtime data contributes to a better rider experience by letting riders know exactly when their bus or train is coming, as well as detour and trip cancellation info. It also enables Cal-ITP to support transit agencies with analyses such as our California Transit Speed Maps, viewable by clicking the button above. Certain feeds may include RT data but not have a speed map available. To generate a speed map, we require GTFS-RT Vehicle Positions data that matches the rest of the GTFS feed. Additionally, we don't currently generate speed maps for rail service. Please contact us at [email protected] with any questions about GTFS-RT data or suggestions for analysis products.

About the January 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 January 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 January 01 to January 31


Consistency with the California GTFS Minimum Guidelines

Do the following files/fields exist? 2023-01-04 2023-01-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
unknown_column A column is unknown. INFO
duplicate_key The values of the given key and rows are duplicates. ERROR
missing_required_field The given field has no value in some input row, even though values are required. ERROR
missing_recommended_field The given field has no value in some input row, even though values are recommended. WARNING
invalid_row_length A row in the input file has a different number of values than specified by the CSV header. ERROR
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
invalid_currency_amount A currency amount field has a value that does not match the format (e.g. expected number of decimal places) of its corresponding currency code field. The number of decimal places is specified by ISO 4217. ERROR
fare_transfer_rule_missing_transfer_count A row from GTFS file fare_transfer_rules.txt has from_leg_group_id equal to to_leg_group_id, but has no transfer_count specified. Per the spec, transfer_count is required if the two leg group ids are equal. 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