Feed status · checked 2026-08-23
Portage Area Regional Transportation Authority (PARTA)
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-08-22
Catalogued in Ohio.
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 50 minutes ago; last changed 50 minutes ago.
Measured 3 of 4 score categories from the feed URL on file (publisher not verified).
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 configured feed URL. Publisher ownership of that URL is not verified.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
1036 of 1051 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
3159 of 3159 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
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.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
⏱ A small file for most flat-fare systems.worth about +15 points in its category
This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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
- 1036 of 1051 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
- 3159 of 3159 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
- Feed evidence
- The feed contains no fare information.
- Next action
- 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.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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. See this feed's finding-clearance log.
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. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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. See this feed's finding-clearance log.
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. · Read the fix guide
Make the change. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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. See this feed's finding-clearance log.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 30 days.
- Published accessibility data
- Accessibility information is stated for 1.4% 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 Passio a fix request
This feed is generated by your Passio system. Copy this and send it to your Passio contact; the fixes apply to the route and stop data behind your AVL setup. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 6 kinds of issue across 4625 instances (0 error, 4612 warning, 13 informational).
Service data covers the next 30 days.
1% of stops state wheelchair accessibility (1% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
1% of stops state accessibility (1% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
11 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (51, 100, DR, 46, 35, 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.
913 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("1000 - MANTUA & STINAFF NB", "1002 - SR303 & ST. MICHAEL'S EB", "1003 - SR303 & ST. MICHAEL'S WB", 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 1051 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.
- 70 (gray)
- 45 (yellow)
- 100 (brown)
- 40 (yellow)
- 80 (blue)
- 30 (red)
- 85 (blue)
- 35SAT (red)
- 90 (pink)
- 35 (red)
- 57 (red)
- 51 (blue)
- 55 (green)
- 59 (purple)
- 58 (gray)
| Route | Type | Line color |
|---|---|---|
| 70 WINDHAM/GARRETTSVILLE | Bus | gray |
| 45 SUBURBAN SOUTH | Bus | yellow |
| 100 CLEVELAND EXPRESS | Bus | brown |
| 40 SUBURBAN NORTH | Bus | yellow |
| 80 RAVEN WEST | Bus | blue |
| 30 INTERURBAN WEST | Bus | red |
| 46 DOWNTOWNER | Bus | purple (no shape in feed) |
| 85 RAVEN EAST | Bus | blue |
| 35SAT SATURDAY INTERURBAN EAST | Bus | red |
| 90 AKRON EXPRESS | Bus | pink |
| 35 INTERURBAN EAST | Bus | red |
| 57 STADIUM LOOP | Bus | red |
| 51 CAMPUS LOOP | Bus | blue |
| 55 COMMUTER SHUTTLE | Bus | green |
| 59 STADIUM NIGHT LOOP | Bus | purple |
| 58 SUMMIT EAST/FRONT CAMPUS | Bus | gray |
| DR DART | Bus | black (no shape in feed) |
List every stop
- KSU DIX STADIUM 2
- KSU DIX STADIUM 3
- KSU DIX STADIUM 4
- KSU SUMMIT EAST
- KSU SUMMIT & TOWNHOMES WB
- KSU SUMMIT & WHITEHALL TERRACE WB
- KEN SUMMIT & LOOP WB
- KSU SUMMIT & E CAMPUS CTR WB
- KSU SUMMIT & MATH/SCIENCE WB
- KSU STUDENT CENTER
- 963 - KENT CENTRAL GATEWAY SOUTH
- KEN MAIN & LINCOLN EB
- KSU ARCHITECTURE & ENV DESIGN SB
- KSU FRANKLIN HALL
- KSU CARTWRIGHT HALL
- KSU MOULTON HALL
- KSU C-MIDWAY EB
- KSU VERDER HALL
- KSU CTR FOR PERF ARTS EAST
- KSU THEATRE & JACKSON EB
- KSU CENTENNIAL F
- KSU JACKSON & LOOP EB
- KSU LOOP & LEEBRICK SB
- KSU VAN CAMPEN HALL
- KSU LOOP & RHODES SB
- KSU SUMMIT & WHITEHALL TERRACE EB
- KSU SUMMIT & TOWNHOMES EB
- KEN SUMMIT & PARTA MAIN
- KSU DIX STADIUM 1
- KSU BOWMAN HALL
- KSU SCHWARTZ CENTER EB
- KSU SUMMIT & FRATERNITY EB
- KSU RECREATION & WELLNESS CENTER
- KEN SUMMIT & LOOP EB
- KSU ALLERTON BALL FIELDS
- RAV UH PORTAGE MEDICAL CENTER
- RAV CHESTNUT & VA SB
- RAV CHESTNUT & RAVENNA HS SB
- RAV CHESTNUT & LINCOLN SB
- RAV CHESTNUT & CENTRAL SB
- RAV CHESTNUT & HIGHLAND SB
- RAV CHESTNUT & LOCUST SB
- RAV MAIN & PARKWAY WB
- RAV MAIN & SYCAMORE WB
- RAV MAIN & FMLY DLR WB
- RAV MAIN & DIAMOND WB
- RAV MAIN & OAKWOOD WB
- RAV MAIN & HILLCREST WB
- RAV MAIN & SCRANTON WB
- RAV SR59 & DLR GEN WB
- RAV SR59 & HILL WB
- RAV SR59 & BRADY LK WB
- RAV SR59 & MENOUGH WB
- RAV SR59 & VLG EST WB
- RAV SR59 & PMHA WB
- RAV SR59 & HVN OF PRTG WB
- RAV SR 59 & BIRDIE SHACK WB
- RAV SR59 & AKRN CHLDRNS WB
- RAV SR59 & POWDERMILL WB
- RAV SR59 & ERIE WB
- KEN SR59 & KLABEN WB
- KEN SR59 & SR261 WB
- KEN SR59 & RHODES WB
- KEN MAIN & 6TH WB
- KEN MAIN & DALE WB
- KEN MAIN & HORNING WB
- KEN MAIN & LINDEN WB
- KEN MAIN & LINCOLN WB
- 962 - KENT CENTRAL GATEWAY NORTH
- RAV MEADOWVIEW PLZ
- RAV PEBBLEBROOK APTS
- 478 - RAVENNA WALMART
- KEN ASHTON & CMPS PT OFFICE
- KEN ALPHA & CAMPUS POINT
- KSU LOOP AND WKSU NB
- KSU LOOP AND RHODES NB
- KSU EASTWAY & TWIN TOWERS WB
- KSU SENHAUSER AND TWIN TOWERS
- KSU SENHAUSER AND LEEBRICK NB
- KSU LEEBRICK AND LOOP EB
- KSU LOOP AND UNIVERSITY OAKS NB
- KSU JACKSON & CENTENNIAL F WB
- KSU JACKSON AND THEATRE NB
- KSU THEATRE AND CENT FOR PERF ARTS WB
- KSU THEATRE AND NIXSON WB
- KSU MIDWAY AND STUDENT CENTER REAR
- KSU MIDWAY AND CENTENNIAL A NB
- KSU TRI-TOWERS
- KSU KORB HALL
- KSU EASTWAY CENTER
- KSU DEWEESE HEALTH CENTER
- KSU ALUMNI BUILDING
- 578 - STR MARKET SQ DR AND MARKET SQ PLZ SB
- 817 - SOUTHGATE TRANSIT CENTER
- 1063 - ONTARIO AND CARNEGIE NB
- 581 - W 6TH & SUPERIOR
- 1062 - ST CLAIR AND 9TH EB
- 1034 - CHESTER AT GREYHOUND EB
- 1061 - CHESTER AND 24TH EB
- 1060 - EUCLID AND 100TH EB
- 1059 - 105TH AND MLK NB
- 964 - MAGNOLIA AND LOUIS STOKES VA
- 1033 - E 21ST AT STEPHANIE TUBBS-JONES SB
- KEN WATER & ERIE NB
- KEN MAIN & WATER WB
- KEN MAIN & RIVER WB
- KEN MAIN & MANTUA WB
- KEN MAIN & PROSPECT WB
- KEN MAIN & FOREST WB
- KEN MAIN & STOW WB
- KEN MAIN & STONEWATER WB
- KEN MAIN & FRANCIS WB
- KEN MAIN & SPAULDING WB
- KEN SPAULDING NORTH
- KEN SPAULDING & SLVR MDWS NB
- KEN SLVR MDWS & GARTH NB
- KEN SLVR MDWS & CAROL NB
- KEN SLVR MDWS & ANITA NB
- KEN LAWRENCE & BART NB
- KEN ANITA & SIMON EB
- KEN SLVR MDWS NORTH
- KEN SLVR MDWS & FAIRCHILD NB
- KEN FAIRCHILD & RIVERWOOD WB
- STO GRAHAM & STOW HS WB
- STO GRAHAM & FISHCREEK WB
- STO FISHCREEK & OREGON PLZ SB
- STO FISHCREEK & CNTRY MNR SB
- STO FISHCREEK & LAKE RUN SB
- STO FISHCREEK & ALDI SB
- 1066 - STOW MEIJER
- STO KENT & STO-KENT PLZ WB
- 622 - STOW TARGET
- STO KENT & STOW GLEN WB
- STO KENT & TACO BELL WB
- STO KSU AIRPORT
- STO KENT & TACO BELL EB
- KEN MAIN & HORNING EB
- KEN MAIN & KENT UCC EB
- KEN MAIN & DALE EB
- KEN MAIN & HOLLY PARK EB
- KEN 6TH & DRUGMART NB
- KEN 6TH & RUGG NB
- KEN 6TH & OHIO NB
- KEN OHIO & 5TH NB
- KEN OHIO & 3RD NB
- KEN LAKE & GRAHAM WB
- KEN LAKE & ROCKWOOD APTS WB
- KEN LAKE & LAKE ST APTS WB
- KEN LAKE & HARVEY WB
- KEN LAKE & WOODSIDE WB
- KEN LAKE & MARVIN WB
- KEN LAKE & LOCK WB
- KEN LAKE & WATER WB
- KEN HUDSON & CUYAHOGA NB
- KEN HUDSON & STINAFF NB
- KEN HUDSON & CARTHAGE NB
- KEN HUDSON & ROOSEVELT NB
- 314 - KENT ROOSEVELT HS
- STO KENT & STO-KENT PLZ EB
- STO KENT & MARSH EB
- STO FISHCREEK & KENT NB
- STO FISHCREEK & GREENLAWN NB
- STO FISHCREEK & LAKE RUN NB
- STO FISHCREEK & CNTRY MNR NB
- STO FISHCREEK & OREGON PLZ NB
- STO GRAHAM & FISHCREEK EB
- STO GRAHAM & STOW HS EB
- KEN FAIRCHILD & RIVERWOOD EB
- KEN SLVR MDWS & FAIRCHILD SB
- KEN SLVR MDWS SOUTH
- KEN SLVR MDWS & ANITA SB
- KEN SLVR MDWS & CAROL SB
- KEN SLVR MDWS & GARTH SB
- KEN SLVR MDWS & SPAUDLING SB
- KEN SPAULDING SOUTH
- KEN SPAULDING & MAIN SB
- KEN MAIN & SPAULDING EB
- KEN MAIN & ETON EB
- KEN MAIN & JUDITH EB
- KEN MAIN & STOW EB
- KEN MAIN & FOREST EB
- KEN MAIN & PROSPECT EB
- KEN MAIN & MANTUA EB
- KEN MAIN & RIVER EB
- KEN MAIN & WATER EB
- KEN WATER & ERIE SB
- KEN MANTUA & CUYAHOGA NB
- KEN MANTUA & STINAFF NB
- KEN MANTUA & RIVERSIDE NB
- KEN MANTUA & GRANT NB
- KEN MANTUA & GRANT SB
- KEN MANTUA & CARTHAGE SB
- KEN MANTUA & STINAFF SB
- KEN LAKE & LOCK EB
- KEN LAKE & MARVIN EB
- KEN LAKE & WOODSIDE EB
- KEN LAKE & HARVEY EB
- KEN LAKE & LAKE ST APTS EB
- KEN LAKE & ROCKWOOD APTS EB
- KEN LAKE & VIRGINIA EB
- KEN LAKE & 1ST EB
- KEN OHIO & 3RD SB
- KEN OHIO & 5TH SB
- KEN 6TH & OHIO SB
- KEN 6TH & RUGG SB
- KEN 6TH & ACME SB
- KEN SR43 & DEVON SB
- BRI SR43 & SHERMAN SB
- BRI SR43 & HOWE SB
- BRI SR43 & BRIMFIELD SB
- BRI SR43 & SANCTUARY SB
- 1088 - BRIMFIELD MEIJER
- 698 - BRIMFIELD WALMART
- AKR MARKET & GOODYEAR WB
- AKR MARKET & SUMMA CITY HOSPITAL
- AKR MILL & COLLEGE WB
- 881 - HIGH & COURTHOUSE SB
- 818 - METRO RKP TRANSIT CTR
- 898 - KENT MARC'S
- KEN MELOY & KENT BOG WB
- KEN MELOY & IND VLY WB
- KEN SUNNYBROOK & IND VAL1 NB
- KEN SUNNYBROOK & IND VAL2 NB
- KEN FRANKLIN & CURRIE HALL NB
- KEN FRANKLIN & JORDAN CT NB
- KEN FRANKLIN & CHERRY NB
- KEN FRANKLIN & SCHOOL NB
- KEN FRANKLIN & ELM NB
- KEN FRANKLIN & OAK NB
- KEN FRANKLIN & HALL NB
- KEN FRANKLIN & WILLIAMS NB
- KEN SUMMIT & WATER EB
- KEN SUMMIT & DEPEYSTER EB
- KEN SUMMIT AND WILLOW EB
- KSU MCGILVREY HALL NB
- KEN MAIN & 6TH EB
- KEN SR59 & RHODES EB
- KEN SR59 & WHISP PINES EB
- KEN SR59 & SR261 EB
- KEN SR59 & KLABEN EB
- RAV SR59 & ERIE EB
- RAV SR59 & POWDERMILL EB
- RAV SR59 & HVN OF PRTG EB
- RAV SR59 & PMHA EB
- RAV SR59 & VLG EST EB
- RAV SR59 & MENOUGH EB
- RAV SR59 & BRADY LK EB
- RAV SR59 & HILL EB
- RAV SR59 & DLR GEN EB
- RAV MAIN & SCRANTON EB
- and 801 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-08-22.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 51.8 | first check |
| 2026-08-07 | 49.7 | down 2.1 |
| 2026-08-22 | 55.8 | up 6.1 |
| 2026-08-23 | 55.8 | 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-08-22.
The feed file was re-published since 2026-08-22.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
What changed over time
On 2026-08-06 this feed started at grade F. On 2026-08-22 the check no longer reported: this feed's service calendar runs out within the next 30 days; service data runs out in 15 day(s). As of 2026-08-23 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-08-22 Score rose 6 points, freshness rose 25 points.
Everything we checked
10 findings, ordered by severity.
Show every finding
- Warning3964 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)
- Warning3159 instances
3159 of 3159 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)
- Warning1036 instances
1036 of 1051 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)
- Warning644 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.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · 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)
- Info775 instances
About 775 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info7 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info6 instances
Platform without parent station (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'platform_without_parent_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: platform_without_parent_station · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Needs attention
This feed is close to NTD-ready. Service data runs out in 30 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 30 days; renew before you certify.
- 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 3159 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
Two requirements remain for this feed to earn the conformance mark. Service data runs out in 30 days; renew to qualify. States wheelchair access on 1% 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 30 days; renew to qualify.
- Accessible Not yet
- States wheelchair access on 1% 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.
- 644 of 1051 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 30 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
- Correctness 74 / 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 50 / 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 34 / 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/portage-area-regional-transportation-authority-parta-2256/2026-08-23.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-23. 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.