Feed status · checked 2026-08-01
Erie Metropolitan Transit Authority
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 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 1004 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
1383 of 1383 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
997 of 997 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
Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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 1004 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
- 1383 of 1383 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
- 997 of 997 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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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 1004 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 Trillium a fix request
This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. 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 9 kinds of issue across 125 instances (0 error, 75 warning, 50 informational).
Service data ended 1004 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
15 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 3, 20A, 20B, 20C, 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.
1164 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("French St at E 5th St", "State St at E 9th St", "State St at W 8th St", 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 1383 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.
- 105 (teal)
- 229 (pink)
- 23 (yellow)
- 22 (teal)
- 21 (pink)
- 20A (red)
- 16 (gray)
- 15 (gray)
- 14 (red)
- 12 (red)
- 11 (pink)
- 20C (teal)
- 20B (gray)
- 4 (teal)
- 3 (teal)
- 1 (teal)
- 24 (red)
- 25 (green)
- 26 (purple)
- 27 (pink)
- 28 (green)
- 29 (orange)
- 30 (red)
- 31 (teal)
- 32 (red)
- 20L (blue)
- 17 (green)
| Route | Type | Line color |
|---|---|---|
| 105 Corry | Bus | teal |
| 229 Fairview | Bus | pink |
| 23 Belle Valley | Bus | yellow |
| 22 Tacoma | Bus | teal |
| 21 Lawrence Park | Bus | pink |
| 20A Downtown Loop | Bus | red |
| 16 North East | Bus | gray |
| 15 E 38th Street | Bus | gray |
| 14 Edinboro | Bus | red |
| 12 Albion | Bus | red |
| 11 Harborcreek | Bus | pink |
| 20C Courthouse Loop | Bus | teal |
| 20B UPMC Hamot | Bus | gray |
| 4 Liberty Street | Bus | teal |
| 3 Peach Street | Bus | teal |
| 1 Glenwood | Bus | teal |
| 24 McClelland | Bus | red |
| 25 Wesleyville | Bus | green |
| 26 E 26th Street | Bus | purple |
| 27 State Street | Bus | pink |
| 28 Erie Heights | Bus | green |
| 29 Asbury | Bus | orange |
| 30 West Millcreek | Bus | red |
| 31 Frontier | Bus | teal |
| 32 Westlake | Bus | red |
| 20L Cultural Loop | Bus | blue |
| 17 Briggs | Bus | green |
| 33 Presque Isle Express | Bus | teal (no shape in feed) |
List every stop
- Sheraton Hotel
- French St at E 5th St
- E 7th at French
- State St at E 9th St
- State St at W 8th St
- Achievement Center
- Asbury Rd at W 23rd St
- W Lake Rd at Woodside Dr
- W Lake Rd at Millfair Rd
- W Lake Rd at Morrison Dr
- Manchester Rd at W Lake Rd
- Manchester Rd at Townsend Dr
- Manchester Rd at Bowman Ct
- Wegmans
- Asbury Rd at W 23rd St
- Harborcreek Senior Center
- Highland Senior Apartments
- St Francis Xavier Church
- interchange at 79 ramps-sb
- Crossroads Communtiy Baptist
- Crosbys
- Old French Rd at Perry Hwy
- Matrix Tools IB
- Fairview Industrial Park East
- Fairview Industrial Park North
- Matrix Tools OB
- Grimm Industries
- Walmart West
- Erie County Tech School
- Fudpucker
- Sciota at E.Columbus
- Enterprise Place
- Barber Center
- Shawnee Trailer Park
- E Washington at Pennsylvania Ave
- E Wasington (Corry Counseling)
- N Center St at W Smith St
- N Center St opp E Bond St
- N Center St at Elk St
- Wright St at Raymond St
- Snyder Cir
- Corry Industrial Park
- Plastics Rd at Enterprise Rd
- W Columbus Ave at Advance Auto Parts
- Corry Plaza
- Credit Union
- Corry Manor
- Davita Dialysis
- W Washington St at Worth St
- W Washington at Essex St
- W Washington St at Plaza St
- Corry Senior Center
- Spring St at W Pleasant St
- Sprint St at Brook St
- Tonnard Manufacturing
- S Center St at Airport Rd
- S Center St at W Pleasant St
- E Main St at N Center St (Bus Shelter)
- E Main St at Pennsylvania Ave
- E Main St at Summer St
- E Main St at Ave A
- N Shady Ave at E Main St
- Corry Walmart
- Corry Hospital
- W 12th at Grace
- WalMart West
- W 26th and Legion
- W 26th St at Peach
- K Mart Plaza - Buffalo Rd at Nagle Inbound
- E 21st at Perry IB
- E 18th St at Parade Blvd IB
- E 6th St at Payne Inbound
- Main St at Water St Inbound
- Main St at Water St
- E 6th St at Payne
- Rice Ave at E 41st
- Rice Ave at E 38th St
- Peach at Avalon
- E 26th at Parade Blvd
- Buffalo Rd at Saltsman
- Buffalo Rd at Saltsman
- E 26th at Elm st
- E 38th at Mercyhurst
- E 26th St at State St
- Old French at E 38th St
- E 26th St at Parade St
- 38th St at State St
- 38th St at State St
- Edinboro University Center
- State at 18th St
- State St at W 18th St
- E 10th St at French St
- E 38th St at Ash St
- W 10th at Peach
- W 2nd St at UPMC Hamot (Bus Shelter)
- Old French Rd opp E 30th St
- Old French Rd at E 33rd St
- Old French Rd at E 35th St
- W Division St at N Pearl St
- N Lake St at E Division St
- Station Rd at W Law Rd
- S Lake St at Ackerman Ln
- S Lake St at Clinton St
- S Lake St at Eagle St
- W Main Rd at S Pearl St
- W Main St at Robinson St
- W Main St at S Mill St
- W Main Rd at West St
- W Main Rd at Clinton St
- W Main Rd at Cemetery Rd
- W Main Rd at Williams Rd
- W Main Rd at Brickyard Rd
- Buffalo Rd at Haskell Rd
- Buffalo Rd at Moorheadville Rd
- Buffalo Rd at King Rd
- Buffalo Rd at Davison Rd
- Buffalo Rd at Bartlett Rd
- Mercyhurst North East
- Janet Miller Building Mercyhurst NE
- Buffalo Rd opp Fiddle Inn
- Buffalo Rd at Bartlett Rd
- Buffalo Rd at Janes Ln
- Buffalo Rd at Highmeyer Rd
- Buffalo Rd at Moorheadville Rd
- W Main Rd at Catholic Cemetery Rd
- W Main Rd at N Brickyard Rd
- W Main Rd opp Williams Rd
- W Main Rd at Poplar Ln
- W Main Rd at Park Lane Rd
- W Main Rd at Cemetery Rd
- W Main Rd at Appletree Ln
- W Main St at Speedway Dr
- W Main St at N Mill St
- W Main St at N Pearl St
- N Lake St at W Main St
- N Lake St at Gibson St
- N Lake St at W Division St
- S Lake St at E Main St
- S Lake St at Grant St
- S Lake St at Clay St
- Station Rd at Wellington St
- Station Rd at E Law Rd
- Boyers Rv
- Rt 19 at Townhall Rd
- Rt 19 at Elk Creek Rd
- Coventina Day Spa
- Rt 19 at Talcott Rd
- Rt 19 at Rolling Meadow Dr
- Waterford Square-INB
- High St at E 1st St
- A. Caplan Company
- Rt 97 at Flatts Rd-IB
- Sunset Drive in Waterford-IB
- Rt 97 at Hare Rd IB
- Rt 97 at Middleton Rd
- Rt 97 at Kimball Hill Rd
- Rt 97 at Rt 8 NB
- Union City McDonalds
- Rt 6 at Hoyt Rd
- Rt 6 And Rt 89 Intersection-IB
- Rt 6 at King Rd
- Rt 6 at Conelway Rd
- Rt6 at Hatchery Rd
- Humes Ford
- Corry Plaza-OB
- Rt 6 at W Smith St Ext
- Rt 6 at W Washington St Ext
- Route 6 at Corry Auto
- Rt 18 at Reese Dr
- Rt 18 at Drury Rd-Nb
- Rt 18 at Cross Station Rd-Nb
- Rt 18 at Cross Station Ext
- Rt 18 at Mill St
- Rt 18 at E Peach St
- Rt 18 at Franklin Center Rd
- Rt 18 at Fillinger Rd
- Rt 18 at Kidder Rd
- Rt 18 at Richardson Rd
- Rt 18 at Thrasher Rd- Nb
- Rt 18 at E Crane St-Nb
- Rt 18 at Sherman Rd-Nb
- Rt 18 at Church
- Rt 18 Nb Albion
- Albion Dollar Store
- Albion mcdonalds
- 6N at Wells Ave
- N Main St at 6N
- Academy St at W Pearl St
- 6N at Academy St
- State St at Main
- S Main St at S Park Ave
- S Main St at Meadow Dr
- Albion SCI
- W 32nd St at Caughey Rd
- W 32nd St opp Stoughton Rd
- W 32nd St at Hastings Rd
- W 32nd St at Legion Rd
- W 32nd St at Zuck Rd
- W 32nd St at Highland Rd
- W 32nd St at Garland St
- W 32nd St at Atlantic Ave
- W 32nd St at Pittsburgh Ave
- W 32nd St at Schaper Ave
- W 32nd St at Post Ave
- W 32nd St at Hampton Ave
- W 32nd St at Harvard Blvd
- W 32nd St at Greengarden Blvd
- W 32nd St at Washington Ave
- W 32nd St at Melrose Ave
- Elmwood Ave at W 32nd St
- Elmwood Ave at Patterson Ave
- W 29th St at Elmwood Ave
- W 29th St at Raspberry St
- W 29th St at Cascade St
- W 29th St at Liberty St
- W 29th St at Hazel St
- W 29th St at Cherry St
- W 29th St at Sigsbee St
- W 29th St at Schley St
- W 29th St at Chestnut St
- Myrtle St at W 29th St
- Myrtle St at W 26th St
- Myrtle St at W 25th St
- Myrtle St at W 24th St
- Myrtle St at W 23rd St
- Myrtle St at W 22nd St
- W 21st St at Myrtle St
- W 21st St at Sassafras St
- W 21st St at Peach St
- W 21st St at State St
- W 21st St at Peach St
- W 21st St at Sassafras St
- Myrtle St at W 21st St
- Myrtle St at W 22nd St
- Myrtle St at W 23rd St
- Myrtle St at W 24th St
- Myrtle St at W 25th St
- Myrtle St at W 26th St
- W 29th St at Myrtle St
- W 29th St at Chestnut St
- W 29th St at Walnut St
- W 29th St at Cherry St
- W 29th St at Hazel St
- W 29th St at Liberty St
- W 29th St at Cascade St
- W 29th St at Raspberry St
- Elmwood Ave at W 29th St
- Elmwood Ave at W 32nd St
- W 32nd St at Melrose Ave
- W 32nd St at Washington Ave
- and 1133 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 | 45.7 | first check |
| 2026-07-30 | 45.7 | no change |
| 2026-07-31 | 45.7 | no change |
| 2026-08-01 | 45.7 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-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
14 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 1004 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)
- Warning1383 instances
1383 of 1383 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)
- Warning997 instances
997 of 997 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)
- Warning580 instances
580 of 997 trips lack rider-facing destination or direction text.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning61 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)
- Warning8 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)
- Warning3 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)
- 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
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
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
This feed describes flexible (demand-responsive) service but has no booking_rules.txt.
Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.
Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)
Finding code: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info34 instances
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.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info8 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)
- Info8 instances
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)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
Flex zones are published but no booking_rules.txt is present.
Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. Service data expired 1004 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 1004 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 997 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 1004 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 1004 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 61 of 1383 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.
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 68 / 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 51 / 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/erie-metropolitan-transit-authority/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.