Prep for a call: printable one-page brief · For your board packet: printable one-pager · Fix log: every issue this feed has cleared · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
Collier Area Transit (CAT)
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 32% of all tracked agencies and 45% of large agencies. Operates 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.1, validator 8.0.1.
Checked for changes 15 minutes ago; last changed 15 minutes 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 with a validity window that reaches at least 60 days out.Likely your export tool
Service data runs out in 15 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
⏱ One export setting.worth about +65 points
Agencies here usually clear this within about 1 week (based on 61 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
1112 of 1112 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
689 of 689 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 with a validity window that reaches at least 60 days out. · 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. See this feed's dated fix log.
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. See this feed's dated fix log.
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. See this feed's dated fix log.
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 6 kinds of issue across 45 instances (0 error, 39 warning, 6 informational).
Service data runs out in 15 day(s). Publish an updated feed soon or riders will lose trip planning.
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.
3 accessibility depth signals
2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (11, 14).
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.
710 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("951 and Bucks Run Dr", "S 5th St and Carver", "66th St SW", 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.
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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 11 (red)
- 12 (yellow)
- 121 (white)
- 13 (orange)
- 14 (teal)
- 15 (purple)
- 16 (white)
- 17 (gray)
- 19 (blue)
- 20 (pink)
- 21 (white)
- 22 (white)
- 23 (red)
- 24 (brown)
- 25 (green)
- 27 (white)
| Route | Type | Line color |
|---|---|---|
| 11 Us 41 - Creekside | Bus | red |
| 12 Airport-Creekside | Bus | yellow |
| 121 Express Immokalee - Marco Island | Bus | white |
| 13 Nch-Coastland Mall | Bus | orange |
| 14 Bayshore -Coastland Mall | Bus | teal |
| 15 Golden Gate City | Bus | purple |
| 16 Golden Gate City | Bus | white |
| 17 Rattlesnake - Fsw | Bus | gray |
| 19 Golden Gate Estates - Immokalee | Bus | blue |
| 20 Pine Ridge | Bus | pink |
| 21 Marco Island Circulator | Bus | white |
| 22 Immokalee Circulator | Bus | white |
| 23 Immokalee Circulator | Bus | red |
| 24 Us 41 East - Charlee Estates | Bus | brown |
| 25 Golden Gate Pkway - Goodlette Rd | Bus | green |
| 27 951-Immokalee Rd | Bus | white |
This feed has 1112 stops.
List every stop
- GOVT Center
- 3rd Ave N
- Vanderbilt Rd
- Conner Park
- Wiggins Pass Beach
- Vanderbilt Beach
- Orange Blossom
- Arbour Walk Cir
- C Blvd
- Naples Blvd
- Pine Ridge Cr
- Clubhouse Dr
- Pine Wood Cir
- Poinciana Dr
- Poinciana Elem
- 5th Ave N
- Golden Gate Pkw
- Longboat Dr
- Horseshoe Dr
- Prospect Ave
- Radio Rd
- North Rd (DMV)
- Estey Ave
- Connecticut Ave
- Glades Blvd
- US 41
- 8th Ave N
- Airport Pulling
- Shadowlawn Dr
- Brookside Dr
- Market St
- San Marco Rd
- 3rd Ave S
- 5th Ave N
- 7th Ave N
- 14th Ave N
- US 41
- 12th Ave N
- Shoreview Dr
- Van Buren Ave
- Bayshore Dr
- E Naples Park
- Lombardy Ln
- Hammock Cove
- Rattlesnake Rd
- Lakewood Blvd
- Guilford Rd
- Walmart US 41
- Golden Gate Pkw
- Palm Dr
- Guilford Rd
- Verity Ln
- Lombardy Ln
- Xeric Ln
- US 41
- Thomasson Ln
- Lakewood Blvd
- US 41
- Sabal Ct
- Diana Ave
- Van Buren Ave
- Jeepers Dr
- Bayshore Dr
- Goodlette Post
- 10th AVE N
- 5th Ave N
- Central Ave
- 3rd Ave S
- US 41
- Commercial Dr
- 26th Ave N
- Shadowlawn Dr
- CAT OPS
- 10th St N
- Fleischman Park
- Airport Rd
- Industrial Blvd
- Airport Rd
- Donna St
- Commercial Blvd
- Livingston Rd
- Ohio Dr
- San Marcos Blvd
- Tina Ln
- Berkshire Comm
- Livingston Rd
- San Marcos Blvd
- Manor Blvd
- Countryside Dr
- Santa Clara Dr
- Radio Rd
- Estuary Blvd
- Michigan Ave
- Freedom Park
- Robin Hood Cir
- Devonshire Blvd
- Prince Adrew Bd
- Golden Gate Pkw
- 55th St SW
- Golden Gate
- 50th St SW
- Coronado Pkwy
- Golden Gate Pkw
- Shady Rest Ln
- 20th Pl SW
- 18th Ct SW
- 17th Ave SW
- Whistlers Green
- Waverly Pl
- Santa Babara Bd
- 17th Ave Sw
- Hunter Blvd
- Sea Grass Ln
- Coronado Pkwy
- Andrew Dr
- Granada Blvd
- 26th Ave SW
- Golden Gate N
- Golden Gate Pk
- Berkshire Rd
- Recreation Ln
- 53rd St SW
- 50th St SW
- Coronado
- Golden Gate Pkw
- 20th Pl SW
- Pine Ridge Rd
- Sunset Rd
- 16th Pl SW
- Whistlers Green
- Waverly Pl
- Logan Ct
- 16th Pl SW
- Hunter Blvd
- Seagrass Ln
- Copper Leaf Ln
- Espinal Blvd
- Center St
- Hawaii Blvd
- Doral Cir
- Charlemagne Blv
- County Barn Rd
- Augusta Blvd
- Lely Manor Care
- College Park Ln
- 951
- Lely Cultural
- Myrtle Rd
- Phys. Regional
- Grand Lely Dr
- Trail Ridge Rd
- Koinonia Dr
- Super Walmart
- Freedom Square
- Lely Resort Bd
- Eagle Lakes
- Ridge Dr
- Whistler Cove
- US 41
- Hardee St
- Holland St
- Johns St
- St. Andrews Bd
- Valley Stream
- Naples Towne Ct
- Thomasson Dr
- Treviso Bay Bd
- Pelican Bay Bd
- Johns St
- Holland St
- Hardee St
- Broward St
- Treetops Dr
- South West Blvd
- Barefoot Rd
- Habitat Rd
- Veronawalk Blvd
- VanderbiltBeach
- Sabal Palm Rd
- 951
- College Pk Ln
- Huntington Wood
- Royal Wood Blvd
- County Barn Rd
- Charlemagne Bd
- Hawaii Blvd
- Airport Rd
- Lakewood Blvd
- Mercato
- Kings Way
- E Crowne Pointe
- Heritage Trail
- Unity Way
- Firano Dr
- City Gate Blvd
- 17th Ave Sw
- Weber Blvd
- Estates Library
- Golden Gate Bd
- Pelican Marsh
- 24th Ave NE
- Randall Blvd
- Orange Tree Bd
- Oil Well Rd
- Seminole Casino
- Randall Blvd
- 24th Ave NW
- 104th Ave N
- Golden Gate Bd
- 13th St
- Weber Blvd
- 13th Ave SW
- 20th Pl SW
- Golden Gate Pkw
- Magnolia Pond
- Madrid Cir
- Radio Rd
- Shadowlawn Dr
- 108th Ave N
- Wildwood Lakes
- Santa Barbara
- Glen Eagle Blvd
- Ospreys Landing
- Kings Way
- Kings Way
- Lakewood Blvd
- Pine Acre
- 951
- 43rd Ln SW
- US 41
- Coral Palms
- Tallwood Way
- Dogwood Way
- Sunshine Blvd
- 44th St SW
- 42nd St SW
- Vineyards Blvd
- Phys. Reg
- Super Walmart
- Riverchase Blvd
- Farm Worker Way
- New Harvest Rd
- CR846
- 9th St E
- Pine St
- 111th Ave N
- Kissimmee St
- Nassau St
- Marrion Feather
- Carson Rd
- and 862 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
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 49.7 | first check |
| 2026-06-20 | 49.7 | no change |
| 2026-06-21 | 47.9 | down 1.8 |
| 2026-06-22 | 49.7 | up 1.8 |
| 2026-06-23 | 49.7 | no change |
| 2026-06-24 | 49.2 | down 0.5 |
| 2026-06-25 | 49.2 | no change |
| 2026-06-26 | 49.2 | no change |
| 2026-06-27 | 49.2 | no change |
| 2026-06-28 | 47.5 | down 1.7 |
| 2026-06-29 | 49.2 | up 1.7 |
| 2026-06-30 | 49.2 | no change |
| 2026-07-01 | 49.2 | no change |
| 2026-07-02 | 49.2 | no change |
| 2026-07-04 | 49.2 | no change |
| 2026-07-05 | 48.8 | down 0.4 |
| 2026-07-06 | 49.2 | up 0.4 |
| 2026-07-07 | 49.2 | no change |
| 2026-07-08 | 49.2 | no change |
| 2026-07-09 | 49.2 | 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.
The feed file was re-published since 2026-07-08.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
- Warning1112 instances
1112 of 1112 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)
- Warning689 instances
689 of 689 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)
- Warning66 instances
66 of 689 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)
- Warning31 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)
- Warning4 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)
- Warning3 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)
- Warning1 instance
A file GTFS asks for (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
Service data runs out in 15 day(s).
When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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)
- Info5 instances
Trip headsign matches intermediate stop (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'trip_headsign_matches_intermediate_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules 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)
NTD certification readiness Needs attention
This feed is close to NTD-ready. Service data runs out in 15 days; renew before you certify.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Needs attention
- Service data runs out in 15 days; renew before you certify.
- 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 689 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 runs out in 15 days; renew to qualify. 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 runs out in 15 days; renew to qualify.
- 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.
- 4 of 556 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.
At risk for the Google and Apple Maps four-week coverage bar. This feed has 15 days of service left. Maps needs at least four weeks (28 days) of upcoming service, so your agency will fall out of trip planners soon. Re-export with a longer calendar.
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 81 / 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 10 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 36 / 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/collier-area-transit-cat-2259/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.