De Lijn

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

25052 of 30309 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)

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

See the linked rule for what this affects.

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

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

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

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)

Between two distant stops, the times imply a speed no transit vehicle reaches.

A rider gets a trip plan that cannot happen. Live systems then report delays that are not real.

Fix: Check the two stop times for a wrong digit first. Then check whether a stop sits at the wrong coordinates, or a stop between them is missing. (Minutes per flagged trip once you open it.)

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

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)

The feed contains no fare information.

Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)

Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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)

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

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

Some service dates fall outside the date window set in feed_info.txt.

feed_info.txt should span every day your service runs, so apps know when the data applies.

Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)

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

The feed has a stretch of two weeks or more with no service running.

A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.

Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)

Finding code: big_gap_in_service · 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 transit vehicle 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.)

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