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

Breeze Transit

Based on the feed this agency publishes

FDCBA

31.7 / 100

unchanged since 2026-07-08

Ahead of 7% of all tracked agencies and 12% of large agencies. Operates in Florida.

Feed expiredAccessibility gapsNo realtime feed

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 16 minutes ago; last fetch returned HTTP 404.

Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.

How we measured this

Confidence in this measurement: provisional.

Realtime quality was not measured this run. It does not count against the grade.
The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead.

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

Top things to fix

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 440 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).

Fix 02

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

1265 of 1296 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

Fix 03

Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).Likely your export tool

1458 of 1458 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).

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. Make this change in whatever tool produces your feed, then re-export.
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. Make this change in whatever tool produces your feed, then re-export.
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. Make this change in whatever tool produces your feed, then re-export.
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 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.

Hi,

Our GTFS feed (Breeze Transit) scored F (31.7 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
   What: Service data ended 440 day(s) ago.
   Validator notice: scorecard_feed_expired
   Guide: https://gtfsscorecard.org/fix/scorecard_feed_expired/

2. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
   What: 1265 of 1296 stops don't say whether a wheelchair user can board there.
   Validator notice: scorecard_wheelchair_boarding_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_boarding_unknown/

3. Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).
   What: 1458 of 1458 trips don't say whether the vehicle is wheelchair accessible.
   Validator notice: scorecard_wheelchair_accessible_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_accessible_unknown/

Full scorecard: https://gtfsscorecard.org/agency/breeze-transit/

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.

Hi Breeze Transit team,

Service data ended 440 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.

The fix is usually one export setting: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.

This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/breeze-transit/

Score by category

Correctness50.0 / 100

The MobilityData validator flagged 9 kinds of issue across 2975 instances (0 error, 2975 warning, 0 informational).

Freshness0.0 / 100

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

Rider experience31.6 / 100

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 not published.

Accessibility1.5 / 100

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

Realtime qualityNot yet measured

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.

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

01 (brown)
02 (red)
03 (orange)
06 (yellow)
07 (brown)
08 (green)
09 (green)
12 (blue)
14 (pink)
17 (pink)
19 (yellow)
25 (yellow)
33 (gray)
76 (teal)
99 (purple)

Routes in Breeze Transit's feed
Route	Type	Line color
01 Downtown/Fruitville/Cattlemen	Bus	brown
02 Downtown/SRQ/UTC Mall	Bus	red
03 Downtown/Bahia Vista/Cattlemen	Bus	orange
06 Beneva/Sarasota Square Mall	Bus	yellow
07 Downtown/N Orange/Newtown/NE Plaza	Bus	brown
08 Downtown/N Orange/US 301/SRQ	Bus	green
09 Venice/North Port	Bus	green
12 Downtown/N Lockwood/University	Bus	blue
14 Downtown/Southgate/Bee Ridge	Bus	pink
17 Sarasota/US-41/Venice	Bus	pink
19 Gulf Gate/Cattlemen	Bus	yellow
25 Southgate/Swift/Gulf Gate	Bus	yellow
33 Siesta Key/Pinecraft/Cattlemen	Bus	gray
76 76 Flyer	Bus	teal
99 Sarasota/SRQ/Bradenton	Bus	purple

This feed has 1296 stops.

List every stop

