Cascais Próxima (MobiCascais)

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

1131 of 6049 trips have no headsign, the text that tells riders where the bus is going. A trip counts when it has trip_headsign or a stop_headsign at every stop.

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 for scorecard_missing_headsigns · See GTFS Best Practices (opens GTFS Best Practices on an external site)

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

The feed contains route shapes no trip uses.

Harmless to riders, but it bloats the feed and suggests stale export data.

Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)

Finding code: unused_shape · Read the fix guide for unused_shape · 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)

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 for expired_calendar · 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 for scorecard_station_no_pathways · See GTFS Schedule reference (opens the GTFS Schedule reference 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)

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)

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 for service_window_outside_feed_period · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

The feed includes a file that is not part of the GTFS spec.

Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.

Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)

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