Feed status · checked 2026-08-01
Monroe County Transportation Authority (MCTA)
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 3 hours ago; last changed 42 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 875 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
Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.Likely your export tool
Some route lines list the same point twice in a row. Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
⏱ Usually one export setting.worth about +8 points in its category
Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.Likely your export tool
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.
⏱ Usually an export-tool fix, not hand editing.worth about +8 points in its category
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 875 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
- Some route lines list the same point twice in a row.
- Next action
- Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.
- 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
- Some stops sit far from the route line, going by the feed's own distance values.
- Next action
- Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.
- 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. 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.
Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. · Read the fix guide
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.
Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. · Read the fix guide
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 was 875 days ago.
- Published accessibility data
- Accessibility information is stated for 100% of stops and 100% 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 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.
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 1353 instances (0 error, 1353 warning, 0 informational).
Service data ended 875 day(s) ago. Trip planners have likely already dropped this feed.
100% of stops state wheelchair accessibility (100% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
100% of stops state accessibility (100% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (101, 103, 204).
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.
163 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Price Chopper / US 209 W", "MCTA / PA 611 W", "Woodland S / PA 611", 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 197 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.
- 101 (red)
- 102 (teal)
- 103 (gray)
- 204 (green)
- 402 (purple)
- 405 (black)
| Route | Type | Line color |
|---|---|---|
| 101 Red | Bus | red |
| 102 Blue | Bus | teal |
| 103 Silver | Bus | gray |
| 204 Green | Bus | green |
| 402 EburgXprs | Bus | purple |
| 405 ShawneeSki | Bus | black |
List every stop
- Price Chopper / US 209 W
- MCTA / PA 611 W
- Woodland S / PA 611
- PA 611 / Knob Rd E
- Fairview Ave / PA 611
- Belmont Knoll / PA 611 SW
- Limeklin / East Kinney
- NCC Annex W
- Kings Way / Rte 196
- Carriage Square / Rte 196
- PCP Main Gate / Rte 196
- PCP JKL Gate / Rte 196
- Brentwood Rd
- PCP Rear Gate / Rte 196
- NHS Mt Pocono
- Sanofi / PA 611 W
- Crossings Premium Outlets S
- Warner Rd / PA 611 W
- Bartonsville Ave / PA 611 W
- American Candle / PA 611 W
- Rimrock Dr / PA 611 W
- Stroud Commons / Rte 611 W
- Fountain Court / PA 611 W
- Careerlink / Rte 611 W
- SONIC / PA 611 W
- Target / PA 611 N
- Radio Rd Best Buy / PA 611 W
- Bills ShopRite Knox St W
- Pocono Medical Center ER Entrance
- Golden Living / E. Brown St N
- Hemlock Dorm ESU
- CAO / Bridge St Apts
- West Main St / Jane St
- West Main St / Grace Park
- Fetherman St / West Main
- West Main St Wawa
- Stroud Mansion
- N. 3rd St / McConnell
- Analomink St / North Green St
- Analomink / S Kistler Sts
- Crystal St / Trackside
- Starbird St / S. Courtland St S
- Dansbury Park SROSC / Day St
- Day St. / Barnum St. W / SARP
- Day St / Lenox Ave W
- Lenox Ave N / Elizabeth St
- N Courtland St W / Lenox Ave
- ESHSS Auditorium / Burson St
- Spruce St. W / N. Courtland St.
- 5th St / N. Courtland St. W
- N Courtland St / Rt 447
- Maple St / N. Courtland St. E / Cramers
- Main / 7th NW
- Main St / 8th
- N 5th / Main / Kays Tavern
- La Tolteca / Commerce Blvd
- Great Wolf Lodge
- Brown St S / Arbys
- Franz Rd N / Windsor Dr
- Franz Rd S / WIndsor Dr
- Kohls E
- Kohls W
- Lowes / Red Robin N
- Lowes / Red Robin S
- 2582 PA 611, SCOTRUN, PA
- PA 611 & I-80 SCOTRUN
- 1245 Pocono Blvd / Mount Pocono
- Hotel M / Mount Pocono
- Prospect / Center Sts W
- Prospect / Center Sts E
- Shawnee Mountain Ski Area
- Baymont Inn / Bartonsville
- PA 611 / Amber / W
- PA 611 / Amber / E
- PA 611 / Desaki / W
- PA 611 / Desaki / E
- PA 715 / Warner Rd / N
- 2558 PA 715 / Sunoco / S
- 2558 PA 715 / Sunoco / N
- 2885 PA 611 / Vincents Deli
- Pocono Ambulance / Rte 611
- MCTA / PA 611 E
- Woodland N / PA 611
- Fork Street / Martz / PA 611
- Casino Theater / PA 611 E
- Belmont Knoll / PA 611
- Limeklin / East Kinney
- Mt Pocono Plaza
- NCC Annex E
- Kings Way / PA 196 E
- Carriage Square / PA 196 E
- PCP Main Gate / PA 196 E
- Woodside Dr W / APCP
- PCP JKL Gate / PA 196 E
- PCP Rear Gate / PA 196
- Great Wolf Lodge / Rte 611 / E
- Great Wolf Lodge / Rte 611 / W
- NHS Mt Pocono
- 5 Corners Mt Pocono
- 5 Corners Mt Pocono
- Acorn Market / PA 611 E
- Pocono Mt East HS S
- Crossings and PA 611
- Crossings Premium Outlets N
- Weis Tannersville
- Cherry Ln / PA 611 E
- Bartonsville Ave / PA 611 E
- American Candle / PA 611 E
- Rimrock Dr / PA 611 E
- Stroud Commons / PA 611 E
- Fountain Court / PA 611 E
- Careerlink / PA 611 E
- Walmart Plaza / PA 940
- NCC Monroe Campus by Pocono Hall
- Pine Hill Rd / PA 611 E
- PMVFD / PA 611 W
- Giant Supermarket / PA 611
- Sonic / PA 611 E
- Target / PA 611 S
- Radio Rd Best Buy / PA 611 E
- St Lukes Hospital
- LVHN Bartonsville
- Mountain Health Care Center
- Bills ShopRite Knox St E
- Kalahari Resort
- Norton Pryor / PA 314 W
- Summit Ave / PA 314 W
- Salvation Army / Summit N
- Pine Hill Rd / PA 196 W
- Snowshoe Apts / PA 196 E
- Snowshoe Apts / PA 196 W
- Edgewood / PA 196 E
- Edgewood / PA 196 W
- Evergreen / PA 196 E
- Evergreen / PA 196 W
- Green Rd / PA 196 E
- Green Rd / PA 196 W
- Renaissance Ln / PA 196 E
- Renaissance Ln / PA 196 W
- Pocono Mountain Public Library
- The Mountain Center
- Laurel Dr / PA 611 NE
- Laurel Dr / PA 611 SW
- Cayugo Dr / PA 611 NE
- Cayugo Dr / PA 611 SW
- Sussex Dr / PA 611 NE
- Sussex Dr / PA 611 SW
- Crows Path / PA 611 NE
- Crows Path / PA 611 SW
- Sharbaugh Rd / PA 611 NE
- Sharbaugh Rd / PA 611 SW
- Hemlock Dr / PA 611 NE
- Hemlock Dr / PA 611 SW
- Corporate Center Dr / PA 611 NE
- Industrial Dr / PA 611 SW
- Weis Stroudsburg
- 1137 N 9th St S / Popeyes
- Price Chopper / US 209 E
- Eastern Monroe Public Library
- Eagles Glen / US Bus 209
- HomeGoods EBurg
- GIANT East Stroudsburg
- Walmart / Lincoln St
- Golden Living / E Brown St S
- ESU Kemp Library
- Weis Eagle Valley
- CAO / Bridge St Apts
- West Main St / Jane St
- West Main St / Grace Park
- West Main St / Fetherman St
- Westgate / Main St
- Westgate / Dreher Ave.
- West Main St Wawa
- Little Angels Cafe
- Analomink St / North Green St
- Analomink / S Kistler Sts
- Crystal St / Hardware Store
- Avon Ct / Day St
- Day St. / Barnum St. E / SARP
- E. Brown / Smith Street
- E. Brown / Smith Street
- Day St / Lenox Ave E
- Lenox Ave S / Elizabeth St
- N Courtland St E / Lenox Ave
- North Courtland St / Burson St E
- Birch St. E / N. Courtland St.
- E. 5th St / N. Courtland St. E
- N Courtland St / PA 447
- N Courtland St / Maple Ave
- McConnell / 4th Sts
- Stroud Mall / Burger King
- Stroud Mall Front Entrance
- Main / 7th SW
- Lower Main / 3rd
- Main St / 8 th SW
- Lower Main and 4th St
- Mt Airy Resort and Casino / Woodland Rd
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 52.4 | first check |
| 2026-07-30 | 52.4 | no change |
| 2026-07-31 | 52.4 | no change |
| 2026-08-01 | 52.4 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
11 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 875 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)
- Warning874 instances
Some route lines list the same point twice in a row.
Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)
Finding code: equal_shape_distance_same_coordinates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning463 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning6 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 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)
- 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
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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · 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)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. Service data expired 875 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 875 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 192 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 875 days ago.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 875 days ago.
- Accessible Met
- States wheelchair access on 100% of stops and 100% of trips.
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.
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 54 / 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 92 / 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/monroe-county-transportation-authority-mcta/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.