Greater Portland Metro Bus

Top things to fix

Score by category

Over time

Overall score across the last 20 checks — unchanged since 2026-07-08.

What changed since your last check

• Correctness— no change
• Freshness— no change
• Rider experience— no change

What changed in this feed

Overall grade and score held steady since 2026-07-08.

Same feed file as 2026-07-08; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

Everything we checked

• Error1 instance

  Service data ended 1160 day(s) ago.

  When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.

  Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)

  Agencies here usually clear this within about 1 week (based on 18 observed fixes).

  Validator rule: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)

• Warning3098 instances

  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)

• Warning2925 instances

  2925 of 2925 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 (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)

  Agencies here usually clear this within about 1 week (based on 5 observed fixes).

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

• Warning553 instances

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

• Warning261 instances

  Stop too far from shape using user distance (flagged by the MobilityData validator).

  See the linked rule for what this affects.

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

  Agencies here usually clear this within about 1 week (based on 6 observed fixes).

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

• Warning32 instances

  Leading or trailing whitespaces (flagged by the MobilityData validator).

  See the linked rule for what this affects.

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

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

• Warning10 instances

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

  Agencies here usually clear this within about 1 week (based on 11 observed fixes).

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

• Warning6 instances

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

  Agencies here usually clear this within about 1 week (based on 61 observed fixes).

  Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning4 instances

  Some trips serve fewer than two stops.

  A trip with one stop can't be ridden; planners ignore it and it may signal an export problem.

  Fix: Check the flagged trips in your scheduling software; remove them or restore their missing stops. (Worth a vendor question if it appears often.)

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

• Warning2 instances

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

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

• Warning1 instance

  This feed's service calendar runs out within the next 7 days.

  When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.

  Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)

  Agencies here usually clear this within about 1 week (based on 16 observed fixes).

  Validator rule: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning1 instance

  Missing feed contact email and url (flagged by the MobilityData validator).

  See the linked rule for what this affects.

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

  Agencies here usually clear this within about 1 week (based on 6 observed fixes).

  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)

• Warning1 instance

  Stops match shape out of order (flagged by the MobilityData validator).

  See the linked rule for what this affects.

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

  Agencies here usually clear this within about 1 week (based on 7 observed fixes).

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

• Warning1 instance

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

  Agencies here usually clear this within about 1 week (based on 31 observed fixes).

  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)

• Warning1 instance

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

  Validator rule: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning1 instance

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

  Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)

• Info548 instances

  About 548 stop names are written in ALL CAPS.

  Mixed-case names are easier to read in apps and are read more naturally by screen readers.

  Fix: Rename stops to mixed case (e.g. 'Main St & 2nd Ave'). (Often a bulk fix in your scheduling software.)

  Validator rule: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)

• Info3 instances

  Big gap in service (flagged by the MobilityData validator).

  See the linked rule for what this affects.

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

  Agencies here usually clear this within about 1 week (based on 13 observed fixes).

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

• Info1 instance

  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 with your feed, so problems linger.

  Fix: Add feed_contact_email to feed_info.txt. (One field.)

  Agencies here usually clear this within about 1 week (based on 10 observed fixes).

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

Beyond the grade

Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.

• 4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (5, 7, 9A, HSK).

  Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.

• 506 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("BUCKNAM RD + 8 BUCKNAM RD", "VERANDA ST + OLYMPIA ST", "SACO ST + PROSPECT ST", and more).

  Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

Some fixes we can make for you

These are the safe mechanical fixes, applied to a copy of your feed. They change only what is certain and leave everything else untouched. Review the diff before you publish.

• Recased shouting stop names 548 changes

  For example: BUCKNAM RD + 8 BUCKNAM RD -> Bucknam Rd + 8 Bucknam Rd

• Recased shouting route names 1 change

  For example: METRO BREEZ -> Metro Breez

Download corrected feed