GTFS Scorecard
← All agencies

Feed status · checked 2026-10-20

Area Transportation Authority of North Central Pennsylvania

Based on the feed source on file; publisher ownership is not verified

Service mode Bus

69.5 / 100

First scorecard for this agency

Cataloged in Pennsylvania.

Covers 131 daysAccessibility gapsRealtime not yet published

Source feed: https://rideata.rideralerts.com/InfoPoint/gtfs-zip.ashx

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.4, validator 8.0.1.

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.

About this feed

Area Transportation Authority of North Central Pennsylvania’s published feed lists 20 bus routes, 1,395 scheduled trips and 204 stops. Its service dates run from 2026-09-08 through 2027-02-28.

Top things to fix

Fix 01

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

204 of 204 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.

Fixing this covers all 204 stops in the feed.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category

Fix 02

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

1395 of 1395 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

Fixing this covers all 1,395 trips in the feed.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Fix 03

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.

This one is about the feed as a whole, so there is no share of it to count.

⏱ A small file for most flat-fare systems.worth about +15 points in its category

Riders and need behind these fixes

  • No ridership snapshot was on hand when this was built, so annual rider-trips are not known.
  • Pennsylvania as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-10-19.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

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.

Finding
Fix 01 in Top things to fix: its feed evidence and the requested 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
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.

  1. Fix 01 · Read the fix guide for scorecard_wheelchair_boarding_unknown

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  2. Fix 02 · Read the fix guide for scorecard_wheelchair_accessible_unknown

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  3. Fix 03 · Read the fix guide for scorecard_no_fare_data

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility
The feed's last published service date is in 131 days.
Published accessibility data
Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information
No fare information is published in the feed.
Realtime information
Realtime-feed availability and live-arrival coverage are not known from this scorecard.

Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.

Send your vendor a fix request

You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.

Score by category

Correctness84.0 / 100

The MobilityData validator flagged 3 kinds of issue across 169 instances (0 error, 169 warning, 0 informational).

Freshness100.0 / 100

Service data covers the next 131 days.

Rider experience24.7 / 100

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.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

