Feed status · checked 2026-08-01
Biddeford Saco Old Orchard Beach Transit
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.3, validator 8.0.1.
Checked for changes 81 minutes ago; last changed 41 days ago.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- 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
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
254 of 259 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 +24 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
812 of 1252 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 +10 points in its category
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool
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.
⏱ Often a bulk fix in your scheduling software.worth about +8 points in its category
Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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
- 254 of 259 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
- 812 of 1252 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
- Feed evidence
- Some rider-facing names are in ALL CAPS or all lowercase.
- Next action
- Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
- 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.
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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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 is in 152 days.
- Published accessibility data
- Accessibility information is stated for 1.9% of stops and 35.1% 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
- 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 Trillium a fix request
This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 5 kinds of issue across 1919 instances (0 error, 660 warning, 1259 informational).
Service data covers the next 152 days.
2% of stops state wheelchair accessibility (2% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
2% of stops state accessibility (2% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (60, 50, 54, 81, 83).
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.
157 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Imperial & Milliken", "311 Main St", "Oregon Ave", 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.
Fares are applied to trips.
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 259 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.
- 50 (orange)
- 51 (black)
- 52 (yellow)
- 53 (teal)
- 54 (gray)
- 60 (brown)
- 70 (purple)
- 80 (pink)
- 81 (purple)
- 82 (teal)
- 83 (red)
| Route | Type | Line color |
|---|---|---|
| 50 Orange / Biddeford Crossing | Bus | orange |
| 51 Black / Biddeford Crossing | Bus | black |
| 52 White / Saco Industrial Park - OOB | Bus | yellow |
| 53 Blue / OOB - Saco Industrial | Bus | teal |
| 54 Silver | Bus | gray |
| 60 Green / Saco - Portland | Bus | brown |
| 70 Zoom Express | Bus | purple |
| 80 Saco | Bus | pink |
| 81 Pine Point | Bus | purple |
| 82 OOB | Bus | teal |
| 83 Camp Ellis | Bus | red |
List every stop
- 485 Main St.
- Main St & King St
- 439 Route 1
- 442 Route 1 - Tractor Supply
- 655 Route 1 - Martin's Point
- 17 Thornton Ave
- Medical Center Dr & Rte 111
- Birch St & Alfred St
- Graham St & Emmons Pl
- 189 Alfred Rd - Martin Community Center
- Congress St & Forest Ave
- Congress St + Center St
- Philbrook Ave and Hampton Inn
- Congress St + Bramhall St
- Congress St & Casco St
- Congress St & Deering St
- Congress St & Weymouth St
- Congress St & Weymouth - MMC
- Southern Maine Medical Center
- 200 Route 1 - The Cheese Iron
- UNE Alfond Forum
- Saco Ave & Pleasantwood Dr
- Saco Transportation Center
- 209 Main St
- Seaglass Terrace & Cascade Rd
- 14 Thornton Ave
- 89 Temple Ave
- Shaw's Saco
- Scammon St/Reny's
- 33 North St
- Elm St & Mason St
- Main St & Smith St
- 517 Main St - Dairy Queen
- 21 Ocean Park Rd - Classic Inn
- Cumberland Ave
- MIlliken Heights - Portland Ave
- Saco Ave - Fielders Choice
- 168 Saco Ave - Birdies Tavern
- Oregon Ave
- Ocean Park Cottages
- Ocean Park Rd/Log Cabin
- Elks Lodge
- Ocean Park & Olive St
- Exit 5 Motel
- 524 Main St - McDonald's
- Main St & Hutchins St
- Main St & Fairfield St
- North St/Elm St Intersection
- Spring St/North St
- 244 Main St - Pharmacy
- 190 Main St
- Alfred & Franklin
- Biddeford Post Office
- Portland Glass/Birch Street
- West Myrtle St
- Elm St & Orchard St
- Hannaford - Biddeford
- Walgreens - Alfred Crosswalk
- 5 Points Shopping Center
- 3 Pomerleau St - YMCA
- Barra Rd / Medical Offices
- Maine Behavioral Health
- Fernandez Building
- Dialysis Building
- Shops at Biddeford Crossing Crosswalk
- Target
- Market Basket / Biddeford Crossing
- Pet Smart/Staples
- Shops Way
- New Life Church
- Walmart
- Mountain Road
- Fiber Materials
- 545 Elm St
- PeoplesChoice Credit Union
- Beacon Ave
- Mason St & Elm St
- 219 Elm St
- 275 Main Street
- Biddeford City Hall
- 105 Main St (Happy Dragon)
- Main St - Mechanics Park
- Elm St & Cutts St
- 232 Elm St - Papa Johns
- 364 Elm St - RepubliCash
- Exit 32 Park & Ride
- Alex Pizza
- Alfred St - Police Station
- North Dam Mill
- Main St & York St
- Lincoln & Pearl St (Parking Garage)
- Elm St & Gooch St
- Elm St & Pleasant St
- North St & Nott St
- North St / Roebuck ave
- North St & Village Green Dr
- 15 Industrial Park Rd.
- Pendleton Drive
- 77 Industrial Park Rd
- 91 Industrial Park Rd
- Industrial Park - Pond
- Biddeford Industrial Park
- 1015 Blue Haven Motor Court
- Waterfall Drive
- Old Blue Point Road
- Orchard St
- 594 Route 1 - Subway
- Holy Donut
- Ready Seafood
- 774 Portland Rd - Funtown Splashtown
- 636 Main St
- 292 Main St
- North St & Vernon St
- Dyer Library
- Main St & Thornton Academy
- Temple Ave/Lee Nail Salon
- Goodwin Ave
- The Pines
- Free St
- West Grand Ave
- Odessa Ave - Northbound
- Union Ave & West Grand Ave
- Chamber of Commerce
- School St
- Saco Ave & Grove Ave
- Brookside Motel
- 4 Cascade Rd
- Rte 1 & Old Blue Point Rd
- Enterprise Drive
- Technology Way - NB
- Passage Way
- Scarborough Downs Shelter
- Portland Farms Rd & Rte 1
- 100 Campus Drive
- 800 Main Street / SP City Line
- 762 Main Street South Portland
- 100 Foden Rd
- Foden Rd/Western Ave
- Western Ave/ Harbor Freight
- Portland City Hall
- Portland Public Library
- Congress St & Park St
- 745 Main Street South Portland
- Tiiton Apt/Volvo
- Pat's Pizza/Florist
- Bangor Savings Bank
- Maine Health
- Irving Gas Station
- Pool St & Foss St
- Oak St
- Simard St
- Meeting House Rd
- UNE Campus Center
- Forest Ave + Bedford St
- Rte 1 & Commerce Dr
- Old Orchard Beach Chamber
- The Brunswick
- Bayview Road
- Camp Ellis @ Seaside Ave
- Pinehurst RV Resort
- OOB Campground
- Sun Retreats Campground
- Jimmy the Greeks Restaurant
- Elmwood Motor Court
- Wild Acres RV Resort & Campground
- Corner Imperial St and Milliken St
- Alouette Beach Resort
- Friendship Suites
- Royal Anchor
- Stern Restaurant
- Bait Shed
- Clam Bake
- Bayleys Campground
- Cascade Plaza
- Sun Outdoors OOB
- Powderhorn Campground
- KOA Campground
- Funtown/Splashtown USA
- Wagon Wheel Motel
- Silver Springs Campground
- 577 Route 1 - Southgate Apts
- Rte 1 & Hillcrest
- Rte 1 & Sunset
- 96 Campus Drive
- 92 Campus Drive
- Campus Dr & Research Dr
- Campus Dr & Research Dr
- Mercy at the Fore
- St John St
- Ready Seafood Lot
- 102 Industrial Park Road
- 775 Portland Rd
- Maine Mall
- Exit 36 Park & Ride
- 435 Elm Street (Marden's)
- York Co. Courthouse
- 479 Elm St
- High Street
- Saco Transportation Center
- Saco Transportation Center
- Wellspring Road
- Pool St - St. Andre
- Pool St & Meeting House Rd
- 73 Pool St
- Technology Way - SB
- Scarborough Downs & Mill Commons
- Saco Ave & Wildwood
- Main & Washington
- Saco Ave & Myrtle Ave
- SMHC & W Cole Rd
- Comfort Inn - Saco
- Imperial & Milliken
- Saco Ave Walgreens
- 17 Spring Hill Rd
- 16 Spring Hill Rd
- Holiday House
- Grand Beach Inn
- McArthur Library
- Lincoln St & Stone St
- 260 Maine Highway 1
- 137 Pool Street
- 235 Pool Street
- 22 Industrial Park Road
- Temple Ave & Williams St
- 55 Saco Ave
- OOB Firehouse - Saco Ave
- Omni Inn - Saco Ave
- 311 Main St
- 218 North St
- North St & Tasker St - Young School
- 72 Industrial Park Rd
- 92 Industrial Park Rd
- Main St & Ross Rd
- Ocean Park & Hodgeman Ave
- North St & Union St
- Cascade Rd & Rte 1
- 110 Main St
- Elm St & Water St
- Pool St & Sokokis Rd
- Pool St & Columbus Way
- 180 Pool St
- Clifford Park - Pool St
- Elm St & Beacon Ave
- Elm St & Union St
- Elm St & Main St
- Cascade Rd & ET - Northbound
- Cascade Rd & ET - Southbound
- Marcotte Motel
- Huot's Seafood Restaurant
- 246 U.S. Route 1 / Rosemont Bakery
- and 9 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 79.4 | first check |
| 2026-07-30 | 79.4 | no change |
| 2026-07-31 | 79.4 | no change |
| 2026-08-01 | 79.4 | 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
8 findings, ordered by severity.
Show every finding
- Warning812 instances
812 of 1252 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)
- Warning533 instances
533 of 1252 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 (opens GTFS Best Practices on an external site)
- Warning366 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)
- Warning294 instances
On some trips the stop distances run a little past the end of the route line.
The stop and shape distance values don't quite line up, so any math that uses them can drift.
Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning254 instances
254 of 259 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)
- Info1252 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 (opens the validator rules on an external site)
- Info5 instances
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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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 (opens the validator rules on an external site)
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 152 days.
- 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 1252 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. States wheelchair access on 2% of stops and 35% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 152 days.
- Accessible Not yet
- States wheelchair access on 2% of stops and 35% 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 152 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
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 82 / 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 100 / 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 59 / 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/biddeford-saco-old-orchard-beach-transit/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.