GTFS Scorecard
← All agencies

Feed status · checked 2026-10-20

Fayette Area Coordinated Transportation (FACT)

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

Service mode Bus

70.8 / 100

First scorecard for this agency

Cataloged in Pennsylvania.

Covers 103 daysAccessibility gapsRealtime not yet published

Source feed: https://fact.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.

Checked for changes 34 minutes ago; last changed 34 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.

About this feed

Fayette Area Coordinated Transportation (FACT)’s published feed lists 7 bus routes, 154 scheduled trips and 156 stops. Its service dates run from 2026-07-21 through 2027-01-31.

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

156 of 156 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 156 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

154 of 154 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 154 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 103 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

Correctness78.0 / 100

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

Freshness100.0 / 100

Service data covers the next 103 days.

Rider experience37.4 / 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

  • 2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (104, 303).

    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.

  • 65 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Uniontown Walmart / Fayette Crossing Pla", "Home Depot / TJ Maxx F116", "16th 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.

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 156 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.

  • 104 (red)
  • 201 (blue)
  • 301 (teal)
  • 303 (purple)
  • 401 (green)
  • 601 (orange)
  • 700 (teal)
Routes in Fayette Area Coordinated Transportation (FACT)'s feed
RouteTypeLine color
104 Masontown / FairchanceBusred
201 Pittsburgh CommuterBusblue
301 Uniontown B/ NemacolinBusteal
303 ConnellsvilleBuspurple
401 Uniontown ABusgreen
601 Brownsville / UniontownBusorange
700 Shuttle Uniontown Mall & Gabe's PlazaBusteal
List every stop
  • Transfer Center
  • Uniontown Hub
  • Transit Center
  • Uniontown Hub
  • Uniontown Mall
  • Uniontown Hospital
  • Uniontown Mall
  • Uniontown Walmart / Fayette Crossing Pla
  • Aldi
  • Centerville Clinic
  • Gabe's Plaza
  • Home Depot / TJ Maxx F116
  • Lowe's
  • Target
  • 16th St
  • Amend Rd
  • Big 6 Rd
  • Big Lots
  • Broadway St
  • Brodak's Shopper's Value
  • Brownsville Walmart
  • Buffington
  • Buffington
  • Cardale
  • Cardale
  • Career Link / Headstart / PIC
  • Carnegie Library
  • Cash Saver
  • Chalk Hill (Subway)
  • Chalk Hill Market
  • Cherry Tree Ln
  • Chez Joey Apartments
  • Children and Youth Services
  • Connellsville Municipal
  • Connellsville St
  • Connellsville St
  • Connellsville Towers
  • Connellsville Walmart
  • Continental 3 & 2
  • Coolspring St
  • Country Side Plaza
  • Crawford Ave
  • Dairy Queen
  • Dollar General Uniontown
  • Dry Knob Hill
  • Dunbar (enter Woodvale St)
  • Dunbar (exit Woodvale St)
  • East Busway stop D
  • Fairbank
  • Fairbank
  • Family Dollar
  • Fayette Avenue
  • Chestnut Ridge
  • Fayette County Blind Assn.
  • Fayette Industrial Park
  • Fayette St
  • Fayette Street Connellsville
  • Fort Mason Village
  • Gallatin Ave / Maple Garden Apts
  • Giant Eagle
  • Harris Garden Apts
  • Health First Medical Center
  • Heritage Apartments
  • High St
  • Highlands Hospital
  • Hiller Ave
  • Holiday Mobile Park
  • Hopwood
  • Hopwood Fire Station
  • Hunters Ridge
  • Hyndman St
  • Iron Bridge Apts
  • Iron Bridge Apts
  • Jefferson St / St. John Church
  • Kyle Ave
  • The Casino at Nemacolin
  • Lafayette Mnr / Beechwood Crt
  • Laurel Mall
  • Lebanon Ave
  • Liberty Ave (Federal Bldg)
  • Libery Ave + Smithfield St
  • Market Street / Union Station
  • Market Street / Union Station
  • Martin's Plaza
  • Masontown City Hall
  • Masontown City Hall
  • McClellandtown Rd
  • Meadow Heights
  • Meridian Point
  • Mill St / Saint Theresa Church
  • Morgantown St
  • Mt. Vernon Towers
  • Mt. Vernon Towers
  • N Main St
  • N Mt. Vernon / St. Mary's Church
  • N Pittsburgh St
  • N Water St
  • Nelson Rd
  • Nemacolin Woodlands
  • New Salem Rd / Mill Street
  • New Salem Rd / Mill Street
  • Nickman's Plaza
  • North Manor
  • Oliver Post Office/Oliver Rd
  • Oliver Square
  • Ollie's Plaza
  • Pechin Rd (enter Dunbar)
  • Pechin Rd (exit Dunbar)
  • Penn DOT License Center
  • Penn St Parking Garage
  • Penn State University
  • Pershing Court / Dunlap St
  • Poplar Ln Court
  • Republic
  • Republic
  • Rite Aid Brownsville
  • Rite Aid Connellsville
  • Rite Aid Connellsville Street
  • River Ave
  • Riverview Apts
  • Rostraver Airport
  • Rt 51 Park & Ride
  • S Arch St
  • S Pittsburgh St
  • S. Mt. Vernon Ave
  • Searight Ave / E Main St
  • Second St
  • Shady Ln
  • Sheetz
  • Sheldon Ave
  • Smithfield & 6th (Burlington)
  • Smithfield St & Forbes Ave
  • Smithfield St & Oliver Ave
  • Smithfield St Bridge + Station Square
  • Smithfield VFD
  • South Hills Ter
  • Star Junction McDonald's
  • Stewart Ave
  • Strickland Estates
  • Dollar Tree
  • Success Dr
  • Thomas St
  • Tuskegee Terrace / Bradbury St
  • Uniontown High School
  • Uniontown Mall / Teletech
  • Uniontown Senior Ctr
  • Uniontown Shopping Center
  • University Commons
  • Village of Searights
  • Walnut Hill Shoppes
  • Water St
  • Woodward Ave
  • Wynnwood Commons
  • YMCA
  • W Carson St + Gateway View Plaza
  • East Busway Penn Station

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

9 findings, ordered by severity.

Show every finding
  • Warning156 instances

    156 of 156 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

  • Warning154 instances

    154 of 154 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

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

  • Warning4 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

  • Warning3 instances

    Between two distant stops, the times imply a speed no bus reaches.

    A rider gets a trip plan that cannot happen. Live systems then report delays that are not real.

    Fix: Check the two stop times for a wrong digit first. Then check whether a stop sits at the wrong coordinates, or a stop between them is missing. (Minutes per flagged trip once you open it.)

    Finding code: fast_travel_between_far_stops · Read the fix guide for fast_travel_between_far_stops · 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

    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 for route_color_contrast · 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

  • 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 103 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) Different (allowed)
Your feed's agency_id is 0; your National Transit Database ID is 30087. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id 0 to NTD ID 30087, and keep the feed value stable. Do not change it solely to make the two values equal.
shapes.txt covers your trips Ready
All 154 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 103 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 103 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 78 / 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 37 / 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.

Fayette Area Coordinated Transportation (FACT): GTFS feed quality grade C, 70.8 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/fayette-area-coordinated-transportation/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.