Feed status · checked 2026-08-01
Collier Area Transit (CAT)
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 1 days ago; last changed 38 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
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 2039 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category
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
581 of 581 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
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
487 of 487 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 +15 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
- Service data ended 2039 day(s) ago.
- Next action
- Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- 581 of 581 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
- 487 of 487 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
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.
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.
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_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.
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. 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 was 2039 days ago.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- No fare information is published in the feed.
- 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.
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 10 kinds of issue across 4868 instances (0 error, 4868 warning, 0 informational).
Service data ended 2039 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.
2 accessibility depth signals
6 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (16, 12, 17, 20, 27, and more).
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.
500 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("US 41 and Andrew Dr", "US 41 and Shadowlawn Dr", "US 41 and Commercial Dr", 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.
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 581 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.
- 14 (teal)
- 17 (green)
- 18 (yellow)
- 24 (brown)
- 21 (white)
- 121 (white)
- 22 (white)
- 23 (red)
- 26 (black)
- 15 (purple)
- 20 (pink)
- 27 (pink)
- 28 (gray)
- 29 (gray)
- 11 (red)
- 19 (blue)
- 16 (gray)
- 25 (green)
- 12 (yellow)
- 13 (orange)
| Route | Type | Line color |
|---|---|---|
| 14 Bayshore -Coastland Mall | Bus | teal |
| 17 Rattlesnake - Fsw | Bus | green |
| 18 Us 41 East - Naples Manor | Bus | yellow |
| 24 Us 41 East - Charlee Estates | Bus | brown |
| 21 Marco Island Circulator | Bus | white |
| 121 Express Immokalee - Marco Island | Bus | white |
| 22 Immokalee Circulator | Bus | white |
| 23 Immokalee Circulator | Bus | red |
| 26 Clam Pass | Bus | black |
| 15 Golden Gate City | Bus | purple |
| 20 Pine Ridge | Bus | pink |
| 27 951-Immokalee Rd | Bus | pink |
| 28 Golden Gate Estates-Oilwell-Immokalee | Bus | gray |
| 29 Beach Bus | Bus | gray |
| 11 Us 41 - Creekside | Bus | red |
| 19 Golden Gate Estates - Immokalee | Bus | blue |
| 16 Golden Gate City | Bus | gray |
| 25 Golden Gate Pkway - Goodlette Rd | Bus | green |
| 12 Airport-Creekside | Bus | yellow |
| 13 Nch-Coastland Mall | Bus | orange |
List every stop
- GOVT Center
- US 41 and 3rd Ave N
- Airport Pulling Rd and Vanderbilt Bch Rd
- Airport Pulling Rd and Orange Blossom Dr
- Airport Pulling Rd and Arbour Walk Cir
- Airport Pulling Rd and J and C Blvd
- Airport Pulling Rd and Naples Blvd
- Pine Ridge Crossing
- Airport Pulling Rd and Clubhouse Dr
- Airport Pulling Rd and Pine Wood Cir
- Airport Pulling Rd and Poinciana Dr
- Poinciana Elementary
- US 41 and 5th Ave N
- Airport Pulling Rd and Golden Gate Pkwy
- Airport Pulling Rd and Longboat Dr
- Airport Pulling Rd and Horseshoe Dr
- Airport Pulling Rd and Prospect Ave
- Airport Pulling Rd and Radio Rd
- Airport Pulling Rd and North Rd (DMV)
- Airport Pulling Rd and Estey Ave
- Airport Pulling Rd and Connecticut Ave
- Airport Pulling Rd and Glades Blvd
- Airport Pulling Rd and US 41
- US 41 and 8th Ave N
- Davis Blvd and Airport Pulling Rd
- Davis Blvd and Shadowlawn Dr
- Davis Blvd and Brookside Dr
- Davis Blvd and Market St
- 951 and San Marco Rd
- Goodlette-Frank Rd and 3rd Ave S
- Goodlette-Frank Rd and 5th Ave N
- Goodlette-Frank Rd and 7th Ave N
- Goodlette-Frank Rd and 14th Ave N
- Bayshore Dr and US 41
- US 41 and 12th Ave N
- Bayshore Dr and Shoreview Dr
- Bayshore Dr and Van Buren Ave
- Thomasson Dr and Bayshore Dr
- E Naples Park
- Thomasson Dr and Lombardy Ln
- Shops at Hammock Cove
- US 41 and Rattlesnake Hammock Rd
- US 41 and Lakewood Blvd
- US 41 and Guilford Rd
- Walmart on US 41
- US 41 and Golden Gate Pkwy
- US 41 and Palm Dr
- US 41 and Guilford Rd
- Thomasson Dr and Verity Ln
- Thomasson Dr and Lombardy Ln
- Thomasson Dr and Xeric Ln
- Thomasson Ln and US 41
- US 41 and Thomasson Ln
- US 41 and Lakewood Blvd
- Bayshore Dr and US 41
- Bayshore Dr and Sabal Ct
- US 41 and Diana Ave
- Bayshore Dr and Van Buren Ave
- Bayshore Dr and Jeepers Dr
- Thomasson Dr and Bayshore Dr
- Goodlette Post Office
- Goodlette-Frank Rd and 10th AVE N
- Goodlette-Frank Rd and 5th Ave N
- Goodlette-Frank Rd and Central Ave
- Goodlette-Frank Rd and 3rd Ave S
- Davis Blvd and US 41
- Davis Blvd and Commercial Dr
- US 41 and 26th Ave N
- Davis Blvd and Shadowlawn Dr
- CAT OPS
- Fleischmann Blvd and 10th St N
- Fleischman Park
- Radio Rd and Airport Rd
- Radio Rd and Industrial Blvd
- Radio Rd and Airport Rd
- Radio Rd and Donna St
- Radio Rd and Commercial Blvd
- Radio Rd and Livingston Rd
- US 41 and Ohio Dr
- Radio Rd and San Marcos Blvd
- Radio Rd and Tina Ln
- Berkshire Commons on Radio Rd
- Radio Rd and Livingston Rd
- Radio Rd and San Marcos Blvd
- Radio Rd and Manor Blvd
- Radio Rd and Countryside Dr
- Radio Rd and Santa Clara Dr
- Radio Ln and Radio Rd
- Golden Gate Pkwy and Estuary Blvd
- US 41 and Michigan Ave
- Freedom Park on Golden Gate Pkwy
- Radio Rd and Robin Hood Cir
- Santa Barbara Blvd and Devonshire Blvd
- Santa Barbara Blvd and Prince Adrew Bvld
- Santa Barbara Blvd and Golden Gate Pkwy
- Golden Gate Pkwy and 55th St SW
- Parkway Promenade - Golden Gate Pkwy
- Golden Gate Pkwy and 50th St SW
- Golden Gate Pkwy and Coronado Pkwy
- Sunshine Blvd and Golden Gate Pkwy
- US 41 and Shady Rest Ln
- Sunshine Blvd and 20th Pl SW
- Sunshine Blvd and 18th Ct SW
- Sunshine Blvd and 17th Ave SW
- Green Blvd and Whistlers Green Cir
- Green Blvd and Waverly Pl
- Green Blvd and Santa Babara Blvd
- Santa Barbara Blvd and 17th Ave Sw
- Santa Barbara Blvd and Hunter Blvd
- Santa Barbara Blvd and Sea Grass Ln
- Santa Barbara Blvd and Coronado Pkwy
- US 41 and Andrew Dr
- US 41 and Granada Blvd
- Santa Barbara Blvd and 26th Ave SW
- Santa Barbara Blvd and Golden Gate PkwyN
- Santa Barbara Blvd and Golden Gate Pkwy
- Santa Barbara Blvd and Berkshire Rd
- Santa Barbara Blvd and Recreation Ln
- Golden Gate Pkwy and 53rd St SW
- Golden Gate Pkwy and 50th St SW
- Golden Gate Pkwy and Coronado Pkwy
- Sunshine Blvd and Golden Gate Pkwy
- Sunshine Blvd and 20th Pl SW
- US 41 and Pine Ridge Rd
- Sunshine Blvd and Sunset Rd
- Sunshine Blvd and 16th Pl SW
- Green Blvd and Whistlers Green Cir
- Green Blvd and Waverly Pl
- Green Blvd and Logan Ct
- Santa Barbara Blvd and 16th Pl SW
- Santa Barbara Blvd and Hunter Blvd
- Santa Barbara Blvd and Seagrass Ln
- Santa Barbara Blvd and Copper Leaf Ln
- US 41 and Espinal Blvd
- US 41 and Center St
- Rattlesnake Hammock Rd and Hawaii Blvd
- Rattlesnake Hammock Rd and Doral Cir
- Rattlesnake Hammock and Charlemagne Blvd
- Rattlesnake Hammock and County Barn Rd
- Rattlesnake Hammock Rd and Augusta Blvd
- Lely Manor Care on Rattlesnake Hammock
- Rattlsnake Hammock and College Park Ln
- Rattlesnake Hammock Rd and 951
- 951 and Lely Cultural Dr
- Lely Elementary
- US 41 and Myrtle Rd
- FSW
- Phys. Regional On 951
- 951 and Grand Lely Dr
- Pasedo Dr and Trail Ridge Rd
- Pasedo Dr and Koinonia Dr
- Super Walmart
- Freedom Square Plaza
- Triangle Blvd and US 41
- US 41 and Lely Resort Blvd
- Eagle Lakes Community Park
- US 41 and Ridge Dr
- US 41 and Whistler Cove Blvd
- Broward St and US 41
- Floridan Ave and Hardee St
- Floridan Ave and Holland St
- Floridan Ave and Johns St
- US 41 and St. Andrews Blvd
- US 41 and Valley Stream Dr
- Naples Towne Center
- US 41 and Thomasson Dr
- US 41 and Treviso Bay Blvd
- US 41 and Pelican Bay Blvd
- Floridan Ave and Johns St
- Floridan Ave and Holland St
- Floridan Ave and Hardee St
- Floridan Ave and Broward St
- US 41 and Treetops Dr
- US 41 and South West Blvd
- US 41 and Barefoot Williams Rd
- US 41 and Habitat Rd
- Triangle Blvd and US 41
- 951 and Veronawalk Blvd
- US 41 and Vanderbilt Beach Rd
- 951 and Sabal Palm Rd
- Rattlesnake Hammock Rd and 951
- Rattlesnake Hammock Rd and College Pk Ln
- Rattlesnake Hammock and Huntington Woods
- Rattlesnake Hammock and Royal Wood Blvd
- Rattlesnake Hammock and County Barn Rd
- Rattlesnake Hammock and Charlemagne Blvd
- Rattlesnake Hammock Rd and Hawaii Blvd
- Davis Blvd and Airport Rd
- Davis Blvd and Lakewood Blvd
- US 41 and Mercato
- Davis Blvd and Kings Way
- Davis Blvd and E Crowne Pointe Blvd
- Davis Blvd and Heritage Trail
- Davis Blvd and Unity Way
- Davis Blvd and Firano Dr
- 951 and City Gate Blvd
- 951 and 17th Ave Sw
- Golden Gate Blvd and Weber Blvd
- Estates Library on Golden Gate Blvd
- Wilson Blvd and Golden Gate Blvd
- US 41 and Pelican Marsh Blvd
- Wilson Blvd and 24th Ave NE
- Immokalee Rd and Randall Blvd
- Immokalee Rd and Orange Tree Blvd
- Immokalee Rd and Oil Well Rd
- Immokalee Rd and 39th Ave NE
- Seminole Casino
- Immokalee Rd and 39th Ave NE
- Immokalee Rd and Oil Well Rd
- Immokalee Rd and Randall Blvd
- Wilson Blvd and 24th Ave NW
- US 41 and 104th Ave N
- Wilson Blvd and Golden Gate Blvd
- Golden Gate Blvd and 13th St
- Golden Gate Blvd and Weber Blvd
- 951 and 13th Ave SW
- 951 and Green Blvd
- 951 and 20th Pl SW
- 951 and Golden Gate Pkwy
- 951 and Magnolia Pond Dr
- Davis Blvd and Bedzel Dr
- US 41 and Shadowlawn Dr
- US 41 and 108th Ave N
- Davis Blvd and Wildwood Lakes Blvd
- Davis Blvd and Santa Barbara Blvd
- Davis Blvd and Glen Eagle Blvd
- Davis Blvd and Ospreys Landing
- Davis Blvd and Kings Way
- Davis Blvd and Kings Way
- Davis Blvd and Lakewood Blvd
- Davis Blvd and Pine Acre
- Golden Gate Pkwy and 951
- Golden Gate Pkwy and 43rd Ln SW
- Immokalee Rd and US 41
- Golden Gate Pkwy and Coral Palms
- Logan Blvd and Tallwood Way
- Logan Blvd and Dogwood Way
- Golden Gate Parkway and Sunshine Blvd
- Golden Gate Parkway and 44th St SW
- Golden Gate Pkwy and 42nd St SW
- Pine Ridge Rd and Vineyards Blvd
- Phys. Reg on Pine Ridge Rd
- Super Walmart
- Immokalee Rd - Riverchase Blvd
- Farm Worker Way
- E Main St and New Harvest Rd
- E Main St and CR846
- E Main St and 9th St E
- N 1st St and Pine St
- US 41 and 111th Ave N
- and 331 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 | 30.1 | first check |
| 2026-07-30 | 30.1 | no change |
| 2026-07-31 | 30.1 | no change |
| 2026-08-01 | 30.1 | 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
15 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 2039 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning4473 instances
Some route lines list the same point twice in a row.
Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)
Finding code: equal_shape_distance_same_coordinates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning581 instances
581 of 581 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)
- Warning487 instances
487 of 487 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)
- Warning208 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning96 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Finding code: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning71 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)
- Warning12 instances
Same stop and route url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_stop_and_route_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: same_stop_and_route_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 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)
- Warning1 instance
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules (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)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (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.)
Finding code: scorecard_no_fare_data · 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 Not ready
Resolve this before you certify on the D-10. Service data expired 2039 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 2039 days ago, so FTA would find the link out of date.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
- agency_id equals your NTD ID (optional) Not checked yet
- This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
- shapes.txt covers your trips Ready
- All 487 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed is close to the conformance mark. Service data expired 2039 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 2039 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.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
- Correctness 42 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
- Freshness 0 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
- Rider experience 38 / 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/collier-area-transit-cat/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.