Réseau urbain Calibus

Some trips have stop times whose distances along the route go backwards.

Apps can show buses jumping backwards or mis-order stops.

Fix: Re-generate shape distances in your export; flag to your vendor if it persists. (Usually an export-tool fix, not hand editing.)

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

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

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

28 of 651 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)

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 route long names repeat the route's short name inside them.

Apps show both names together, so riders see the number twice, like '5 5 Downtown'.

Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)

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

A file GTFS asks for (usually feed_info.txt) is missing.

feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.

Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)

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

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

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

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)

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 connecting entrances, platforms, and any elevators, with a level for each. (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)

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

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