HDPT

Top things to fix

Score by category

Over time

Overall score across the last 20 checks — unchanged since 2026-07-08.

What changed since your last check

• Correctness— no change
• Freshness— no change
• Rider experience— no change

What changed in this feed

Overall grade and score held steady since 2026-07-08.

Same feed file as 2026-07-08; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

Everything we checked

• Error1 instance

  Service data ended 1888 day(s) ago.

  When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.

  Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)

  Agencies here usually clear this within about 1 week (based on 18 observed fixes).

  Validator rule: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)

• Warning9138 instances

  9138 of 9138 trips don't say whether the vehicle is wheelchair accessible.

  Even with accessible stops, riders need to know the bus itself can take them.

  Fix: Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)

  Agencies here usually clear this within about 1 week (based on 5 observed fixes).

  Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

• Warning279 instances

  279 of 279 stops don't say whether a wheelchair user can board there.

  Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

  Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)

  Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

• Warning46 instances

  Same stop and route url (flagged by the MobilityData validator).

  See the linked rule for what this affects.

  Fix: Review the rule documentation for 'same_stop_and_route_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

  Validator rule: same_stop_and_route_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning32 instances

  Stops match shape out of order (flagged by the MobilityData validator).

  See the linked rule for what this affects.

  Fix: Review the rule documentation for 'stops_match_shape_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

  Agencies here usually clear this within about 1 week (based on 7 observed fixes).

  Validator rule: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning27 instances

  Some service calendars in the feed have already ended.

  Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.

  Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)

  Agencies here usually clear this within about 1 week (based on 61 observed fixes).

  Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning11 instances

  Some stops sit far from the route line they belong to.

  Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.

  Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)

  Agencies here usually clear this within about 2 weeks (based on 6 observed fixes).

  Validator rule: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning10 instances

  Route long name contains short name (flagged by the MobilityData validator).

  See the linked rule for what this affects.

  Fix: Review the rule documentation for 'route_long_name_contains_short_name' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

  Validator rule: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning9 instances

  Some scheduled trips move faster between stops than a bus can.

  Usually a typo'd stop time; riders get arrival times no bus can meet.

  Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)

  Agencies here usually clear this within about 2 weeks (based on 6 observed fixes).

  Validator rule: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning2 instances

  Route short name too long (flagged by the MobilityData validator).

  See the linked rule for what this affects.

  Fix: Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

  Validator rule: route_short_name_too_long · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning1 instance

  This feed's service calendar runs out within the next 7 days.

  When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.

  Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)

  Agencies here usually clear this within about 1 week (based on 16 observed fixes).

  Validator rule: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning1 instance

  Missing feed contact email and url (flagged by the MobilityData validator).

  See the linked rule for what this affects.

  Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

  Agencies here usually clear this within about 1 week (based on 6 observed fixes).

  Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning1 instance

  Some files leave out fields that GTFS asks for but does not require.

  Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.

  Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)

  Agencies here usually clear this within about 2 weeks (based on 8 observed fixes).

  Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning1 instance

  Some route colors don't contrast with their text color.

  Route badges get hard to read, most of all for riders with low vision.

  Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)

  Validator rule: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning1 instance

  Many of the feed's trips don't run at all in the next 7 days.

  It usually means old service periods are still in the export, making the feed bigger and harder to check.

  Fix: Trim past service periods the next time you export. (One setting in most export tools.)

  Agencies here usually clear this within about 1 week (based on 31 observed fixes).

  Validator rule: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning1 instance

  Some trips serve fewer than two stops.

  A trip with one stop can't be ridden; planners ignore it and it may signal an export problem.

  Fix: Check the flagged trips in your scheduling software; remove them or restore their missing stops. (Worth a vendor question if it appears often.)

  Validator rule: unusable_trip · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning1 instance

  Unused trip (flagged by the MobilityData validator).

  See the linked rule for what this affects.

  Fix: Review the rule documentation for 'unused_trip' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

  Validator rule: unused_trip · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Info1 instance

  feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

  App makers and state data programs have nobody to email when they spot a problem with your feed, so problems linger.

  Fix: Add feed_contact_email to feed_info.txt. (One field.)

  Agencies here usually clear this within about 1 week (based on 10 observed fixes).

  Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

Beyond the grade

Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.

• 26 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 3, 4, 5, 18, and more).

  Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.

• 252 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("E Bruce St & Hardesty Higgins House (sh)", "E Mkt St & Cloverleaf Shopping Ctr (sh)", "Carrier Dr & Festival (shelter)", and more).

  Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.