RINGLING BLVD @ S TUTTLE AVE
MONICA PKWY @ MONICA PL
27TH PKWY @ GALLEON PL
27TH PKWY @ RANDA BLVD
27TH PKWY @ RIDGE AVE
DR MARTIN LUTHER KING JR WAY @ N TUTTLE AVE
DR MARTIN LUTHER KING JR WAY @ CHESTER AVE
DR MARTIN LUTHER KING JR WAY @ EUCLID AVE
DR MARTIN LUTHER KING JR WAY @ BOOKER AVE
DR MARTIN LUTHER KING JR WAY @ LEONARD REID AVE
DR MARTIN LUTHER KING JR WAY @ PERSHING AVE
DR MARTIN LUTHER KING JR WAY @ GILLESPIE AVE
N OSPREY AVE @ DR MARTIN LUTHER KING JR WAY
N OSPREY AVE @ 29TH ST
N ORANGE AVE @ DR MARTIN LUTHER KING JR WAY
N ORANGE AVE @ 23RD ST
N ORANGE AVE @ 20TH ST
N ORANGE AVE @ 18TH ST
N OSPREY AVE @ 12TH ST
N ORANGE AVE @ 12TH ST
N ORANGE AVE @ 12TH ST NS
N ORANGE AVE @ 8TH ST
N ORANGE AVE @ BOULEVARD OF THE ARTS
N ORANGE AVE @ FRUITVILLE RD
S OSPREY AVE @ OAK ST
S OSPREY AVE @ BROTHER GEENEN WAY
FRUITVILLE RD @ GOODRICH AVE
S TAMIAMI TRL @ DATURA ST
S TAMIAMI TRL @ WISTERIA ST
S TAMIAMI TRL @ BOYCE ST
S TAMIAMI TRL @ WEBBER ST
S TAMIAMI TRL @ ROSE ST
S TAMIAMI TRL @ GLENGARY ST
S TAMIAMI TRL @ WORRINGTON ST
S TAMIAMI TRL @ N LAKE SHORE DR
S TAMIAMI TRL @ FIELD RD
S TAMIAMI TRL @ KESTRAL PARK WAY
S TAMIAMI TRL @ LANDINGS BLVD
FRUITVILLE RD @ N OSPREY AVE
S TAMIAMI TRL @ CONSTITUTION BLVD
S TAMIAMI TRL @ MEADOWOOD ST
S TAMIAMI TRL @ UPPER BEECHWOOD AVE
S TAMIAMI TRL @ UPPER GLENCOE AVE
FRUITVILLE RD @ N LINKS AVE
SARASOTA SQUARE BLVD @ POTTER PARK DR
S TAMIAMI TRL @ POCONO TRL E
S TAMIAMI TRL @ PALMETTO RD E
N TAMIAMI TRL @ ALBEE RD E
N TAMIAMI TRL @ SPENCER AVE
N TAMIAMI TRL @ COLLINS RD
FRUITVILLE RD @ FLETCHER AVE
N TAMIAMI TRL @ GIOTTO DR
S TAMIAMI TRL @ RUBENS DR
S TAMIAMI TRL @ JO AN DR
FRUITVILLE RD @ AUDUBON PL
S TAMIAMI TRL @ SOUTHWINDS DR
S TAMIAMI TRL @ MEADOWOOD ST
S TAMIAMI TRL @ CONSTITUTION BLVD
S TAMIAMI TRL @ MONTE CARLO DR
S TAMIAMI TRL @ CARMILFRA WAY
S TAMIAMI TRL @ PHILLIPPI ST
S TAMIAMI TRL @ LAS LOMAS DR
S TAMIAMI TRL @ PROCTOR RD
S TAMIAMI TRL @ SANDRALA DR
S TAMIAMI TRL @ WORRINGTON ST
S TAMIAMI TRL @ ROBINHOOD ST
S TAMIAMI TRL @ GLENGARY ST
S TAMIAMI TRL @ ROSELAWN ST
FRUITVILLE RD @ N LIME AVE
S TAMIAMI TRL @ ORCHID ST
S TAMIAMI TRL @ GOLDENROD ST
S TAMIAMI TRL @ WEBBER ST
S TAMIAMI TRL @ SUNNYSIDE CT
S TAMIAMI TRL @ DATURA ST
FRUITVILLE RD @ N LIME AVE FS
S OSPREY AVE @ BROTHER GEENEN WAY
N OSPREY AVE @ OAK ST
S OSPREY AVE @ LAUREL ST
S OSPREY AVE @ MORRILL ST
FRUITVILLE RD @ N JEFFERSON AVE
N ORANGE AVE @ 12TH ST FS
N ORANGE AVE @ 4TH ST
UNIVERSITY PKWY @ N WASHINGTON BLVD
UNIVERSITY PKWY @ N WASHINGTON BLVD
N WASHINGTON BLVD @ DESOTO RD
N WASHINGTON BLVD @ SANFORD CIR
N WASHINGTON BLVD @ NORTHGATE BLVD
N TUTTLE AVE @ 6TH ST
N WASHINGTON BLVD @ MYRTLE ST
N ORANGE AVE @ 1ST ST
N WASHINGTON BLVD @ 4TH ST
N WASHINGTON BLVD @ 6TH ST
N WASHINGTON BLVD @ 9TH ST
N TUTTLE AVE @ 8TH ST
N WASHINGTON BLVD @ 12TH ST
N WASHINGTON BLVD @ 17TH ST
17TH ST @ EAST AVE
17TH ST @ LIME AVE FS
17TH ST @ EUCLID AVE
17TH ST @ N TUTTLE AVE
RINGLING BLVD @ EAST AVE
N TUTTLE AVE @ 10TH ST
12TH ST @ N TUTTLE AVE
12TH ST @ TARPON AVE
N LOCKWOOD RIDGE RD @ 15TH ST
N LOCKWOOD RIDGE RD @ MONICA PKWY
N LOCKWOOD RIDGE RD @ PATTON ST
N LOCKWOOD RIDGE RD @ LOCKWOOD MEADOWS BLVD
N LOCKWOOD RIDGE RD @ 27TH PKWY
N LOCKWOOD RIDGE RD @ GOCIO RD
N LOCKWOOD RIDGE RD @ GOCIO RD FS
N TUTTLE AVE @ 12TH ST
N LOCKWOOD RIDGE RD @ MYRTLE ST
N LOCKWOOD RIDGE RD @ HAMLETS BLVD
N LOCKWOOD RIDGE RD @ 49TH ST
N LOCKWOOD RIDGE RD @ 51ST ST
N LOCKWOOD RIDGE RD @ DESOTO RD
N LOCKWOOD RIDGE RD @ 61ST ST
N LOCKWOOD RIDGE RD @ 61ST ST
N LOCKWOOD RIDGE RD @ 59TH ST
N LOCKWOOD RIDGE RD @ DESOTO RD
N LOCKWOOD RIDGE RD @ DESOTO RD FS
N LOCKWOOD RIDGE RD @ 51ST ST
N LOCKWOOD RIDGE RD @ 49TH ST
N LOCKWOOD RIDGE RD @ 44TH ST
N LOCKWOOD RIDGE RD @ 42ND ST
N LOCKWOOD RIDGE RD @ MYRTLE ST
N LOCKWOOD RIDGE RD @ 40TH ST
N LOCKWOOD RIDGE RD @ 40TH ST NS
N LOCKWOOD RIDGE RD @ LOCKWOOD MEADOWS BLVD
N LOCKWOOD RIDGE RD @ MONICA PKWY
N LOCKWOOD RIDGE RD @ 15TH ST
12TH ST @ TARPON AVE
12TH ST @ N TUTTLE AVE
17TH ST @ N TUTTLE AVE NS
17TH ST @ N TUTTLE AVE
17TH ST @ N EUCLID AVE
17TH ST @ LIME AVE
17TH ST @ MANGO AVE
17TH ST @ EAST AVE
N WASHINGTON BLVD @ 17TH ST
N WASHINGTON BLVD @ 13TH ST
BENEVA RD @ LAKE POINTE BLVD
N WASHINGTON BLVD @ 10TH ST
N WASHINGTON BLVD @ 6TH ST
GANTT RD @ COUNTRY WALK LN
GANTT RD @ CEDAR POINTE BLVD
GANTT RD @ PROCTOR RD
CATTLEMEN RD @ PROCTOR RD
CATTLEMEN RD @ WILKINSON RD
CATTLEMEN RD @ CASA DEL SOL BLVD
CATTLEMEN RD @ CENTER POINTE DR
CATTLEMEN RD @ BEE RIDGE RD
CATTLEMEN RD @ CATTLERIDGE BLVD
CATTLEMEN RD @ CATTLERIDGE AVE
CATTLEMEN RD @ CATTLERIDGE DR
CATTLEMEN RD @ MCKOWN RD
CATTLEMEN RD @ COLONIAL OAKS BLVD
CATTLEMEN RD @ CATTLEMEN LN
BENEVA RD @ FRUITVILLE RD FS
CATTLEMEN RD @ HAGERMAN RD
CATTLEMEN RD @ OLD SUMMERWOOD BLVD
N TAMIAMI TRL @ 11TH ST
DESOTO RD @ ISABELLA AVE
UNIVERSITY PKWY @ HONORE AVE
UNIVERSITY PKWY @ MEDICI CT
LONGWOOD RUN BLVD @ UNIVERSITY PKWY
BENEVA RD @ CIRCUS BLVD
LONGWOOD RUN BLVD @ DEL SOL BLVD
LONGWOOD RUN BLVD @ MONTE ROSSO RD
LONGWOOD RUN BLVD @ MAGNOLIA PL
DESOTO RD @ N LOCKWOOD RIDGE RD
BAHIA VISTA ST @ COLEMAN AVE
BENEVA RD @ CIRCUS BLVD NS
DESOTO RD @ N WASHINGTON BLVD
DESOTO RD @ N OSPREY AVE
DESOTO RD @ TRI PAR DR
N TAMIAMI TRL @ BEVERLY DR
N TAMIAMI TRL @ REMINGTON DR
CLARK RD @ BESSIE DR
BENEVA RD @ CALLIANDRA DR
N BENEVA RD @ 12TH ST
N TAMIAMI TRL @ 13TH ST
N TAMIAMI TRL @ 15TH ST
17TH ST @ N BENEVA RD
N TAMIAMI TRL @ 17TH ST
N TAMIAMI TRL @ PANAMA DR
N TAMIAMI TRL @ PATTERSON DR
N TAMIAMI TRL @ HIGHLAND ST
N TAMIAMI TRL @ MYRTLE ST
N TAMIAMI TRL @ 42ND ST
N TAMIAMI TRL @ 46TH ST
17TH ST @ ANDREA PL
N TAMIAMI TRL @ 47TH ST
N TAMIAMI TRL @ MECCA DR
N TAMIAMI TRL @ 47TH ST
N TAMIAMI TRL @ UNIVERSITY PKWY
UNIVERSITY PKWY @ ROYAL PALM AVE
UNIVERSITY PKWY @ DESOTO PL
DESOTO RD @ TRI PAR DR
DESOTO RD @ SARASOTA LAKES BLVD
DESOTO RD @ DESOTO PKWY
DESOTO RD @ N WASHINGTON BLVD
DESOTO RD @ N LOCKWOOD RIDGE RD
DESOTO RD @ ISABELLA AVE
DESOTO RD @ SAN JUAN DR
DESOTO RD @ ANGELES AVE
DESOTO RD @ MINK RD
DESOTO RD @ CARMEN AVE
DESOTO RD @ SAN JOSE DR
DESOTO RD @ TIVOLI AVE
LONGWOOD RUN BLVD @ MONTE ROSSO RD
LONGWOOD RUN BLVD @ DEL SOL BLVD
LONGWOOD RUN BLVD @ UNIVERSITY PKWY
UNIVERSITY PKWY @ MEDICI CT
BENEVA RD @ FAIRWAY WOODS BLVD
BENEVA RD @ TORREY PINES BLVD
BENEVA RD @ CURTISS AVE
CATTLEMEN RD @ OLD SUMMERWOOD BLVD
CATTLEMEN RD @ HAGERMAN RD
BAHIA VISTA ST @ GANTT AVE
CATTLEMEN RD @ CATTLEMEN LN
CATTLEMEN RD @ COLONIAL OAKS BLVD
CATTLEMEN RD @ CATTLERIDGE AVE
CATTLEMEN RD @ BEE RIDGE RD
CATTLEMEN RD @ BEE RIDGE RD NS
CATTLEMEN RD @ CENTER POINTE DR
CATTLEMEN RD @ CASA DEL SOL BLVD
CATTLEMEN RD @ CASA DEL SOL BLVD FS
BENEVA RD @ PALMER RANCH PKWY
CATTLEMEN RD @ WILKINSON RD
CATTLEMEN RD @ PROCTOR RD
GANTT RD @ PROCTOR RD
GANTT RD @ CEDAR OAK BLVD
GANTT RD @ COUNTRY WALK LN
GANTT RD @ ASHTON RD
CLARK RD @ PINKNEY AVE
CLARK RD @ DEREK AVE
CLARK RD @ HONORE AVE
CLARK DR @ LAWTON DR
CLARK RD @ SAWYER RD
CLARK RD @ LAMBERT PL
CLARK RD @ MIRROR LAKE RD
CLARK RD @ WILSHIRE BLVD
CLARK RD @ SAWYER RD
CLARK RD @ GROCERY LN
CLARK RD @ DEREK AVE
GULF GATE DR @ ARUBA LN
GULF GATE DR @ BISPHAM RD
N TAMIAMI TRL @ SYLVAN DR
and 1046 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 20 checks — unchanged since 2026-07-08.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-06-19	31.7	first check
2026-06-20	31.7	no change
2026-06-21	31.7	no change
2026-06-22	31.7	no change
2026-06-23	31.7	no change
2026-06-24	31.7	no change
2026-06-25	31.7	no change
2026-06-26	31.7	no change
2026-06-27	31.7	no change
2026-06-28	31.7	no change
2026-06-29	31.7	no change
2026-06-30	31.7	no change
2026-07-01	31.7	no change
2026-07-02	31.7	no change
2026-07-04	31.7	no change
2026-07-05	31.7	no change
2026-07-06	31.7	no change
2026-07-07	31.7	no change
2026-07-08	31.7	no change
2026-07-09	31.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 440 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)
Warning2737 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.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1458 instances
1458 of 1458 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)
Warning1265 instances
1265 of 1296 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)
Warning170 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)
Warning33 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)
Warning15 instances
Same name and description for route (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_name_and_description_for_route' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: same_name_and_description_for_route · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning13 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.)
Agencies here usually clear this within about 2 weeks (based on 6 observed fixes).
Validator rule: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning4 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.)
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)
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.)
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
Validator rule: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
Route long name contains short name (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_long_name_contains_short_name' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: route_long_name_contains_short_name · 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
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)
Info1211 instances
About 1211 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 (e.g. 'Main St & 2nd Ave'). (Often a bulk fix in your scheduling software.)
Validator rule: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)

