← Home

The most common GTFS problems.

Across 1661 comparable feed records, these are the problems most feeds share. Each one is common, which means each fix helps a lot of riders at once.

Most common problems

The six most widespread problemsShare of comparison-eligible feed records carrying each problem.
  1. Stops missing wheelchair boarding information94.9%1576 feed records
  2. Trips missing wheelchair accessibility information88.4%1469 feed records
  3. Non-standard columns54.3%902 feed records
  4. Mixed case recommended field54.1%898 feed records
  5. No feed contact51.3%852 feed records
  6. No fare data42%697 feed records

What each problem means and how to fix it

Plain-language coverage

Of the 113 distinct problem codes seen in the covered corpus, 52 carry vetted plain-language text: 46.0% of codes and 90.2% of all finding instances. Codes without curated text fall back to a generic line that links to the validator's rule documentation.

Next up for curation, ranked by how often riders' data actually hits each problem:

Notice codeInstancesFeed records
unsorted_stop_times102130570
duplicate_key62519920
trip_with_shape_dist_traveled_but_no_shape_distances32958916
missing_bike_allowance15873555
foreign_key_violation15071423
equal_shape_distance_diff_coordinates_distance_below_threshold8829996
trip_distance_exceeds_shape_distance7189341
equal_shape_distance_diff_coordinates5371210
block_trips_with_overlapping_stop_times4257831
platform_without_parent_station31948157

In plain words: most feeds trip on the same handful of things, and most of those are one export setting. If you run an agency, scanning this list is a fast way to find a fix that probably applies to you too.

The directory contains 2493 published feed records. Prevalence uses 1661 canonical, non-duplicate records under rubric 1.5, scoring profile gtfs-scorecard-1.5, MobilityData gtfs-validator 8.0.1, reader archive profile raw-v1, and measured categories Correctness, Freshness, Rider experience. It never changes a grade. The same data is at the problems API (problems.json).