Home
Directory
June 2022
Antelope Valley Transit Authority

Monthly GTFS Quality Report
Antelope Valley Transit Authority  ·  June 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

05-31-2022
Feed End Date
2
Days With No Service
22
Routes
883
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 June 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 June 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 June 01 to June 30

Consistency with the California GTFS Minimum Guidelines

Do the following files/fields exist? 2022-06-04 2022-06-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
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