Larnaka Public Transport (LPT)

Foreign key violation (flagged by the MobilityData validator).

See the linked rule for what this affects.

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

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

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

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

Same name and description for stop (flagged by the MobilityData validator).

See the linked rule for what this affects.

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

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

Two or more routes share the same name.

Riders can't tell the routes apart in apps.

Fix: Give each route a distinct short or long name. (One field per route.)

Validator rule: duplicate_route_name · 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)

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)

feed_info.txt is missing its start/end dates

Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.

Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)

Validator rule: scorecard_missing_feed_info_dates · 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)