2 accessibility depth signals

  • 5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (BFDW, RVBW, MTMD, CLFW, DUFR).

    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.

  • 62 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("BRUSSELLS ST & JOHN ST", "METOXET & JACKSON", "COURTHOUSE (COURT ST ENTRANCE)", 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.

Realtime qualityNot yet measured

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 204 stops.

Skip to route and stop data

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.

  • RWXP (blue)
  • EMXP (red)
  • FRST (black)
  • BFDR (red)
  • BFDB (green)
  • BFDW (brown)
  • BDSP (blue)
  • MCC (blue)
  • PXDB (green)
  • PUXS (black)
  • RVBW (gray)
  • CLFB (green)
  • CLFR (brown)
  • MTLP (black)
  • MTMD (brown)
  • CLFW (brown)
  • VEXP (red)
  • PWCL (black)
  • DUFB (blue)
  • DUFR (red)
Routes in Area Transportation Authority of North Central Pennsylvania's feed
RouteTypeLine color
RWXP Ridgway ExpressBusblue
EMXP Emporium ExpressBusred
FRST Friday Shopping TripBusblack
BFDR Bradford Red RouteBusred
BFDB Bradford Blue RouteBusgreen
BFDW Bradford White RouteBusbrown
BDSP Bradford to SmethportBusblue
MCC McKean County ConnectionBusblue
PXDB Punxsy to DuBoisBusgreen
PUXS Punxsy ShadowBusblack
RVBW Reynoldsville to BrockwayBusgray
CLFB Clearfield BlueBusgreen
CLFR Clearfield RedBusbrown
MTLP The Mountain LoopBusblack
MTMD The Mountain Mid-day LoopBusbrown
CLFW Clearfield WhiteBusbrown
VEXP The Valley ExpressBusred
PWCL Penn West Clarion LoopBusblack
DUFB DuBois BlueBusblue
DUFR DuBois RedBusred
List every stop
  • DAGUSGAHONDA
  • LAFAYETTE STREET
  • Lafayette Street SB
  • ELCAM
  • BRUSSELLS ST & JOHN ST
  • METOXET & JACKSON
  • COURTHOUSE (COURT ST ENTRANCE)
  • MONROE & FRONT ST
  • KEYSTONE - ST MARYS CARBON
  • ST JOSEPH TERRACE
  • ELK TOWERS
  • Metco/Penn United
  • BUCKTAIL VILLAGE
  • STACKPOLE COMPLEX
  • Stackpole Complex
  • BIG TROUT INN
  • AAM RIDGWAY
  • ATA TRANSIT CENTER SAINT MARYS
  • ROUTE 120 & BROAD
  • Penn United/Metco
  • W MAIN ST & OAK ST
  • W MAIN & OAK (Outbound)
  • SERVIDEA DR.
  • US Resistor / COMTEC
  • Product Assuranre Services
  • Product Assurance Services (Left Side)
  • Eastern Sintered Alloys
  • Metal Power Products
  • Penn Highlands Elk Campus
  • Elk Towers
  • Saint Marys Plaza
  • Walmart Saint Marys
  • Dollar Tree / Dunhams
  • Save A Lot Saint Marys
  • MAPLE ST APT
  • EMPORIUM ARMS
  • RITE AID EMPORIUM
  • ROUTE 120 & ROUTE 46
  • 4th and Spruce
  • EMERY TOWERS (EB)
  • EMERY TOWERS (WB)
  • SENIOR CENTER BRADFORD
  • BRMC
  • BRADFORD MALL
  • WALMART BRADFORD
  • CONGRESS & ELM (IB)
  • CONGRESS & ELM (OB)
  • TOPS MARKET (BRADFORD)
  • JACKSON & PLEASANT
  • UPB CAMPUS SAFETY OFFICE
  • DOROTHY LN & W WASHINGTON ST
  • US 219 & RT 59 (TACKS INN)
  • CENTRAL TOWERS WB
  • KANE POST OFFICE
  • CENTRAL TOWERS EB
  • COUNTRY FAIR KANE
  • E MAIN ST & FUTURES WAY (SB)
  • PLAZA STORES
  • E MAIN ST & FUTURES WAY (NB)
  • SAVE A LOT BRADFORD
  • MARILYN HORNE MUSEUM
  • HIGH RISE (EB)
  • HIGH RISE (WB)
  • CONGRESS & THOMPSON
  • MCKEAN CO COURTHOUSE
  • SMETHPORT FAMILY PRACTICE
  • COSTAS HARDWARE
  • MCKEAN COUNTY CHILDREN AND YOUTH
  • TOPS MARKET (KANE)
  • LEWIS RUN BOROUGH BUILDING
  • VETERANS SQUARE
  • KENNDY ST & JACKSON AVE
  • LANTZ CORNERS (NITTANY MINI MART)
  • HAINES ST & FRALEY ST
  • UNION SQUARE
  • MAIN & CHESTNUT ST
  • ELM & CHESTNUT ST
  • MCKEAN COUNTY DOMESTIC RELATIONS
  • CROSBY MINI-MART (OB)
  • CROSBY MINI-MART (IB)
  • US 219 & RT 59 (TJS MINI MART)
  • THE GUIDANCE CENTER
  • CYCLONE PA (RT 646 AT BINGHAM RD)
  • CAMPUS & BARBOUR
  • PUNXSY TRANSIT CTR
  • GOODWILL - FALLS CREEK
  • SYKESVILLE POST OFFICE
  • BIG RUN POST OFFICE
  • MAHONING TOWERS
  • MAHONING TOWERS
  • LANE AVE CARE HOME
  • SHADOW HOTEL
  • PUNXSY PLAZA
  • GRACE PLACE APARTMENTS SB
  • JEFF CTY HI-RISE (Outbound)
  • JEFF CTY HI-RISE
  • HOMETOWN MARKET
  • PUNXSY HOSPITAL
  • Punxsutawney Rapid Care
  • WALMART PUNXSY
  • REYNOLDSVILLE MUNICIPAL
  • TOBY TERRACE
  • REYNOLDSVILLE GRANGE
  • SKYVIEW TERRACE
  • JEFFERSON COUNTY HOUSING AUTHORITY OFF.
  • 28TH SOUTH 4TH ST. APTS
  • GRAYSTONE COURT VILLAS
  • PRIMARY HEALTH NETWORK
  • COUNTY ASSISTANCE OFFICE CAO
  • Mikes Bilo NB
  • SYCAMORE APARTMENTS
  • CULINARY ARTS IUP
  • DOLLAR TREE PUNXSY
  • SHEETZ PUNXSUTAWNEY Left Side
  • CULINARY ARTS IUP
  • IUP PUNXSY
  • CULINARY ARTS IUP
  • SHEETZ PUNXSUTAWNEY
  • 10TH & PLEASANT ST
  • FOUNDRY
  • Q CARE PUNXSY
  • MAIN ST MALL
  • ST MICHAELS TERRACE TRANSIT CENTER
  • COMMONS
  • SHOP GOODWILL
  • WALMART DUBOIS
  • SANDY PLAZA MAIN ENTRANCE
  • DUBOIS MALL MAIN ENTRANCE
  • FALLS CREEK POST OFFICE
  • GATEWAY TOWERS
  • GIANT EAGLE DUBOIS
  • LOWES
  • MARTINS DUBOIS
  • Penn Highlands Dubois West Campus
  • SAVE A LOT DUBOIS
  • 146 HANES DRIVE
  • Falls Creak Right Side
  • HANES & OKLAHOMA SALEM RD
  • ATA DUBOIS TERMINAL
  • HANES AND OKLAHOMA SALEM RD Left
  • DIXON & BRADY
  • Penn Highlands Clearfield Campus Front
  • HILL ST & HIGH ST
  • WRIGLEY ST & HILL ST
  • WALMART CLEARFIELD
  • LOWES CLEARFIELD
  • CLEARFIELD SQUARE
  • CLF-MHMR
  • MT LAUREL NURSING HOME
  • COLONIAL COURTYARD
  • GREYSTONE
  • CLEARFIELD CO COURTHOUSE
  • CLEARFIELD SENIOR CENTER
  • CLEARFIELD CAREERLINK
  • LINDEN ST & LATIMER ST
  • LAWRENCE PARK VILLAGE
  • JOYNER SPORTS MEDICINE
  • KNICKERBOCKER
  • LOCUST ST & N 3RD ST
  • DROP IN CENTER CLF
  • MEYERS TOWERS
  • Tractor Supply
  • MAPES AVE & GOOD ST
  • CENTER ST & W MAPLE
  • CLEARFIELD CENTER FOR ACTIVE LIVING
  • MILL RD & PARK DR
  • CLEARIFELD FAIRGROUNDS
  • NICHOLS ST & WEAVER ST
  • DAISY ST & BIGLER AVE
  • DAISY ST & E 10TH ST
  • LUTHERSBURG G & S MINI-MART
  • GRAMPIAN PA RT 219 & 879
  • CURWENSVILLE IGA
  • HYDE UNI-MART
  • LEONARD ST CLEARFIELD
  • PARK AVE APTS
  • CURWENSVILLE COMMONS
  • RIDGEVILLE NURSING HOME
  • EDGEWOOD APTS
  • HYDE ADULT TRAINING
  • J & G FOOD MARKET
  • PARK AVE & S 3RD
  • W WASHINGTON AVE & RIDGE ST
  • Knarr Street and Shaffer Ave
  • CLEARFIELD CO ASST OFFICE
  • N 3RD ST & E MARKET ST
  • WOODLAND AVE & WRIGLEY ST
  • Highland Street
  • 1St Street
  • CVS DuBois
  • TIPPIN MARWICK
  • REINHARD VILLAGE
  • COLLEGE PARK APTS
  • EAGLE PARK
  • 5TH AVE & SOUTH ST
  • CLARION MALL
  • WALMART CLARION
  • LIBERTY TOWERS
  • MCDONALDS CLARION
  • MAIN ST & 5TH AVE
  • STARBUCKS
  • BELL TOWER CLARION
  • CENCLEAR INDUSTRIAL DRIVE
  • CURWENSVILLE HOUSE

Over time

This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.

Everything we checked

8 findings, ordered by severity.

Show every finding
  • Warning1395 instances

    1395 of 1395 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference

  • Warning204 instances

    204 of 204 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference

  • Warning165 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 for mixed_case_recommended_field · See MobilityData GTFS Validator rules

  • Warning3 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 for stop_too_far_from_shape_using_user_distance · See MobilityData GTFS Validator rules

  • 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 for missing_feed_contact_email_and_url · See MobilityData GTFS Validator rules

  • 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 for scorecard_no_fare_data · See GTFS Best Practices

  • Info174 instances

    About 174 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 for scorecard_stop_names_all_caps · See GTFS Best Practices

  • 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. Small errors then sit in the feed for months.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

    Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules

NTD GTFS readiness Ready

Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.

Published Ready
Published at a public URL.
Valid Ready
Passes validation with no errors.
Current Ready
Service data covers the next 131 days.
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) Equal
This feed's agency_id also equals its NTD ID (30196). Equality is allowed but not required; keep the value stable and retain the P-50 crosswalk.
shapes.txt covers your trips Ready
All 1395 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

One requirement remains for this feed to earn the conformance mark. 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 Met
Service data covers the next 131 days.
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.

Clears the Google and Apple Maps four-week coverage bar. This feed has 131 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 84 / 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 100 / 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 25 / 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.

Part of the Pennsylvania portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Pennsylvania

Other scorecards in Pennsylvania, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

Area Transportation Authority of North Central Pennsylvania: GTFS feed quality grade D, 69.5 of 100, checked 2026-10-20. GTFS 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/area-transportation-authority-of-north-central-pa/2026-10-20.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-10-20. 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.