Monthly GTFS Quality Report
Placer County
 · 
April 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
09-04-2023
5.0
8
152
​
About the April 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 April 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 April 01 to April 30
Consistency with the California GTFS Minimum Guidelines
Do the following files/fields exist? | 2023-04-04 | 2023-04-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 | |
foreign_key_violation | A foreign key references the primary key of another file. A foreign key violation means that the foreign key referenced from a given row (the child file) cannot be found in the corresponding file (the parent file). The Foreign keys are defined in the specification under "Type" for each file. | ERROR | |
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 | |
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 | |
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 |