GTFS Scorecard

← Back to the full scorecard

Board packet · transit data quality · checked 2026-10-07

St Lawrence County Public Transit

Grade F · 40.4 / 100

Unchanged since 2026-10-06.

What this grade measures

The quality of the schedule data in the feed scored here for trip-planning apps: whether riders using Google Maps, Apple Maps, or Transit see current, correct, and complete information. It measures the data feed, not service quality or operations.

Progress this period

No newly cleared items this period. The score and trend above reflect where the feed stands today.

What needs attention next

Three improvements, in priority order, each sized so the board can see what it is approving:

  1. Correct feed_end_date in feed_info.txt. Set it to 2027-12-31, the last day in your calendar, or to the last day your schedule is reliable.

    feed_info.txt says this feed ends on 2026-04-30. Your service calendar runs to 2027-12-31. The GTFS standard tells apps to trust a feed only up to its end date. So apps may stop showing your service on the earlier date, even though the calendar goes on.

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

    Estimated effort: One field in feed_info.txt, often an export setting.

  2. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

    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.

    Fixing this covers all 153 stops in the feed.

    Estimated effort: A column in stops.txt; your scheduling software likely has it.

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

    Estimated effort: A small file for most flat-fare systems.

Riders and need behind these fixes

  • This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
  • New York as a whole measures moderate 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-05.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the 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.

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
feed_info.txt says this feed ends on 2026-04-30. Your service calendar runs to 2027-12-31.
Next action
Correct feed_end_date in feed_info.txt. Set it to 2027-12-31, the last day in your calendar, or to the last day your schedule is reliable.
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

Produced by the GTFS Scorecard, an open-source data quality tool. A data-quality read to support the board conversation, not an official compliance determination. Live scorecard: https://gtfsscorecard.org/agency/st-lawrence-county-public-transit/. Rubric v1.4, validator 8.0.1.