Ondéa (Aix-les-Bains)

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)

Some route lines list the same point twice in a row.

Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.

Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)

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

Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).

See the linked rule for what this affects.

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

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

Some stops sit far from the route line, going by the feed's own distance values.

Trip planners may draw the route down the wrong streets or point riders to the wrong corner.

Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)

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

120 of 820 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference 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 for service_has_no_active_day_of_the_week · 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.)

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

5 of 2290 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference 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)

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

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

Some internal IDs use characters outside the basic text set.

These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.

Fix: Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language. (A planned ID change, not a quick text cleanup.)

Finding code: non_ascii_or_non_printable_char · 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 for trip_coverage_not_active_for_next7_days · 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 for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices 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.)

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

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 for big_gap_in_service · 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)

Future feed (flagged by the MobilityData validator).

See the linked rule for what this affects.

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

Finding code: future_feed · 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 for unknown_column · 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 for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)