Feed status · checked 2026-08-01
Manatee County Area Transit
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Florida.
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 3 hours ago; last changed 30 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
928 of 928 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
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
Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.Likely your export tool
Some stops sit far from the route line, going by the feed's own distance values. Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
⏱ Usually an export-tool fix, not hand editing.worth about +8 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
- 928 of 928 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
- 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
- Feed evidence
- Some stops sit far from the route line, going by the feed's own distance values.
- Next action
- Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.
- 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. 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.
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. 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.
Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. · 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 is in 307 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 100% 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 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.
Score by category
The MobilityData validator flagged 5 kinds of issue across 2412 instances (0 error, 2412 warning, 0 informational).
Service data covers the next 307 days.
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 published.
0% of stops state accessibility (0% 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 (304).
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.
915 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("29TH ST E/60TH AVE E", "60TH AVE E/32ND ST E", "60TH AVE E/35TH LN E", 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 928 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 (pink)
- 12 (pink)
- 13 (gray)
- 16 (pink)
- 2 (white)
- 201 (white)
- 203 (gray)
- 3 (gray)
- 304 (red)
- 33 (blue)
- 4 (gray)
- 5 (orange)
- 6 (white)
- 75 (yellow)
- 8 (gray)
- 9 (pink)
- 99 (white)
| Route | Type | Line color |
|---|---|---|
| 1 1 PALMETTO/ELLENTON | Bus | pink |
| 12 12 SR 70 / 53RD AVE E | Bus | pink |
| 13 13 DOWNTOWN/PALMETTO | Bus | gray |
| 16 16 15TH STREET E/TALLEVAST | Bus | pink |
| 2 2 EAST BRADENTON - SAMOSET | Bus | white |
| 201 201 PALMETTO RUBONIA HOLY CROSS | Bus | white |
| 203 203 SKYWAY CONNECTION | Bus | gray |
| 3 3 MANATEE AVENUE EAST | Bus | gray |
| 304 304 MANATEE AVE WEST | Bus | red |
| 33 GULF ISLANDS FERRY | Bus | blue |
| 4 4 9TH AVE EAST & WEST | Bus | gray |
| 5 5 AMI TROLLEY | Bus | orange |
| 6 6 CORTEZ ROAD | Bus | white |
| 75 75 BEACH CONNECT SHUTTLE | Bus | yellow |
| 8 8 ONECO | Bus | gray |
| 9 9 26TH ST WEST | Bus | pink |
| 99 99 BRADENTON/SARASOTA | Bus | white |
List every stop
- ELLENTON OUTLET MALL
- 29TH ST E/60TH AVE E
- 60TH AVE E/32ND ST E
- 60TH AVE E/35TH LN E
- MENDOZA RD/64TH AVE E
- MENDOZA RD/RIDGEWOOD BLVD
- MENDOZA RD/72ND AVE E (VICTORY ROAD)
- VICTORY RD/71ST AVE E
- VICTORY RD/US 301 N
- US 301/RIDGEWOOD BLVD
- US 301/60TH AVE E
- 60TH AVE E/20TH CT E
- US 301/51ST AVE E
- US 301/45TH AVE E
- US 301/FRANKLIN AVE
- US 301/CENTRAL AVE (GAMBLE PLANT)
- US 301/36TH AVE E
- US 301/GARY AVE E
- US 301/24TH AVE E
- US 301/19TH AVE E
- US 301/CANAL RD
- HABEN BLVD/MANATEE SCHOOL FOR ARTS
- HASKO RD/WALMART PALMETTO
- HASKO RD/US 301
- US 301/US 41 RAMP
- 10TH ST W/2ND AVE W
- 10TH ST W/4TH AVE W
- 10TH ST W/5TH AVE DR W
- 10TH ST W/7TH AVE WB
- 10TH ST W/13TH AVE W
- 10TH ST W/14TH AVE W
- 14TH AVE W/12TH ST W
- 14TH AVE W/14TH ST W
- 14TH AVE W/17TH ST W
- 8TH AVE W/7TH ST W
- 7TH ST W/7TH AVE W
- 17TH ST W / 9TH AVE W
- PALMETTO STATION
- BAYSHORE RD/25TH ST W
- BAYSHORE RD/20TH ST W
- 17TH ST E/1ST AVE E
- 17TH ST E/3RD AVE E
- 17TH ST W/3RD AVE W
- 17TH ST W/5TH AVE W
- 17TH ST W/BAYSHORE RD
- BAYSHORE RD/17TH ST W
- US 301/PALMETTO VILLAGE SHOPPING CTR
- US 301/PALM 2ND ST
- US 301/HABEN BLVD
- US 301 N/23RD AVE E (FELD ENTERTAINMENT)
- US 301 N/25TH AVE DR E
- US 301 N/LINDEN DR
- US 301 N/LEFFINGWELL AVE
- US 301 N/40TH AVE E
- US 301 N/44TH AVE E
- US 301 N/18TH ST E
- 60TH AVE E/US 301 N
- 10TH ST W/5TH AVE W
- 18TH ST & PALM DR
- 17TH ST W/6TH AVE W
- 18TH ST E/44TH AVE E
- 18TH ST E/46TH AVE E
- 47TH TER E/18TH ST E
- 19TH ST CT E/47TH TER E
- 19TH ST CT E/SOUTH OF 44TH AVE E
- 19TH ST CT E/39TH AVE E
- 38TH AVE E/18TH ST E
- 15TH ST E/33RD AVE DR E
- 15TH ST E/31ST AVE E
- 15TH ST E/32ND AVE E
- 15TH ST E/34TH AVE E
- 26TH AVE E/19TH ST E
- 26TH AVE E/18TH ST E
- 26TH AVE E/16TH ST CT E
- 26TH AVE E/15TH ST E
- 26TH AVE E/12TH ST CT E (PUBLIC WORKS)
- 26TH AVE E/9TH ST E
- 26TH AVE E/5TH ST E
- 26TH AVE E/3RD ST E
- 26TH AVE E/1ST ST
- 1ST ST/23RD AVE E
- 1ST ST/17TH AVE W (RED BARN FLEA MARKET)
- 1ST ST/13TH AVE E
- MLK AVE W/2ND ST W
- MLK AVE W/3RD ST W
- MLK AVE W/6TH ST W
- MLK AVE W/8TH ST W
- MLK AVE W/9TH ST W
- 9TH ST W/10TH AVE W
- 9TH ST W/12TH AVE W
- 9TH ST W/14TH AVE W
- 9TH ST W/17TH AVE W (LECOM PARK)
- 9TH ST W/19TH AVE W
- 9TH ST W/21ST AVE W
- 9TH ST W/23RD AVE W
- 9TH ST W/26TH AVE W
- 9TH ST W/29TH AVE W
- 9TH ST W/31ST AVE W
- DESOTO STATION
- 301 BLVD/9TH ST W
- 9TH ST W/31ST AVE W
- 30TH AVE W/8TH ST W
- 30TH AVE W/6TH ST W
- 30TH AVE W/1ST ST (US 41)
- 30TH AVE E/3RD ST E
- 30TH AVE E/5TH ST E
- 30TH AVE E/7TH ST E
- 30TH AVE E/9TH ST E
- 30TH AVE E/11TH ST CT E
- 30TH AVE E/15TH ST E
- 30TH AVE W/3RD ST W
- 30TH AVE E/US 301
- 30TH AVE E/21ST ST CT E
- 30TH AVE E/25TH ST E
- 30TH AVE E/27TH ST E
- 26TH AVE E/27TH ST E
- 67TH ST CIR E/6TH AVE E (SUNRISE INN)
- 67TH ST CIR E/6TH AVE E (DAYS INN)
- 67TH ST CIR E/6TH AVE E (CRACKER BARREL)
- 67TH ST CIR E/6TH AVE E (MCDONALDS)
- SR 64 E/KAY RD
- CYPRESS CREEK BLVD/SR 64 WALMART
- SR 64 E/CYPRESS CREEK BLVD
- SR 64 E/57TH ST E
- SR 64 E/53RD ST E
- SR 64 E/50TH ST E (RIVERS EDGE)
- SR 64 E/AMERICA'S CUP BLVD
- SR 64 E/43RD ST BLVD E
- MANATEE AVE E/27TH ST E
- MANATEE AVE E/26TH ST E
- MANATEE AVE E/24TH ST E
- MANATEE AVE E/23RD ST E
- MANATEE AVE E/21ST ST E
- MANATEE AVE E/19TH ST E
- MANATEE AVE E/17TH ST E
- MANATEE AVE E/15TH ST E
- MANATEE AVE E/12TH ST E
- MANATEE AVE E/10TH ST E
- MANATEE AVE E/6TH ST E
- 6TH AVE E/12TH ST E
- 2ND ST E/4TH AVE E (MANATEE HOSPITAL)
- 2ND ST E/RIVERSIDE DR E
- RIVERFRONT BLVD/100 RIVERFRONT BLVD
- 3RD ST W/3RD AVE W
- MANATEE AVE W/3RD ST W
- MANATEE AVE W/15TH ST W
- MANATEE AVE W/20TH ST W
- MANATEE AVE W/24TH ST W
- MANATEE AVE W/26TH ST W
- MANATEE AVE W/28TH ST W
- MANATEE AVE W/29TH ST W
- MANATEE AVE W/32ND ST W
- MANATEE AVE W/37TH ST W
- MANATEE AVE W/38TH ST W
- MANATEE AVE W/40TH ST W WESTGATE
- MANATEE AVE W/43RD ST W
- MANATEE AVE W/45TH ST W
- MANATEE AVE W/47TH ST W
- MANATEE AVE W/49TH ST W
- MANATEE AVE W/51ST ST W
- MANATEE AVE W/53RD ST W
- MANATEE AVE W/55TH ST W
- MANATEE AVE W/59TH ST W
- MANATEE AVE W/63RD ST W
- MANATEE AVE W/65TH ST W
- MANATEE AVE W/VILLAGE GREEN PKWY
- MANATEE AVE W/BEACHWAY PLAZA
- MANATEE AVE W/77TH ST W
- MANATEE AVE W/81ST ST W
- MANATEE AVE W/CAUSEWAY PARK
- MANATEE AVE W/FLAMINGO DR
- MANATEE AVE W/PERICO WAY
- MANATEE AVE W/PERICO BAY BLVD
- MANATEE AVE W/MARTINIQUE DR
- MANATEE AVE W/EAST BAY DR
- MANATEE AVE/6TH AVE W
- MANATEE AVE/6TH AVE
- MANATEE AVE W/MARTINIQUE DR
- MANATEE AVE W/PERICO BAY BLVD
- MANATEE AVE W/BRISTOL BAY DR
- MANATEE AVE W/FLAMINGO DR
- MANATEE AVE W/CAUSEWAY PARK
- MANATEE AVE W/PALMA SOLA BLVD
- MANATEE AVE W/77TH ST W
- MANATEE AVE W/75TH ST W
- MANATEE AVE W/VILLAGE GREEN PKWY
- MANATEE AVE W/67TH ST W
- MANATEE AVE W/FOUNTAIN CT SHOPPING
- MANATEE AVE W/62ND ST W
- MANATEE AVE W/60TH ST W
- BLAKE HOSPITAL TRANSFER POINT
- 59TH ST W/38TH AVE W (YMCA)
- 59TH ST W/15TH AVE W
- 59TH ST W/11TH AVE W
- 59TH ST W/9TH AVE DR W
- 59TH ST W/7TH AVE DR W
- 59TH ST W/MANATEE AVE W
- MANATEE AVE W/59TH ST W
- MANATEE AVE W/55TH ST W
- MANATEE AVE W/51ST ST W
- MANATEE AVE W/49TH ST W
- MANATEE AVE W/46TH ST W
- MANATEE AVE W/44TH ST W
- MANATEE AVE W/39TH ST W(WESTGATE PLAZA)
- MANATEE AVE W/33RD ST CT W
- MANATEE AVE W/32ND ST W
- MANATEE AVE W/30TH ST W
- MANATEE AVE W/28TH ST W
- MANATEE AVE W/25TH ST W
- MANATEE AVE W/22ND ST W
- MANATEE AVE W/19TH ST W
- MANATEE AVE W/VIRGINIA DR
- 6TH AVE W/8TH ST W
- 6TH AVE W/6TH ST W
- 6TH AVE W/3RD ST W
- 6TH AVE W/2ND ST W
- 6TH AVE E/2ND ST E
- 6TH AVE E/5TH ST E (HEALTH DEPT)
- 6TH AVE E/7TH ST E
- MANATEE AVE E/14TH ST E
- MANATEE AVE E/15TH ST E
- MANATEE AVE E/18TH ST E
- MANATEE AVE E/20TH ST E
- MANATEE AVE E/23RD ST E
- MANATEE AVE E/25TH ST E
- MANATEE AVE E/27TH ST E
- MANATEE AVE E/29TH ST E
- MANATEE AVE E/CARLTON ARMS BLVD
- SR 64 E/41ST ST E
- SR 64 E/OAKLEAF BV (BRADEN RIVER PLZ)
- SR 64 E/48TH ST CT E
- SR 64 E/51ST ST E
- SR 64/53RD ST E
- SR 64 E/MORGAN JOHNSON (VA CLINIC)
- SR 64 E/MORGAN JOHNSON RD
- SR 64 E/60TH ST CT E
- MANATEE AVE E/4TH ST E
- CORTEZ RD W/103RD ST CT W (PARADISE BAY)
- GULF DR/42ND ST (MANATEE PUBLIC BEACH)
- 59TH ST W/17TH AVE W
- SR 64 E/CARLTON ARMS BLVD
- GT BRAY REC CENTER WB
- 38TH AVE E/30TH ST E
- 30TH ST E/53RD AVE E (WALMART)
- 30TH ST E/51ST AVE E (FARSIDE)
- 30TH ST E/49TH AVE E
- 30TH ST E/45TH WAY E
- 30TH ST E/38TH AVE E
- 27TH ST E/36TH AVE E
- 27TH ST E/34TH AVE E
- and 678 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 | 74.3 | first check |
| 2026-07-30 | 74.3 | no change |
| 2026-07-31 | 74.3 | no change |
| 2026-08-01 | 74.3 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
8 findings, ordered by severity.
Show every finding
- Warning2220 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)
- Warning928 instances
928 of 928 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)
- Warning170 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
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)
- Warning16 instances
Some route long names repeat the route's short name inside them.
Apps show both names together, so riders see the number twice, like '5 5 Downtown'.
Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)
Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
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)
- Info475 instances
About 475 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)
- 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 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 307 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 Needs attention
- 1250 of 1274 trips have a shape; 24 do not. Fill in shapes.txt and trips.shape_id for the remaining trips so every trip has a path. Reduced, Rural, and Tribal NTD reporters need full coverage by Report Year 2026.
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 0% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 307 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 100% 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 306 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 70 / 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 60 / 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.
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/manatee-county-area-transit-2258/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.