GTFS Scorecard
← All agencies

Feed status · checked 2026-10-20

Freedom Transit (Washington County)

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

Service mode Bus

77.0 / 100

First scorecard for this agency

Cataloged in Pennsylvania.

Covers 72 daysAccessibility gapsRealtime not yet published

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

Freedom Transit (Washington County)’s published feed lists 7 bus routes, 99 scheduled trips and 139 stops. Its service dates run from 2026-03-02 through 2026-12-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

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

99 of 99 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 99 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 72 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

Correctness92.0 / 100

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

Freshness100.0 / 100

Service data covers the next 72 days.

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

1 accessibility depth signal

  • 114 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("College St. & E. Beau St.", "3rd St. & Jefferson Ave.", "Dollar General - Jefferson Ave.", 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 139 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.

  • L-A (red)
  • L-B (blue)
  • L-SAT (yellow)
  • CL-A (purple)
  • CL-B (pink)
  • M (green)
  • M-SAT (yellow)
Routes in Freedom Transit (Washington County)'s feed
RouteTypeLine color
L-A Local ABusred
L-B Local BBusblue
L-SAT Local SaturdayBusyellow
CL-A County Line ABuspurple
CL-B County Line BBuspink
M Metro CommuterBusgreen
M-SAT Saturday Metro CommuterBusyellow
List every stop
  • College St. & E. Beau St.
  • 3rd St. & Jefferson Ave.
  • Dollar General - Jefferson Ave.
  • Jefferson Ave. & Maple Ave.
  • Henderson Ave. & Allison Ave.
  • Henderson Ave. & Monterrey Ave.
  • Washington Penn Plastics
  • W. Pike St. & S. Shady Ave.
  • E. Pike St. & S. McNary St.
  • W. Pike St. & Hutchinson Ave.
  • W. Pike St. & Hutchinson Ave.
  • E. Pike St. & S. McNary St.
  • W. Pike St. & S. Shady Ave.
  • U.P.S.
  • Rt. 18 Trailer Ct.
  • Arden - Fairgrounds
  • Henderson Ave. & Allison Ave.
  • Jefferson Ave. & E. Wylie Ave.
  • Liberty Ave + William Penn
  • Jefferson Ave. & 3rd St.
  • Baird Ave. & Broad St.
  • Ridge Ave. & Murtland Ave.
  • Murtland Ave. & North Ave.
  • Rt. 980 & Morganza Rd.
  • Rt. 980 & Morganza Rd.
  • W. Beau St. & N. Franklin Ave.
  • W. Wheeling St. & S. Main St.
  • Locust Ave. & Murtland Ave.
  • Wilson Ave. & Larch St.
  • 3rd St. & Donnan Ave.
  • Maple Ave. & Summerlea Ave.
  • Jefferson Ave. & Oakland Ave.
  • 3rd St. & Duncan Ave.
  • Moon Rd. & Windsor Rd.
  • Windsor Rd. & Regent Dr.
  • Regent Dr. & Castle Rd.
  • Main @ 4th
  • Rte. 88 after Dry Run/Rte. 136
  • Rte. 88 @ Finleyville VFD
  • Valley Brook Rd. & E. McMurray Rd.
  • Rte. 19 & Hidden Valley Rd.
  • McMurray - Rte. 19 @ Lakeside Plaza
  • Canon House - North Central
  • Washington Health System - Landings Dr.
  • 1st St & Giffin Ave.
  • Rte. 19 @ Crosswinds Dr.
  • Rte. 19 & Gateshead Dr.
  • Valley Brook Rd. & E. McMurray Rd.
  • Rte. 88 & Boyer St.
  • Main St. @ Dry Run/Rte. 136
  • Main St. @ 4th St.
  • McDonald - Noblestown Rd. & Center Ave.
  • W. Maiden St. @ Washington Senior Center
  • W. Maiden St. @ TRPIL
  • Bellmead Apartments
  • Valley View Terrace - Valley Rd.
  • Henderson Ave and Regent Dr (Local B)
  • 5th Ave. & Smithfield St.
  • Smithfield St. @ 6th Ave.
  • Arden - Trolley Museum
  • Arden - Fairgrounds
  • Baird Ave. & Chesnut St.
  • Beau St. Park & Ride
  • Beau St. @ Shop N Save Plaza
  • Blvd of the Allies @ Wood St. / Pt. Park
  • Blvd of the Allies @ Wood St. / Pt. Park
  • Canon Apartments - North Central
  • Canonsburg Senior Center - Pike St.
  • Canonsburg Shop n Save - Pike St.
  • Cecil Senior Center - Millers Run Rd.
  • Centerville Clinic
  • Central Assembly of God - Pike St.
  • Central Assembly of God - Pike St.
  • Century Plaza
  • West Chestnut St. @ Shop N Save Plaza
  • Citizens Library
  • Pike St. & Country Club Rd.
  • Washington Courthouse
  • Crown Center Mall
  • Crumrine Tower
  • East Busway - near Amtrak/Greyhound
  • E. Maiden St. & Dunn Ave. (to Park)
  • E. Maiden St. & Dunn Ave. (to Transit Ce
  • E. Maiden St. & Wade Ave. (to Park)
  • E. Maiden St. & Wade Ave. (to Transit Ce
  • E. Wylie Ave. & Allison Ave. (to Transit
  • Haveloch Commons - Coal St.
  • Henderson Ave. & Regent Dr.
  • Heritage Library - Fourth St.
  • Heritage Library - Fourth St.
  • Pike Inn - Pike St.
  • Pike Inn - Pike St.
  • Pike St. & 2nd St.
  • Pike St. & 2nd St.
  • Jefferson Ave. & E. Wylie Ave. (to Maple
  • Jessop Place Park & Ride
  • Gateway Center - Liberty Ave. & Stanwix
  • Liberty @ 10th St.
  • Liberty Ave. - 3 Gateway Center
  • Locust St. & Leonard Ave.
  • Maiden St. & S Main St.
  • Maple Terrace Apartments (Maple Ave.)
  • McDonald Giant Eagle - Station St.
  • Pike St. & Third St.
  • Pike St. & Third St.
  • Murtland Ave. & Ridge Ave. (to Transit C
  • Bishop Rd. & Beech St.
  • Bishop Rd. & Elm St.
  • Northgate Plaza (Gabes)
  • N. Lincoln St. & Highland Ave.
  • Northgate - Westgate Apartments (Donnan
  • Old Mill (Hobby Lobby)
  • Oaksprings Plaza (Penn Commercial)
  • W. Pike St. & Buccaneer Dr.
  • W. Pike St. & Racetrack Rd.
  • Route 19/Murtland Ave.
  • Southpointe Park & Ride
  • Strabane Square (Target)
  • South Hills Transit Station
  • Tanger Outlets - Main Entrance
  • Thomas Campbell Apartments
  • Meadows Casino - Racetrack Rd.
  • Trich Dr. Loop
  • Trinity Point Dr.
  • Valley View Terrace - Valley Rd.
  • Trinity Point (Walmart)
  • Washington Mall (Home Depot)
  • Washington High School (Hall Ave.)
  • Washington High School (Jefferson Ave.)
  • Washington High School (Jefferson Ave.)
  • Washington Hospital (Wilson Ave.)
  • Washington Park
  • W. Chestnut St. & McCarrel Ave. (to Crow
  • W. Chestnut St. & McCarrel Ave. (to Tran
  • Pike St. & Greenside Ave.
  • Pike St. & Greenside Ave.
  • W&J Rossin Center
  • East Chestnut St. Transit Center
  • East Busway - near Amtrak/Greyhound

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

6 findings, ordered by severity.

Show every finding
  • Warning139 instances

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

  • Warning99 instances

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

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

  • 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

  • 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 72 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 235; your National Transit Database ID is 30111. 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 235 to NTD ID 30111, and keep the feed value stable. Do not change it solely to make the two values equal.
shapes.txt covers your trips Ready
All 99 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 72 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 72 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 92 / 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 38 / 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.

Freedom Transit (Washington County): GTFS feed quality grade C, 77.0 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/freedom-transit/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.