Feed status · checked 2026-08-01
Greater Portland Metro Bus
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Maine.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.2, validator 8.0.1.
Checked for changes 9 hours ago; last changed 9 days ago.
Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: provisional.
- Realtime quality was not measured this run. It does not count against the grade.
- The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 1183 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.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
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.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
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.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- Service data ended 1183 day(s) ago.
- Next action
- Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- 553 of 553 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- 2925 of 2925 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date was 1183 days ago.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- No fare information is published in the feed.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 13 kinds of issue across 3421 instances (0 error, 3418 warning, 3 informational).
Service data ended 1183 day(s) ago. Trip planners have likely already dropped this feed.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
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.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 553 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 1 (teal)
- 2 (yellow)
- 3 (white)
- 4 (gray)
- 5 (green)
- 7 (red)
- 8 (pink)
- 9A (orange)
- 9B (green)
- BRZ (teal)
- HSK (teal)
| Route | Type | Line color |
|---|---|---|
| 1 Congress Street | Bus | teal |
| 2 Riverton | Bus | yellow |
| 3 Route 3 | Bus | white |
| 4 Westbrook | Bus | gray |
| 5 Maine Mall | Bus | green |
| 7 Falmouth | Bus | red |
| 8 Peninsula Loop | Bus | pink |
| 999 Test Route | Bus | white (no shape in feed) |
| 9A North Deering via Stevens Ave | Bus | orange |
| 9B North Deering via Washington Ave | Bus | green |
| BRZ METRO BREEZ | Bus | teal |
| HSK Husky Line | Bus | teal |
List every stop
- BUCKNAM RD + 8 BUCKNAM RD
- BRIGHTON AVE + 416 BRIGHTON AVE
- FORESIDE RD + MUSSEL COVE LN
- BARRON CENTER O/B
- FOREST AVE + BELMONT ST
- FOREST AVE + 1837 FOREST AVE
- PORTLAND ST + FOREST AVE
- BLUEBERRY LN + WHIPPLE FARM LN
- WESTBROOK HANNAFORD
- FOREST AVE + NEWTON ST
- MECHANIC ST + WEST VALENTINE ST
- RSVP
- ROUTE 1 + ROUTE 88
- WASHINGTON AVE + 1133 WASHINGTON AVE
- FOREST AVE + AVALON ST
- MIDDLE ST + FRANKLIN ST
- WASHINGTON AVE + 1751 WASHINGTON AVE
- LUNT RD + COMMUNITY CENTER
- FORESIDE RD + MEADOW CREEK LN
- WASHINGTON AVE + CANCO RD
- WASHINGTON AVE + VERANDA ST
- FOREST AVE + RIVERSIDE INDUSTRIAL PWKY
- ROUTE 1 + 183 ROUTE 1
- STEVENS AVE + 716 STEVENS AVE
- STEVENS AVE + 500 STEVENS AVE
- ROUTE 1 + PHILLIPS RD
- CONGRESS ST + FOREST AVE
- WASHINGTON AVE + CHURCHILL ST
- BEDFORD ST USM I/B
- FOREST AVE + PARK AVE
- BRIGHTON AVE + STEVENS AVE
- ROSEMONT CORNER O/B
- BRIGHTON MEDICAL CTR O/B
- DANFORTH ST + SCHOOL ST
- MAIN ST + 800 MAIN ST
- WASHINGTON AVE + CONGRESS ST
- QUIMBY AVE + SACO ST
- WASHINGTON AVE + SANBORN ST
- FOREST AVE + WILLIAM ST
- BRIGHTON AVE + PITT ST
- STEVENS AVE + RACKLEFF ST
- CONGRESS ST + CENTER ST
- CONGRESS ST + HOBART ST
- FORESIDE RD + 154 FORESIDE RD
- WASHINGTON AVE + BREWSTER ST
- DEPOT RD + 33 DEPOT RD
- MAIN ST + 140 MAIN ST
- JOHNSON RD + TIME WARNER CABLE
- INDIA ST + 65 INDIA ST
- BRIDGE ST + DANA CT
- WASHINGTON AVE + STONECREST DR
- WASHINGTON AVE + MUGWHY
- CONGRESS ST + CASCO ST
- CONGRESS ST + WEYMOUTH ST
- WESTBROOK CITY HALL
- FOREST AVE + BEDFORD ST
- WASHINGTON AVE + OCEAN AVE
- AUBURN ST + GARSOE DR
- FALMOUTH WALMART I/B
- FOREST AVE + DARTMOUTH ST
- HARNOIS AVE + MAIN ST
- WASHINGTON AVE + E. PROMENADE
- AUBURN ST + 92 AUBURN ST
- MAIN ST + DUNN ST
- FOREST AVE + ARLINGTON ST
- FODEN RD + WESTERN AVE
- CONGRESS ST + PARK ST
- FOREST AVE + FALMOUTH ST
- CONGRESS ST + VALLEY ST
- CONGRESS ST + SHERIDAN ST
- WASHINGTON AVE + RAY ST
- BRIGHTON AVE + CAPISIC ST I/B
- MAIN ST + 250 MAIN ST
- PARK AVE + WEYMOUTH ST
- SAGAMORE VILLAGE O/B
- IDEXX
- WILLIAM CLARKE DR + CENTRAL ST
- MAIN ST + 668 MAIN ST
- GRAY RD + 25 GRAY RD
- FORE RIVER PARKWAY + FEDERIC ST
- MORRILL'S CORNER
- WASHINGTON AVE + RIVERSIDE DR
- WASHINGTON AVE + FOX ST
- BRIGHTON AVE + BEACON ST
- CONGRESS ST + HAMPSHIRE ST
- CONGRESS ST + WEYMOUTH ST
- BUCKNAM RD + 4 BUCKNAM RD
- FOREST AVE + LINCOLN ST
- INTERNATIONAL PKWY + CONGRESS ST
- FOREST AVE + POLAND ST
- ROCK ROW
- WASHINGTON AVE + EASTERN PROMENADE
- CONGRESS ST + 690 CONGRESS ST
- WASHINGTON AVE + REGAN LN
- VERANDA ST + KENSINGTON ST
- BRACKETT ST + SPRING ST
- ROUTE 1 + 196 ROUTE 1
- AUBURN ST + LONGVIEW ST
- ST JOHN ST + 70 ST JOHN ST
- SACO ST + 345 SACO ST
- BRIDGE ST + CUMBERLAND ST
- AUBURN ST + LYSETH MOORE ST
- BAXTER BLVD + 43 BAXTER BLVD
- WEST ST + CARLETON ST
- CONGRESS ST + 181 CONGRESS ST
- STEVENS AVE + BRIGHTON AVE
- BRIGHTON AVE + CAPISIC ST O/B
- FOREST AVE + HIGH ST
- ST JOHN ST + 117 ST JOHN ST
- CONGRESS ST + FREDERIC ST
- BRIGHTON AVE + ROWE AVE
- MYRTLE ST + BRIDGE ST
- MARGINAL WAY + FRANKLIN ST
- NORTH ST + QUEBEC ST
- EASTERN PROMENADE + WALNUT ST
- AUBURN ST + RUSTIC ST
- ROUTE 1 + ANDREWS AVE
- WASHINGTON AVE + MAINE AVE
- ROUTE 1 + 64 ROUTE 1
- MYRTLE ST + PRINCE ST
- ROUTE 1 + NORTHBROOK DR
- NORTH ST + CUMBERLAND AVE
- MAINE MEDICAL CENTER
- FOREST AVE + READ ST
- EAST END SCHOOL
- WASHINGTON AVE + OAKLEY ST
- FOREST AVE + CONGRESS ST
- CONGRESS ST + FROST ST
- CONGRESS ST + FOREST AVE
- MAIN ST + HASKELL ST
- FORESIDE RD + OLD POWERHOUSE RD
- BROWN ST + BRIDGE ST
- MAIN ST + SCHOOL ST
- MECHANIC ST + PROSPECT ST
- EMERY ST + SPRUCE ST
- WASHINGTON AVE + GREENWOOD LN
- MAIN ST + MASON ST
- MYRTLE ST + BRIDGE ST
- WASHINGTON AVE + LAMBERT ST
- TD BANK FALMOUTH
- MAIN ST + LIZA HARMON DR
- EASTERN PROMENADE + VESPER ST
- AUBURN ST + CROQUET LN
- FOREST AVE + MORRILL ST
- MAIN ST + RIVERSIDE ST
- CONGRESS ST + FRANKLIN ST
- PULSE
- MIDDLE RD + FALMOUTH RD
- FODEN RD + DARLING AVE
- CONGRESS ST + 1945 CONGRESS ST
- WASHINGTON AVE + SUMMITT ST
- EASTERN PROMENADE + CONGRESS ST
- WASHINGTON AVE + HARVARD ST
- STEVENS AVE + PROSPECT ST
- WOODFORD O/B
- WASHINGTON AVE + GREENWOOD LN
- MARGINAL WAY + 87 MARGINAL WAY
- MOTHERHOUSE I/B
- FOREST AVE + PLEASANT ST
- WASHINGTON AVE + JOHANSEN ST
- MIDDLE ST + 188 MIDDLE ST
- BRIGHTON AVE + MACHIGONNE ST
- HAT TRICK DR + DEPOT RD
- WASHINGTON AVE + RIVERSIDE ST
- BRIDGE ST + FALMOUTH ST
- BEDFORD ST USM O/B
- STEVENS AVE + POLAND ST
- AUBURN ST + HILLSIDE ST
- MYRTLE ST + PRINCE ST
- CONGRESS ST + WALDO ST
- OXFORD ST + ALDER ST
- CONGRESS ST + 1717 CONGRESS ST
- MAIN ST + LOCUST ST
- CONGRESS ST + WHITNEY ST
- CONGRESS ST + INTERNATIONAL PKWY
- VERANDA ST + FAIRFIELD ST
- FORESIDE RD + RICKER RD
- FOREST AVE + WALTON ST
- CONGRESS ST + 1189 CONGRESS ST
- JETPORT ACCESS RD + JOHNSON RD
- STEVENS AVE + PERCIVAL ST
- FORESIDE RD + APPLEGATE LN
- MAIN ST + 458 MAIN ST
- FORESIDE RD + 266 FORESIDE RD
- FOREST AVE + PLEASANT ST
- CONGRESS ST + DEERING AVE
- FOREST AVE + 1037 FOREST AVE
- FOREST AVE + HARTLEY ST
- EASTERN PROMENADE + TURNER ST
- CONGRESS ST + HUTCHINS DR
- TEMPLE ST + FEDERAL ST
- PORTLAND EXPO/HADLOCK FIELD
- JOHNSON RD + 94 JOHNSON RD
- DEERING HS OUTBOUND
- STEVENS AVE + ARBOR ST
- CONGRESS ST + GARRISON ST
- STEVENS AVE + PLEASANT AVE
- ELM ST + LANCASTER ST
- STEVENS AVE + TWIN KNOLLS LN
- MAIN ST + TRAMWAY LN
- FOREST AVE + KENNEBEC ST
- MAIN ST + 380 MAIN ST
- PARK AVE + HIGH ST
- CASCO BAY LINES
- MYRTLE ST + BROWN ST
- VERANDA ST + HAWTHORNE ST
- STEVENS AVE + ELMWOOD ST
- PROSPECT ST + SACO ST
- FRANKLIN TOWERS
- VERANDA ST + SHERWOOD ST
- WASHINGTON AVE + W. KIDDER ST
- WESTERN AVE + 371 WESTERN AVE
- MAIN ST + 741 MAIN ST
- VERANDA ST + MARINE HOSPITAL RD
- FOREST AVE + BAILEY ST
- WASHINGTON AVE + W. PRESUMPSCOT ST WEST
- PREBLE ST + CUMBERLAND AVE
- FORESIDE RD + 213 FORESIDE RD
- WESTBROOK ST + 1025 WESTBROOK ST
- MAIN ST + STROUDWATER ST
- ROSEMONT CORNER I/B
- PREBLE ST + LANCASTER ST
- FOREST AVE + HARTLEY ST
- AUBURN ST + BARTLEY ST
- AUBURN ST + JACKSON ST
- MOTHERHOUSE O/B
- VERANDA ST + SHERWOOD ST
- ROUTE 1 + GILSLAND FARM RD
- STEVENS AVE + 825 STEVENS AVE
- FOREST AVE + WALTON ST
- CONGRESS ST + INDIA ST
- BRIGHTON AVE + 460 BRIGHTON AVE
- CONGRESS ST + VALLEY ST
- ROUTE 1 + WINSLOW RD
- MARGINAL WAY + 161 MARGINAL WAY
- PARK AVE + GILMAN ST
- CONGRESS ST + UNUM WEST
- WASHINGTON AVE + 1364 WASHINGTON AVE
- FOREST AVE + ALLEN AVE
- WASHINGTON AVE + BERNARD RD
- WESTBROOK ST + 1050 WESTBROOK ST
- MAINE MALL JC PENNEY
- BACK COVE HANNAFORD
- ALLEN AVE + 50 ALLEN AVE
- UNUM I/B
- JOHNSON RD + VALLEY AVE
- BRIGHTON AVE + KENWOOD ST
- ROUTE 1 + FORESIDE COMMON RD
- AUBURN ST + 206 AUBURN ST
- PTC O/B
- and 303 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 5 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-16 | 23.5 | first check |
| 2026-07-25 | 23.5 | no change |
| 2026-07-30 | 23.5 | no change |
| 2026-07-31 | 23.5 | no change |
| 2026-08-01 | 23.5 | no change |
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-31.
Same feed file as 2026-07-31; 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
19 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 1183 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.)
Finding code: 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.)
Finding code: 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. 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)
- 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.)
Finding code: 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.)
Finding code: 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.)
Finding code: 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.)
Finding code: 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.)
Finding code: 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.)
Finding code: 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.)
Finding code: 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.)
Finding code: 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.)
Finding code: 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.)
Finding code: 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.)
Finding code: 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.)
Finding code: 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.)
Finding code: 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 where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: 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.)
Finding code: big_gap_in_service · Read the fix guide · 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).
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)
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. Service data expired 1183 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- Service data expired 1183 days ago, so FTA would find the link out of date.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
- agency_id equals your NTD ID (optional) Not checked yet
- This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
- shapes.txt covers your trips Ready
- All 2925 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed is close to the conformance mark. Service data expired 1183 days ago. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 1183 days ago.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 4 of 2925 trips list fewer than two stops. A trip with one stop has no leg a rider can ride; trip planners can't route anyone on it, so the service effectively does not exist. Check your scheduling export: every trip should list each stop it calls at, in order, with times.
- 10 of 553 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
- Correctness 38 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
- Freshness 0 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
- Rider experience 23 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/greater-portland-metro-bus/2026-08-01.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-08-01. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.