Israel Ministry of Transport national GTFS

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

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

Stop time with arrival before previous departure time (flagged by the MobilityData validator).

See the linked rule for what this affects.

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

Finding code: stop_time_with_arrival_before_previous_departure_time · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

Location with unexpected stop time (flagged by the MobilityData validator).

See the linked rule for what this affects.

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

Finding code: location_with_unexpected_stop_time · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

Invalid phone number (flagged by the MobilityData validator).

See the linked rule for what this affects.

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

Finding code: invalid_phone_number · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

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

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

Missing required field (flagged by the MobilityData validator).

See the linked rule for what this affects.

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

Finding code: missing_required_field · See MobilityData GTFS Validator rules (opens the validator rules 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.)

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

Some scheduled trips move faster between stops than a transit vehicle can.

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

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

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

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

Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference 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 transit vehicle 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.)

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

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

Even with accessible stops, riders need to know the transit vehicle 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.)

Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference 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.)

Finding code: duplicate_route_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

959 of 420947 trips have no headsign, the text that tells riders where the transit vehicle is going.

When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)

Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)

Some service calendars have no days of the week switched on.

Trips tied to these calendars never run; they are dead data that can mask real schedule problems.

Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)

Finding code: service_has_no_active_day_of_the_week · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

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

Trip planners may draw the transit vehicle route through the wrong path or point riders to the wrong boarding location.

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

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

Unexpected enum value (flagged by the MobilityData validator).

See the linked rule for what this affects.

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

Finding code: unexpected_enum_value · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

On some trips the stops fall along the route line in a different order than the schedule lists.

Trip planners can draw the transit vehicle doubling back or skipping ahead, which confuses riders reading the map.

Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)

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

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

Finding code: trip_coverage_not_active_for_next7_days · 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 (the file itself is absent)

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

Finding code: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

This feed models stations or entrances but has no pathways.txt.

Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.

Fix: Add pathways.txt to link entrances, platforms, and elevators. Give each one a level. (Worth it for multi-level or large stations; flat stops don't need it.)

Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

Trip with shape dist traveled but no shape distances (flagged by the MobilityData validator).

See the linked rule for what this affects.

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

Finding code: trip_with_shape_dist_traveled_but_no_shape_distances · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

Unsorted stop times (flagged by the MobilityData validator).

See the linked rule for what this affects.

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

Finding code: unsorted_stop_times · 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.)

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

Future calendar (flagged by the MobilityData validator).

See the linked rule for what this affects.

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

Finding code: future_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

Unused station (flagged by the MobilityData validator).

See the linked rule for what this affects.

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

Finding code: unused_station · 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).

App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.

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

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