Feed status · checked 2026-08-01
CATABUS
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Pennsylvania.
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 16 hours ago; last fetch returned HTTP 403.
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
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 1806 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
Re-generate shape distances in your export; flag to your vendor if it persists.Likely your export tool
Some trips have stop times whose distances along the route go backwards. Apps can show buses jumping backwards or mis-order stops.
⏱ Usually an export-tool fix, not hand editing.worth about +24 points in its category
Review the rule documentation for 'invalid_phone_number' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid phone number (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points in its category
This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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 1806 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
- Some trips have stop times whose distances along the route go backwards.
- Next action
- Re-generate shape distances in your export; flag to your vendor if it persists.
- 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
- Invalid phone number (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'invalid_phone_number' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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. This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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.
Re-generate shape distances in your export; flag to your vendor if it persists.
Make the change. This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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.
Review the rule documentation for 'invalid_phone_number' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Make the change. This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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 1806 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
- 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
This feed is served from the TransitFeeds archive, which is no longer maintained. The most useful request is publishing the current feed from a live URL, then these fixes. Each fix names the validator notice and a guide link.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 13 kinds of issue across 5703 instances (121 error, 5562 warning, 20 informational).
Service data ended 1806 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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (W, Rl).
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.
291 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("N Atherton St at Hillcrest Ave", "1101 N. Atherton St (CVS)", "801 W Aaron Dr (Park Forest Apartments)", 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 359 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.
- V (purple)
- R (white)
- K (blue)
- W (brown)
- Bl (blue)
- Rl (red)
- N (green)
- Hm (pink)
- P (orange)
| Route | Type | Line color |
|---|---|---|
| V | Bus | purple |
| R | Bus | white |
| K | Bus | blue |
| W | Bus | brown |
| Bl | Bus | blue |
| Rl | Bus | red |
| N | Bus | green |
| Hm | Bus | pink |
| P | Bus | orange |
List every stop
- Boalsburg Pike at St. Josephs school
- 121 Mary Elizabeth St
- Warner Blvd at Boalsburg Med Offices
- S Atherton St at Circle Dr
- S Atherton St at Warnock Rd
- S. Atherton St at Hubler Rd (Inbound)
- South Atherton Street at Scenery Drive
- E. College Ave at S. Allen Street
- 801 W Aaron Dr (Park Forest Apartments)
- Burrowes Rd at Deike Building
- Burrowes Rd at Waring Commons
- Pattee Transit Center Eastbound
- Curtin Rd at Pavilion Theatre
- E College Ave at Atherton Hall
- Bigler Rd at Computer Building
- Shortlidge Rd at White Building
- Pollock Rd at Millennium Science Com
- Curtin Rd at McCoy Natatorium
- Curtin Rd at Shields Building
- 1003 W Aaron Dr (Copper Beech)
- University Dr at Jordan Center Gate D
- Curtin Rd at the Intramural Building
- East Halls at Curtin Hall
- South Atherton at Creekside Plaza
- 1661 S Atherton St (IHOP)
- Opposite 1031 E College Ave
- E College Ave at Your Building Center
- E College Ave at Squirrel Dr Outbound
- Walmart - Inbound
- Ross/Bed Bath & Beyond
- Nittany Mall Main Entrance
- E College Av at Hickeys
- E College Ave at Puddintown Rd
- 1031 East College Ave (Lettermans)
- W Whitehall Road at CATA
- W Beaver Ave at S Barnard St
- W College Ave at N Barnard St
- South Burrowes St at Calder Way
- Colonnade Blvd at Home Goods
- Colonnade Blvd at Target/Dicks
- Colonnade Blvd Opposite Kohls
- Opposite 240 Toftrees Ave
- 240 Toftrees Ave (Turtle Creek Apts)
- 301 Toftrees Ave
- Opposite 301 Toftrees Ave
- 359 Toftrees Ave (Parkgate Apartments)
- 350 Toftrees Ave (Turtle Creek Apts)
- Cricklewood Dr at N Barkway Lane
- Cricklewood Dr at S Barkway Lane
- Cricklewood Dr at Wilts Lane Outbound
- Cricklewood Dr at Wilts Lane Inbound
- 541 Cricklewood Dr
- 711 Cricklewood Dr
- Opposite 711 Cricklewood Dr
- Cricklewood Dr at the American Ale House
- Cricklewood Dr at Cricklewood Apts
- Opposite 910 Cricklewood Dr
- 910 Cricklewood Dr
- Presidents Dr at Varsity Lane Inbound
- Presidents Dr at Varsity Lane Outbound
- Village at Penn State Inbound
- Village at Penn State Outbound
- Cricklewood Dr at Cricklewood Circle
- Fox Hollow Rd at Orchard Rd Inbound
- Fox Hollow Rd at Orchard Rd Outbound
- Porter Rd at Beaver Stadium East
- Porter Rd at the Visitors Center
- Porter Rd at Jordan East Parking
- Hastings Rd at Lot 43 East
- Hastings Rd at Forest Research Lab
- N Atherton St at Walker Building
- Curtin Rd at Bryce Jordan Center
- W College Ave at N Sparks St
- W Beaver Ave at S Sparks St
- W College Ave at N Butz St
- W College Ave at Buckhout St
- W College Ave near Corl St
- W College Ave at Hoy St
- 1445 W College Ave
- 1400 W College Ave
- Opposite 1506 W College Ave
- 1506 W College Ave
- 2110 W College Ave
- 2111 W College Ave
- W College Ave at Holly Circle Inbound
- W College Ave at Chelsea Lane Inbound
- W College Ave at Chelsea Lane Outbound
- W College Ave at Bristol Ave Inbound
- W College Ave at Bristol Ave Outbound
- Enterprise Dr at Bristol Ave
- Opposite 3035 Enterprise Dr
- 3075 Enterprise Drive
- Enterprise Dr at Cato Ave
- Cato Ave at Enterprise Dr
- Cato Ave at Research Dr
- 200 Shiloh Rd
- Premiere Dr at the UEC 12 Theatre
- Dreibelbis St at the Summit at Shiloh
- 2601 E College Ave
- E College Ave at Struble Rd
- E College Ave at Nittany Commons
- E College Ave opp Nittany Commons
- E College Ave at Limerock Terrace
- Pike St at Limerock Terrace Inbound
- Pike St at Limerock Terrace Outbound
- Pike St at Hickory Lane Inbound
- Pike St at Hickory Lane Outbound
- 542 Pike St
- 537 Pike St
- Pike St at Dale St Outbound
- Pike St at Dale St Inbound
- Pike St at Mary St Inbound
- Pike St at Mary St Outbound
- Elmwood St at Elm St
- 700 Elmwood St
- Elmwood St at Clover Rd
- Elmwood St at Hillview Ave
- 200 Elmwood St
- 201 Elmwood St
- Mount Nittany Medical Center
- Centre Med Science Bldg
- Park Ave at Orchard Rd Westbound
- Park Ave at Orchard Rd Eastbound
- Curtin Rd at Stadium West Parking Lot
- Curtin Rd at Visual Arts Building
- Pattee Transit Center Westbound
- Burrowes Rd at Rec Hall
- Burrowes Road at Westgate Building
- S Burrowes St at the James Elliott Bldg
- Beaver Ave at Schlow Library/CATA Office
- S Pugh St at E College Ave
- Opposite 240 S Pugh St
- 240 S Pugh St (Days Inn)
- S Pugh St at E Nittany Ave
- S Pugh St at E Fairmount Ave
- S Pugh St at E Hamilton Ave Inbound
- S Pugh St at E Hamilton Ave Outbound
- S Pugh St at Waring Ave
- 909 S Pugh St
- 1015 S Pugh St
- 1006 S Pugh St
- Easterly Pkwy at Old Boalsburg Rd
- 1218 S Allen St
- S Pugh St at E Ellen Ave
- 1248 S Atherton St (Citizens Bank)
- S Pugh St at Bradley Ave
- 1306 S Atherton St
- S Atherton St at Norma Street
- S Atherton St at Whitehall Rd
- S Atherton St at Science St
- Science St. at the Ramada
- East Marylyn Ave at Foxdale Village
- Rolling Ridge Drive at Hills Plaza
- 301 Rolling Ridge Dr (Mt Nittany Res)
- Rolling Ridge Dr at Hills Plaza South
- Opposite 383 Rolling Ridge Dr
- Opposite 501 Rolling Ridge Dr
- 1100 W Aaron Dr (Copper Beech)
- Windmere Dr at Wellington Dr
- Radnor Rd at Regent Ct
- Geisinger Medical Center at Scenery Park
- S Atherton Street at Highland Alley
- S Atherton St at Fairmount Ave Outbound
- S Atherton St at W Fairmount Ave Inbound
- S. Atherton St. at Pizza Hut
- 805 S Atherton St
- Research Drive at CATA
- 720 W Aaron Dr (Aaron Village)
- S Atherton St at Centre Lane
- Waupelani Dr at S Allen St
- Waupelani Dr at The Retreat
- Waupelani Dr at Executive House
- Waupelani Dr at Lions Gate Apts
- 445 Waupelani Dr (Nittany Gardens)
- 450 Waupelani Dr (Hearthside)
- Waupelani Dr at Southgate Dr Inbound
- Waupelani Dr at Southgate Dr Outbound
- 712 Southgate Dr
- Southgate Dr at Highlandon Ct
- Southgate Dr at Ashwicken Ct
- Southgate Dr at Blue Course Dr
- N Atherton St at Arbor Way
- 215 Blue Course Dr (Near Shell)
- Blue Course Dr at BB&T Bank
- Northland Center Outbound
- Northland Center Inbound
- Blue Course Dr near Teaberry Lane
- Blue Course Dr at Blue Course Commons
- Havershire Blvd. at The Heights
- Havershire Blvd. across from The Heights
- Havershire Blvd. at Northwick (Inbound)
- Havershire Blvd. at Northwick (Outbound)
- Havershire Blvd. at Rushcliff (Outbound)
- Havershire Blvd. at Rushcliff (Inbound)
- Circleville Rd at Farmstead Lane Inbound
- Circleville Rd at Farmstead Ln Outbound
- Valley Vista Dr at Oak Hill Apts Oubound
- Valley Vista Dr at Oak Hill Apts Inbound
- Valley Vista Dr at Bachman Lane Outbound
- Valley Vista Dr at Bachman Lane Inbound
- Valley Vista at Devonshire Outbound
- Valley Vista Dr at Devonshire Inbound
- Valley Vista at Oakley Dr Inbound
- 1224 N Atherton St - Discovery Space
- Amblewood Way at School Drive
- Carnegie Dr at Vista Lofts
- Carnegie Drive at Valley Vista Drive
- Valley Vista Dr Opp Lowes Center
- Valley Vista Drive at Lowes Center
- N Atherton St at Mitchell Ave Inbound
- Colonnade Blvd at Chicos
- Colonnade Blvd at Wegmans
- Martin St at Park Crest Lane Inbound
- Martin St at Park Crest Lane Outbound
- 1400 Martin St (Parkcrest Terrace)
- Opposite 1400 Martin St
- Martin Street at Herman Drive
- 1471 Martin St (Weis)
- 1521 Martin St (Northland Bowl)
- Park Lane at Aaron Dr
- Park Lane at Devonshire Dr
- Park Lane at Cornwall Rd Inbound
- Park Lane at Cornwall Rd Outbound
- Park Lane at Sierra Lane
- Park Lane at Shannon Lane
- Park Lane at Park Forest Ave Inbound
- Park Lane at Park Forest Ave Outbound
- Park Forest Ave at Northbrook Greens
- Park Forest Ave Opposite Northbrook
- Park Forest Ave at N Atherton Outbound
- Park Forest Ave at N Atherton Inbound
- Trader Joes Plaza
- 1870 North Atherton Street
- N Atherton St at Chick-Fil-A
- N Atherton St at Colonnade Blvd
- Middle of Oakwood Ave Outbound
- 658 Oakwood Ave
- Vairo Blvd at Vairo Village (Upper)
- Vairo Blvd opposite Vairo Village(Upper)
- Vairo Blvd opposite Vairo Village(lower)
- Vairo Blvd at Vairo Village(lower)
- Vairo Blvd at Tremont Inbound(lower)
- Vairo Blvd at Tremont Inbound upper
- Vairo Blvd at Tremont Outbound
- Vairo Blvd at The Pointe Inbound
- Vairo Blvd at The Pointe Outbound
- Vairo Blvd at The Bryn Inbound
- Vairo Blvd at The Bryn Outbound
- Williamsburg Sq. - Holiday Inn/Spring Hi
- Oakwood Ave at Texas Roadhouse
- and 109 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 | 22.0 | first check |
| 2026-07-30 | 22.0 | no change |
| 2026-07-31 | 22.0 | no change |
| 2026-08-01 | 22.0 | 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
17 findings, ordered by severity.
Show every finding
- Error120 instances
Some trips have stop times whose distances along the route go backwards.
Apps can show buses jumping backwards or mis-order stops.
Fix: Re-generate shape distances in your export; flag to your vendor if it persists. (Usually an export-tool fix, not hand editing.)
Finding code: decreasing_or_equal_stop_time_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Invalid phone number (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_phone_number' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_phone_number · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Service data ended 1806 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 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)
- Warning920 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)
- Warning856 instances
856 of 856 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)
- Warning359 instances
359 of 359 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)
- Warning155 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)
- Warning9 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)
- Warning1 instance
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.)
Finding code: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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)
- 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)
- Info19 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Finding code: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · 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).
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. 2 validator errors to resolve. Service data expired 1806 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 2 validator errors to resolve.
- Current Not ready
- Service data expired 1806 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 856 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. 2 validator errors to resolve. Service data expired 1806 days ago. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 2 validator errors to resolve.
- Current Not yet
- Service data expired 1806 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. The feed also carries 121 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
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 13 / 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 52 / 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/centre-county-transit-authority-cata/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.