Cal-ITP

Monthly GTFS Quality Report
Norwalk Transit System  ·  Jan 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.


Feed Published
20211231
Feed End Date
25
Days With No Service
17
Routes
259
Stops

Aggregated metrics for  Jan

  • Service hours per day in the active feed:

Changes from Jan 01 to Jan 31

  • Percentage of stop and route IDs that have changed since the previous month.
  • More than 5% being new or dropped is a cause for attention.

Consistency with the California GTFS Minimum Guidelines

Do the following files/fields exist? 2022-01-02 2022-01-16 2022-01-30
Visual display shapes.txt
Navigation levels.txt
pathways.txt
Fares fare_leg_rules.txt
fare_rules.txt
Technical contacts feed_info.txt
Cal-ITP validation errors observed Number of errors
Error Name Error Description 2022-01-02 2022-01-16 2022-01-30
decreasing_or_equal_shape_distance Two consecutive points in shapes.txt should have increasing values for shape_dist_traveled. If the values are equal, this is considered as an error. 830 830 830
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. If possible, the GTFS dataset should cover at least the next 30 days of service. 1 1 1
route_short_and_long_name_equal Short and long name should not be identical. 13 13 13
route_short_name_too_long Short name of a route is too long (more than 12 characters). Note that major trip planning applications start truncating short names after seven characters. 10 10 10
same_name_and_description_for_route The GTFS spec requires that a route_description is distinct from both the route short and long names. 17 17 17
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. 32 32 32
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). 266 266 266