Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
St Lawrence County Public Transit
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 45% of all tracked agencies and 42% of mid-size agencies. Operates in New York.
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.1, validator 8.0.1.
Checked for changes 12 minutes ago; last changed 12 minutes 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
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
153 of 153 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
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.
⏱ A small file for most flat-fare systems.worth about +15 points
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).Likely your export tool
134 of 162 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ Often one default setting in your export.worth about +12 points
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
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. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
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. · Read the fix guide
Make the change. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). · Read the fix guide
Make the change. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Send Passio a fix request
This feed is generated by your Passio system. Copy this and send it to your Passio contact; the fixes apply to the route and stop data behind your AVL setup. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 7 kinds of issue across 52 instances (0 error, 38 warning, 14 informational).
Service data covers the next 30 days.
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.
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 (12, 61, 62, 63, 65).
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.
46 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Bottle & Can Retrieval - Massena", "Center Road & English Settlement Rd - Oswegatchie", "CR 10 & Mayhew Road - Depeyster", 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.
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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 65 (pink)
- 66 (green)
- 61 (pink)
- 63 (orange)
- 68 (green)
- 12 (red)
- 31 (brown)
- 62 (teal)
- 69 (teal)
- 70B (brown)
- 67 (brown)
- 70A (black)
- 71 (yellow)
- 73 (teal)
- 74 (purple)
- 80 (pink)
- 81 (gray)
| Route | Type | Line color |
|---|---|---|
| 65 Route 65 | Bus | pink |
| 66 Route 66 | Bus | green |
| 61 Route 61 | Bus | pink |
| 63 Route 63 | Bus | orange |
| 68 Route 68 (Clarkson Shuttle) | Bus | green |
| 12 Route 12 | Bus | red |
| 31 Route 31 | Bus | brown |
| 62 Route 62 | Bus | teal |
| 69 Route 69 (Roo Shuttle) | Bus | teal |
| 70B Route 70B (Massena Shuttle) | Bus | brown |
| 67 Route 67 (Bear Shuttle) | Bus | brown |
| 70A Route 70A (Massena Shuttle) | Bus | black |
| 71 Route 71 | Bus | yellow |
| 73 Route 73 | Bus | teal |
| 74 Route 74 | Bus | purple |
| 80 Route 80 | Bus | pink |
| 81 Route 81 | Bus | gray |
This feed has 153 stops.
List every stop
- Laurel & Grassmete Terrace Apts - Massena
- Price Chopper - Gouverneur
- Primary Care Center - Norfolk
- Al Smith's Superette - Norfolk
- Aldi - Ogdensburg
- Oxshire Creamery - Depeyster
- Human Services Center - Canton OB
- Lamphere's Market - Hopkinton
- Belmont Court - Ogdensburg
- Center for Sight - Ogdensburg
- Church Street Covered Stop - Gouverneur
- Community Health Center - Ogdensburg
- Dollar General - Ogdensburg
- Public Library - Massena
- Lincoln School - Ogdensburg
- Massena Hospital - Massena
- Parkview Rise - Ogdensburg
- Price Chopper - Ogdensburg
- Walmart - Massena
- Save A Lot - Gouverneur
- St. Peters Square - Ogdensburg
- CR 27 & Fulton Road - Lisbon
- Fulton Road & SH 68 - Lisbon
- Peru Street & SH11B - Lawrenceville
- Town Office - Dekalb Junction
- Fire Station - Morley
- Parkway Express IGA - Waddington
- Housing Authority - Massena
- Dollar General - Morristown IB
- Claxton-Hepburn Hospital - Ogdensburg
- Northwood Manor - Ogdensburg
- Save A Lot - Ogdensburg
- Stewart's - Heuvelton OB
- Route 68 Deli - Lisbon
- CR 10 & Mayhew Road - Depeyster
- 7-Eleven - Ogdensburg
- The Arc - Canton
- SH 812 & US Hwy 11 - Dekalb
- CR 10 & Plimpton Rd - Depeyster
- CR 11 & Bilow Rd - Gouverneur
- East Rd & SH 12 - Heuvelton
- Gouverneur Hospital - Gouverneur
- SH 58 & CR 6 - Edwardsville
- Brooklyn Road - Lawrenceville
- USH 11 & Main St - Richville
- Kearney Rd & CR 12 - Rossie
- Save A Lot - Potsdam OB
- St. Lawrence Centre Mall - Massena
- Price Chopper - Massena OB
- Walmart - Potsdam OB
- Municipal Building - Norwood
- Price Chopper - Potsdam
- Collegiate Village - Potsdam
- St. Lawrence Health System Medical Center - Canton OB
- Falls Market & Deli - Rensselaer Falls
- Canton Potsdam Hospital - Potsdam OB
- Rev. Patterson Wound Center - Ogdensburg
- Walmart - Ogdensburg
- CR 6 & SH 37 - Hammond
- Urgent Care - Potsdam
- Village Park - Raymondville
- Walgreens - Ogdensburg
- Dollar General - Heuvelton
- Clarkson Student Center - Potsdam OB
- SUNY Miller Campus Center - Canton
- Dollar General - Massena
- Senior Center - Akwesasne
- Police Activities League (King St) - Massena
- DMV Office - Massena
- Mohawk Casino - Akwesasne
- Bob's Motel - Massena
- Diane Burns Tower - Canton OB
- EJ Noble Medical Building - Canton OB
- Center Road & English Settlement Rd - Oswegatchie
- Lovejoy Road & Lee Road - Oswegatchie
- CR 6 & Lovejoy Rd - Oswegatchie
- MILC - Massena
- Middle Road & McCormick Road - Oswegatchie
- Twin Leaf Plaza & Diner - Akwesasne
- Westgate Apts - Canton
- Community Center - Massena
- Highland Nursing Home - Messena
- St. Regis Nursing Home - Massena
- NY 184 & Plimpton Rd - Kokomo Corners
- Liberty Apts - Canton
- SH 37 & Sand Street Road - Brier HIll
- CR 6 & Lost Village Rd - Oswegatchie
- Lovejoy Rd & Middle Rd - Oswegatchie
- Aldi - Massena
- McCormick Rd & Center Rd - Oswegatchie
- SH 58 & SH 184 - Pope Mills
- Centennial Terrace - Ogdensburg
- Village Park - Canton OB
- SH 812 & Stevenson Road - Kendrew Corners
- Tru-North Pizza - Flackville
- Across Fire Dept - Heuvelton
- Old Snell Hall - Potsdam
- Riverview Motel - Waddington
- ABCD Hardware - Winthrop
- Roxy Theater (Theater Side) - Potsdam
- Roxy Theater (Bus Shelter Side) - Potsdam
- Hepburn Library - Madrid
- Munson St Covered Stop - Potsdam OB
- Save A Lot - Canton OB
- Valero/Parkview Express - Morristown
- Sunoco - Gouverneur
- SH 37 & S Hammond Rd - Hammond
- LBSH Senior Housing - Brasher Falls
- Main St & Willow St - Richville IB
- Mill Yard Estates - Parishville
- Dept of Social Services - Canton OB
- Tri-Town IGA - Brasher Falls
- Hamilton St Parking Lot - Potsdam
- The Arc - Massena
- Post Office - Chippewa Bay
- Evergreen Park (Racquette Rd) - Potsdam
- Lawrence Ave Apts - Potsdam
- SUNY Potsdam Barrington Dr Bus Shelter OB
- Dept of Social Services - Canton IB
- Save A Lot - Potsdam IB
- Canton Potsdam Hospital - Potsdam IB
- Munson St Covered Stop - Potsdam IB
- St. Lawrence Health System Medical Center - Canton IB
- SUNY Potsdam Barrington Dr Bus Shelter IB
- Diane Burns Tower - Canton IB
- Village Park - Canton IB
- EJ Noble Medical Building - Canton IB
- Human Services Center - Canton IB
- Save A Lot - Canton
- Walmart - Potsdam IB
- Main St & Willow St - Richville OB
- Clarkson Student Center - Potsdam IB
- Price Chopper - Massena
- ABCD Hardware - Winthrop IB
- Walmart - Ogdensburg OB
- Stewart's - Heuvelton IB
- The Arc Jefferson (Gouverneur St)
- Dept of Social Services - Canton (IB2)
- Sure Stay - Massena
- Stewart's - Massena
- Ollie's - Massena
- Bottle & Can Retrieval - Massena
- Alcoa Park - Massena
- Spanky's - Massena
- Police Activities League (Bayley Rd) - Massena
- BJ's - Massena
- Tim Horton's - Massena
- Post Office - Helena
- Community Services - Akwesasne
- Price Chopper - Massena IB
- Louisville Housing - Louisville
- Senior Court - Edwards
- Pine Grove - Gouverneur
Over time
Overall score across the last 21 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 55.5 | first check |
| 2026-06-20 | 55.5 | no change |
| 2026-06-21 | 55.5 | no change |
| 2026-06-22 | 55.5 | no change |
| 2026-06-23 | 55.5 | no change |
| 2026-06-24 | 55.5 | no change |
| 2026-06-25 | 55.5 | no change |
| 2026-06-26 | 55.5 | no change |
| 2026-06-27 | 55.5 | no change |
| 2026-06-28 | 55.5 | no change |
| 2026-06-29 | 55.5 | no change |
| 2026-06-30 | 55.5 | no change |
| 2026-07-01 | 55.5 | no change |
| 2026-07-02 | 55.5 | no change |
| 2026-07-03 | 55.5 | no change |
| 2026-07-04 | 55.5 | no change |
| 2026-07-05 | 55.5 | no change |
| 2026-07-06 | 55.5 | no change |
| 2026-07-07 | 55.5 | no change |
| 2026-07-08 | 55.5 | no change |
| 2026-07-09 | 55.5 | 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-08.
The feed file was re-published since 2026-07-08.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
- Warning153 instances
153 of 153 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.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning134 instances
134 of 162 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 (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning128 instances
128 of 162 trips have no headsign.
Riders at the stop can't tell which direction a bus is going.
Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)
Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning20 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.)
Agencies here usually clear this within about 2 weeks (based on 6 observed fixes).
Validator rule: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning7 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.)
Agencies here usually clear this within about 1 week (based on 11 observed fixes).
Validator rule: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning6 instances
Stop too far from shape using user distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: 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)
- Warning3 instances
Stops match shape out of order (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stops_match_shape_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: stops_match_shape_out_of_order · 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.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info11 instances
Service window outside feed period (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_window_outside_feed_period' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 17 observed fixes).
Validator rule: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3 instances
Big gap in service (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'big_gap_in_service' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 13 observed fixes).
Validator rule: big_gap_in_service · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Some fixes we can make for you
These are the safe mechanical fixes, applied to a copy of your feed. They change only what is certain and leave everything else untouched. Review the diff before you publish.
Trimmed surrounding whitespace 1 change
For example: 'route_long_name': 'Route 74 ' -> 'Route 74'
Run it yourself on your own copy of the feed: scorecard autofix <feed.zip> --out corrected.zip
NTD certification readiness Needs attention
This feed is close to NTD-ready. Service data runs out in 30 days; renew before you certify.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Needs attention
- Service data runs out in 30 days; renew before you certify.
- agency_id matches your NTD ID Not checked yet
- Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
- shapes.txt covers your trips Ready
- All 162 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 and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
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). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and 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 runs out in 30 days; renew to qualify. States wheelchair access on 0% of stops and 17% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data runs out in 30 days; renew to qualify.
- Accessible Not yet
- States wheelchair access on 0% of stops and 17% 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.
- 7 of 153 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 540 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
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.
- Correctness 73 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 50 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 36 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: 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 live badge on your agency site or feed README. It updates daily 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/st-lawrence-county-public-transit-2611/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, 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.