Beyond the grade

Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.

1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (08).
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.
1273 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("FRUITVILLE RD @ GOODRICH AVE", "FRUITVILLE RD @ N OSPREY AVE", "FRUITVILLE RD @ N LINKS AVE", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

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 1211 changes
For example: DOWNTOWN TRANSFER STATION -> Downtown Transfer Station

Download corrected feed

NTD certification readiness Not ready

Resolve this before you certify on the D-10. Service data expired 440 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 440 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.

shapes.txt covers your trips Ready: All 1458 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 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 440 days ago. States wheelchair access on 2% 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 440 days ago.
Accessible Not yet: States wheelchair access on 2% 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.

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 50 / 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 32 / 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.

[![Breeze Transit GTFS data quality grade: F](https://gtfsscorecard.org/data/artifacts/breeze-transit/badge.svg)](https://gtfsscorecard.org/agency/breeze-transit/)

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/breeze-transit/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.

GTFS Scorecard. (2026). Breeze Transit GTFS feed-quality record, dated 2026-07-09 (grade F (31.7/100), rubric v1.1, gtfs-validator 8.0.1, feed sha256 e1a40f4bda07…). https://gtfsscorecard.org/data/artifacts/breeze-transit/2026-07-09.json

@misc{gtfsscorecard-breeze-transit-2026-07-09,
  title        = {Breeze Transit GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/breeze-transit/2026-07-09.json}},
  note         = {Checked 2026-07-09; rubric v1.1; gtfs-validator 8.0.1; grade F (31.7/100)}
}

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.