Kumamoto Bus (熊本バス)

A file is missing a column that GTFS requires.

Apps may reject the whole file, so riders could lose the affected routes or stops.

Fix: Add the required column named in the finding to the flagged file. (Often an export setting; ask your vendor if it recurs.)

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

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.)

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

1191 of 1191 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. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)

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

579 of 579 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)

Some rider-facing names are in ALL CAPS or all lowercase.

ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.

Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)

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

Some stops exist in the feed but no trip ever stops at them.

Riders may walk to a stop where no bus is scheduled to arrive.

Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)

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

feed_info.txt lists no contact email and no contact URL.

Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.

Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)

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)

Platform without parent station (flagged by the MobilityData validator).

See the linked rule for what this affects.

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

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

Some files contain columns that are not part of the GTFS spec.

Harmless to riders, but apps ignore these columns and they can hide typos in real column names.

Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)

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

Some trip headsigns name a stop along the way, not the final destination.

The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.

Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)

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

The feed includes a file that is not part of the GTFS spec.

Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.

Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)

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

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

Trip-planning apps and regional data coordinators 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.)

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