Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
Greater Attleboro Taunton Regional Transit Authority (GATRA)
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 9% of all tracked agencies and 9% of mid-size agencies. Operates in Massachusetts.
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.1, validator 8.0.1.
Checked for changes 18 minutes ago; last changed 8 days ago.
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 445 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
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
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
567 of 567 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
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).Likely your export tool
910 of 910 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ Often one default setting in your export.worth about +15 points
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
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.
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
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. 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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. 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. 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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). · 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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
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.
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 8 kinds of issue across 42 instances (0 error, 41 warning, 1 informational).
Service data ended 445 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.
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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 10 (purple)
- 11 (green)
- 12 (green)
- 14 (gray)
- 15 (yellow)
- 16 (orange)
- 18 (pink)
- 2 (gray)
- 4 (red)
- 5 (white)
- 6 (green)
- 7 (yellow)
- 8 (blue)
- DMS (brown)
- FL (blue)
- LIB (blue)
- L1 (red)
- L2 (green)
- L4 (blue)
- MC (green)
- ML (orange)
- MT (teal)
- SAI (red)
- WP (red)
- WNB (blue)
| Route | Type | Line color |
|---|---|---|
| 10 Attleboro/N. Attleborough | Bus | purple |
| 11 South Attleboro Connector | Bus | green |
| 12 Attleboro/South Attleboro | Bus | green |
| 14 North Attleborough/Plainville | Bus | gray |
| 15 Sturdy Hospital/La Salette | Bus | yellow |
| 16 Seekonk/Attleboro | Bus | orange |
| 18 Taunton/Norton/Attleboro | Bus | pink |
| 2 Broadway/Market Basket | Bus | gray |
| 4 Weir/Westside | Bus | red |
| 5 Walmart/E. Taunton/Target | Bus | white |
| 6 Whittenton | Bus | green |
| 7 School St./Route 44 | Bus | yellow |
| 8 County St./Target | Bus | blue |
| DMS Downtown Middleborough Shuttle | Bus | brown |
| FL Freedom Link | Bus | blue |
| LIB Liberty Link | Bus | blue |
| L1 Wareham/Onset/Wareham | Bus | red |
| L2 Cranberry Plaza To Buzzards Bay | Bus | green |
| L4 Cranberry Plaza To West Wareham | Bus | blue |
| MC Manomet/Cedarville Link | Bus | green |
| ML Mayflower Link | Bus | orange |
| MT Medway T Shuttle | Bus | teal |
| SAI Marshfield/Duxbury/Kingston | Bus | red |
| WP Wareham Plymouth Connection | Bus | red |
| WNB Wareham-New Bedford Connection | Bus | blue |
This feed has 567 stops.
List every stop
- Indian School
- Hannaford
- Market Basket
- East Water
- Linden St.
- Karena Drive
- Shaw's
- Peck St.
- 1008 West Main
- Field St.
- P Hill Rd Plaza
- MAP Academy
- Lourdes
- Bourne Park & Ride
- Buzzard's Bay
- Buzzard's Bay
- Wareham Crossing
- Cromeset Woods
- Kingsbury Plaza
- Webster Square
- Roche Bros.
- Duxbury Housing
- Tura's Pharmacy
- Tura's Pharmacy
- Beach St.
- Railroad Tracks
- Railroad Tracks
- Martin Sr. Pkwy
- Martin Sr. Pkwy
- Myles Standish
- Myles Standish
- School St.
- School St.
- Longmeadow Rd.
- Longmeadow Rd.
- Dean St.
- Dean St.
- South St. W
- South St. W
- Court St.
- Weir St.
- Summer St.
- Weir St.
- Summer St.
- Hart St.
- Hart St.
- County St.
- County St.
- Mozzone Blvd.
- Elm St.
- High St.
- North Ave.
- John Dietsch Blvd.
- John Dietsch Blvd.
- North Ave.
- S Main St.
- Mill St.
- Mill St.
- S Main St.
- Allen Ave.
- Allen Ave.
- Emerald Square Mall
- Allen Ave.
- Greenfield St.
- Lathrop Rd.
- Lathrop Rd.
- Greenfield St.
- Deer Park
- Deer Park
- Taunton Depot
- Taunton Depot
- North Hub
- Rosebrook
- ALDI's
- East Water St.
- Middleboro Ave.
- Middleboro Ave.
- County St.
- County St.
- CVS Cranberry
- Depot St.
- Court House
- Depot St.
- Wareham
- Health System
- Mattapoisett
- Route 105 (Marion)
- SRTA
- Mattapoisett
- Route 105 (Marion)
- Hillcrest Acres
- Plainville
- Washington St.
- Washington St.
- Market Basket
- Walmart Raynham
- Highland Hills
- Tiffany St.
- Tiffany St.
- Bible Chapel
- Sturdy Memorial
- Sunset Acres
- Highland Hills
- Sturdy Memorial
- Plainridge
- Highland
- Highland
- Main Ave & Route 28
- Onset Ave & Tenth St
- Attleboro T.C.
- MarketPlace Square
- Target
- Benefit St.
- Mendon Rd.
- Walmart
- North Ave.
- Attleboro School
- Jewel Ave.
- Council Aging
- Triboro Plaza
- Hope Gardens
- LaSalette Shrine
- Attleboro Crossing
- South Main
- Central Plaza
- Stop & Shop
- Circle Court
- Elm Terrace
- Emerald Square
- Trucchi's
- Acorn Hill
- Town Hall
- Riverview
- Nemasket Apts.
- Hannaford
- Middlebury Arms
- Lakeville MBTA
- Health Center
- Norfolk
- Village St.
- Medway School
- Route 58
- Mill Pond
- Cranberry Plaza
- Onset Village
- Onset Pier
- Wareham Center
- Grant St.
- Cromeset
- Agawam Village
- 7-Eleven
- Kingston Collection
- Plymouth
- BID Hospital
- Exit 5 P&B
- Shops 5
- Long Pond
- Plymouth Plantation
- Clement's Market
- Brook School
- Cedarville
- Gellar's
- Woodcrest
- White Horse
- Cordage Park
- Walmart
- Industrial Park
- Market Basket
- Algonquin Heights
- Plymouth Center
- Kingston Train
- Kingsbury Square
- Island Creek
- Halls Corner
- Duxbury Library
- Millbrook Motors
- Marshfield
- Green Harbor
- Brant Rock
- Winslow
- Shop/Kohl's
- Taunton School
- Weir St.
- Kilmer Ave.
- Route 44
- Thomas School
- Social Security
- Shaw's
- Carolina Hill
- Pinehill Estates
- Shop
- Williams St.
- Washington
- Taunton Bus Terminal
- Bristol Commons
- Walmart
- Hart St.
- Richard DeWert
- Hart's Four
- Target
- Green
- Winter St.
- Presbey Court
- Morton Hospital
- 1380 Bay St.
- Northwoods
- Myles Standish
- Norton Avenue
- Norton Post
- Chartley Corners
- South Middleborough
- Union St.
- Fuller Hospital
- Sturdy Hospital
- Bristol College
- Post Office
- Walmart
- Senior Center
- Whittenton
- Main St.
- Main St.
- Maple Terrace
- Clarence St.
- Camp St.
- S Main St.
- Stanley St.
- Towne St.
- Union St.
- Norton Ave
- Oak St.
- Shores St.
- Scott Drive
- Scott Drive
- David St.
- Norton Ave
- David St.
- Perry Ave.
- Pleasant St.
- Crowe Farm Lane
- Haggerty Highway
- Pleasant St.
- Pleasant St.
- North Attleboro
- North Ave.
- Mendon Rd.
- 272 County
- Highland Ave.
- Hope Gardens
- LaSalette Shrine
- Attleboro Crossing
- and 317 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 9 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-30 | 35.7 | first check |
| 2026-07-01 | 35.7 | no change |
| 2026-07-02 | 35.7 | no change |
| 2026-07-04 | 35.7 | no change |
| 2026-07-05 | 35.7 | no change |
| 2026-07-06 | 35.7 | no change |
| 2026-07-07 | 35.7 | no change |
| 2026-07-08 | 35.7 | no change |
| 2026-07-09 | 35.7 | 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-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 445 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)
- Warning910 instances
910 of 910 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)
- Warning910 instances
910 of 910 trips have no headsign.
Riders at the stop can't tell which direction a bus is going.
Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)
Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning567 instances
567 of 567 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)
- Warning16 instances
Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_diff_coordinates_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning11 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)
- Warning7 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Enable 'remove unused shapes' (or similar) 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)
- Warning3 instances
Some service calendars in the feed have already expired.
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)
- Warning2 instances
Equal shape distance same coordinates (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_same_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: equal_shape_distance_same_coordinates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
A recommended GTFS file (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Agencies here usually clear this within about 1 week (based on 13 observed fixes).
Validator rule: missing_recommended_file · Read the fix guide · 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
feed_info.txt is missing its start/end dates (the file itself is absent)
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
Validator rule: scorecard_missing_feed_info_dates · 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)
- Warning1 instance
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 connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)
Validator rule: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info1 instance
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.)
Validator rule: unknown_column · 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).
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.
3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (18, WP, 6).
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.
200 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Main Ave & Route 28", "Onset Ave & Tenth St", "Summer St.", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
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 2 changes
For example: SRTA -> Srta
Run it yourself on your own copy of the feed: scorecard autofix <feed.zip> --out corrected.zip
NTD certification readiness Not ready
Resolve this before you certify on the D-10. Service data expired 445 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 445 days ago, so FTA would find the link out of date.
- agency_id matches your NTD ID Not checked yet
- Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
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). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and 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 445 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 445 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.
- 11 of 287 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
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.
- Correctness 66 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 0 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 22 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: 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 live badge on your agency site or feed README. It updates daily 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-attleboro-taunton-regional-transit-authority-gatra-418/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, 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.