Réseau urbain Eveole

Block trips with overlapping stop times (flagged by the MobilityData validator).

See the linked rule for what this affects.

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

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

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

Missing required agency id (flagged by the MobilityData validator).

See the linked rule for what this affects.

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

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

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

30 of 7216 trips have no headsign.

Riders at the stop can't tell which direction a bus is going.

Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)

Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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.)

Validator rule: mixed_case_recommended_field · 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 bus route through the wrong streets or point riders to the wrong corner.

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

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

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

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)

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

Validator rule: route_color_contrast · Read the fix guide · 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.)

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

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

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

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