GTFS Scorecard
← All agencies

Feed status · checked 2026-08-01

South Portland

Based on the feed this agency publishes

Service mode Bus

37.0 / 100

unchanged since 2026-07-31

Catalogued in Maine.

Feed expiredAccessibility gaps

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.3, validator 8.0.1.

Checked for changes 69 minutes ago; last changed 41 days ago.

Measured 4 of 4 score categories from the agency's own feed.

How we measured this

Confidence in this measurement: high.

  • All four score categories were measured this run.
  • Realtime was sampled in one bounded window of 6 snapshots.
  • The feed was downloaded from the agency's own URL.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

Top things to fix

Fix 01

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 300 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

Fix 02

Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.

The trip updates realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.

⏱ Usually a vendor support ticket.worth about +50 points in its category

Fix 03

Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.

The service alerts realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.

⏱ Usually a vendor support ticket.worth about +50 points in its category

This feed is exported from Remix. The change happens in your Remix workspace; once your planners update the data there, the published export picks it up.

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

  1. 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. This feed is exported from Remix. The change happens in your Remix workspace; once your planners update the data there, the published export picks it up.

    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.

  2. Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · Read the fix guide

    Make the change. This feed is exported from Remix. The change happens in your Remix workspace; once your planners update the data there, the published export picks it up.

    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.

  3. Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · Read the fix guide

    Make the change. This feed is exported from Remix. The change happens in your Remix workspace; once your planners update the data there, the published export picks it up.

    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 300 days ago.
Published accessibility data
Accessibility information is stated for 0.6% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information
Fare information is published using GTFS Fares v1.
Realtime information
No realtime feed was reachable during sampling.

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

This feed is exported from Remix. If your planners work in Remix, the change happens in your own workspace; otherwise forward this to whoever maintains your Remix data. Each fix names 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

Correctness72.5 / 100

The MobilityData validator flagged 7 kinds of issue across 469 instances (0 error, 145 warning, 324 informational).

Freshness0.0 / 100

Service data ended 300 day(s) ago. Trip planners have likely already dropped this feed.

Rider experience46.6 / 100

1% of stops state wheelchair accessibility (1% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.

Accessibility0.4 / 100

1% of stops state accessibility (1% marked accessible). Reflects what the feed states, not verified physical usability.

2 accessibility depth signals

  • 1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (24B).

    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.

  • 167 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("WESTERN AVE + LONG CREEK DRIVE", "COTTAGE RD + SOULE ST", "MAIN ST + COX 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.

FaresLegacy fares

Fares are applied to trips.

Realtime quality0.0 / 100

Sampled 6 times outside service hours: 0 of 2 configured feeds healthy.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

This feed has 169 stops.

Skip to route and stop data

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.

  • 21 (green)
  • 24A (red)
  • 24B (orange)
Routes in South Portland's feed
RouteTypeLine color
21 Willard SquareBusgreen
24A Maine Mall via Main StreetBusred
24B Maine Mall via Community CenterBusorange
List every stop
  • BROADWAY + LINTON
  • BROADWAY + Broadway
  • MAIN + RIDGELAND AVE
  • MAIN + SKILLINGS
  • MAIN ST + RIDGELAND AVE
  • MAINE MALL RD + Macys
  • MAINE MALL RD + J C Penney
  • MAINE MALL RD + IHOP
  • MAINE MALL RD + Goodwill
  • THOMAS ST + Millcreek Hub
  • BROADWAY + Broadway (Shelter)
  • CONGRESS ST + Monument Square
  • OCEAN ST + PARROT ST
  • OCEAN ST + DERBY RD
  • OCEAN ST + SAWYER ST
  • OCEAN ST + SIMMONS ST
  • OCEAN ST + STANLEY ST
  • CONGRESS ST + MONUMENT WY
  • PHILBROOK AVE + Hampton Inn
  • PILLSBURY ST + COTTAGE RD
  • BROADWAY + BURNHAM ST
  • PILLSBURY + LOWELL
  • PREBLE ST + FORT RD
  • PREBLE ST + FRANKLIN TER
  • PREBLE ST + STANFORD ST
  • PREBLE ST + PREBLE ST EXT
  • PREBLE ST + HIGH ST
  • WESTBROOK ST + Redbank
  • RUNNINGHILL RD + Fairchild
  • RUNNINGHILL RD + TARGET
  • RUNNINGHILL RD + SABLE OAKS DR
  • BROADWAY + BURNHAM
  • SAWYER + BROADWAY
  • SAWYER + Ferry Village
  • SAWYER ST + MARSH RD
  • SAWYER + MOSHER ST
  • SAWYER ST + CORMIER RD
  • SAWYER + STERLING
  • SAWYER + FRONT ST
  • SAWYER ST + MITCHELL RD
  • FORT RD + SMCC
  • SPRING ST + PAYNE RD
  • SPRING ST + 55 SPRING ST
  • SPRING ST + 25 SPRING ST
  • TEMPLE ST + FORE ST
  • TEMPLE ST + FREE ST
  • E ST + WATERMAN DR
  • WATERMAN DR + E ST
  • WESTBROOK ST + WESTCOTT RD
  • WESTBROOK ST + LOWER COACH RD
  • WESTBROOK ST + UPPER COACH RD
  • BROADWAY + ELM ST
  • WESTBROOK ST + WESTCOTT RD
  • WESTBROOK ST + Landry Village
  • WESTBROOK ST + Temple Beth Hamm
  • WESTBROOK ST + LOWER COACH RD
  • WESTBROOK ST + UPPER COACH RD
  • WESTERN AVE + LONG CREEK DRIVE
  • WESTERN AVE + Long Creek Medical Center
  • WESTERN AVE + Staples Plaza
  • WESTERN AVE + LONG CREEK DR
  • BROADWAY + ELM ST
  • WESTERN AVE + FODEN RD
  • PREBLE ST + Willard Square
  • YORK ST + PLEASANT ST
  • YORK ST + STATE ST
  • BRICKHILL AVE + Brickhill
  • BRICKHILL AVE + HERON COVE DR
  • BRICKHILL AVE + TOWNHOUSE DR
  • BROADWAY + EVANS ST
  • BROADWAY + Amato's
  • ANTHOINE + 36 ANTHOINE
  • HIGHLAND + CRESTVIEW
  • HIGHLAND + WINTERBERRY ST
  • HIGHLAND + Opp. SOUTH PORTLAND H.S.
  • P.S. FACILITY TP
  • BROADWAY + FELLOWS ST
  • HIGHLAND + MSW FACILITY RD
  • HIGHLAND + ALFRED ST
  • HIGHLAND + OPP WHISPERING PINES
  • HIGHLAND + WHISPERING PINES
  • OCEAN + D ST
  • OCEAN + D ST
  • OCEAN + A ST
  • OCEAN + A ST
  • WATERMAN + B ST
  • 425 BROADWAY
  • BROADWAY + LINCOLN ST
  • WATERMAN + B ST
  • WATERMAN + E ST
  • JOHN ROBERTS + PHILBROOK
  • BROADWAY + MUSSEY ST
  • BROADWAY + N KELSEY ST
  • BROADWAY + KENNETH ST
  • BROADWAY + ORLANDO ST
  • BROADWAY + PREBLE ST
  • BROADWAY + PRIDES ST
  • BROADWAY + SCAMMAN ST
  • BROADWAY + SO KELSEY ST
  • BROADWAY + STROUT ST
  • ANTHOINE ST + HAMILTON ST
  • BROADWAY + 740 BROADWAY
  • BROADWAY + Christian School
  • BROADWAY + KENNETH ST
  • BROADWAY + LINTON ST
  • BROADWAY + Mahoney Middle School
  • BROADWAY + 747 BROADWAY
  • BROADWAY + ANTHOINE
  • BROADWAY + ANTHOINE ST
  • BROADWAY + CLEMONS ST
  • BROADWAY + KELLY ST
  • ANTHOINE ST + OSBORNE AVE
  • BROADWAY + KELLEY ST
  • BROADWAY + LINCOLN ST
  • BROADWAY + STANFORD ST
  • BROADWAY + FELLOWS ST
  • BROADWAY + PRIDES ST
  • BROADWAY + STROUT ST
  • BROADWAY + Cash Corner
  • BROADWAY + Cash Corner
  • MAIN ST + Cash Corner
  • ANTHOINE ST + BROADWAY
  • MAIN ST + Cash Corner
  • EVANS ST + Community Center
  • CONGRESS ST + FOREST AVE
  • COTTAGE RD + SOULE ST
  • COTTAGE RD + HOMESTEAD AVE
  • EVANS ST + BONNYBRIER RD
  • EVANS ST + BONNYBRIER RD
  • EVANS ST + CUMBERLAND RD
  • EVANS ST + CUMBERLAND RD
  • ANTHOINE ST + COLUMBUS AVE
  • EVANS ST + HIGHLAND AVE
  • EVANS ST + Evans Community Center
  • FODEN RD + DARLING AVE
  • FODEN RD + WESTERN AVE
  • 1001 GALLERY BLVD
  • GALLERY BLVD + Lowes
  • GALLERY BLVD + Gallery Road Walmart
  • GANNETT DR
  • 295 GANNETT DR
  • 207 GANNETT DR
  • ANTHOINE ST + HAMILTON ST
  • 119 GANNETT DR
  • PHILLBROOK AVE + Hannafords Store
  • HIGH ST + SPRING ST
  • HIGHLAND AVE + South Portland High School
  • HIGHLAND AVE + Lighthouse Day School
  • HIGHLAND AVE + T-LEDGE DR
  • HIGHLAND AVE + Nazarine Church
  • HIGHLAND AVE + T-Ledge Condos
  • KALER RD + SPURWINK AVE
  • BENJAMAN PICKETT ST + ADAMS ST
  • LINCOLN ST + CHAPMAN ST
  • LINCOLN ST + BODGE ST
  • LINCOLN ST + CHURCH ST
  • LINCOLN ST
  • LINCOLN + 390 LINCOLN ST
  • LINCOLN ST + CHAPMAN ST
  • MAIN ST + COX ST
  • MAIN ST + SKILLINGS ST
  • BROADWAY + BENJAMAN PICKETT ST
  • MAIN ST + FROSWICK AVE
  • MAIN + WILSON
  • MAIN ST + MARDALE AVE
  • MAIN ST + MARDALE AVE
  • MAIN ST + WESTBROOK ST
  • MAIN ST + WESTBROOK ST
  • MAIN ST + ALTON ST

Over time

Overall score across the last 4 checks — unchanged since 2026-07-31.

2026-07-25: 37.02026-07-30: 37.02026-07-31: 37.02026-08-01: 37.0
Show the numbers
CheckScoreChange
2026-07-2537.0 first check
2026-07-3037.0 no change
2026-07-3137.0 no change
2026-08-0137.0 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change
  • Realtime quality 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

14 findings, ordered by severity.

Show every finding
  • Error1 instance

    Service data ended 300 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

  • Error1 instance

    The trip updates realtime feed failed during sampling.

    When this feed is down, riders see scheduled times presented as if they were live.

    Fix: Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)

    Finding code: scorecard_rt_trip_updates_unreachable · Read the fix guide · See GTFS-Realtime reference

  • Error1 instance

    The service alerts realtime feed failed during sampling.

    When this feed is down, riders see scheduled times presented as if they were live.

    Fix: Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)

    Finding code: scorecard_rt_service_alerts_unreachable · Read the fix guide · See GTFS-Realtime reference

  • Warning322 instances

    322 of 322 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

  • Warning168 instances

    168 of 169 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

  • Warning135 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

  • Warning34 instances

    34 of 322 trips lack rider-facing destination or direction text.

    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 · See GTFS Best Practices

  • 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

  • Warning2 instances

    Some scheduled trips move faster between stops than a bus can.

    Usually a typo'd stop time; riders get arrival times no bus can meet.

    Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)

    Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules

  • 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

  • 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

  • Info322 instances

    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

  • Info135 instances

    About 135 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

  • Info2 instances

    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 · See MobilityData GTFS Validator rules

NTD GTFS readiness Not ready

Resolve this before you certify on the D-10. Service data expired 300 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 300 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 322 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 300 days ago. States wheelchair access on 1% 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 300 days ago.
Accessible Not yet
States wheelchair access on 1% 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.

Realtime reliability

The realtime feed responded on 0.0% of 200 checks over the last 34 days, with lag not reported by the feed.

Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.

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 72 / 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 47 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality 0 / 100
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.

South Portland GTFS data quality grade: F

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/south-portland-2641/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.