The feed address on file failed at our last check (HTTP 403). Download the newest saved copy from the Mobility Database, or send us the new address.
Feed status · checked 2026-11-09
Rochester City Lines
Based on a Mobility Database mirror copy of an archived feed listing
Scored from a Mobility Database mirror copy downloaded on 2026-10-19, because the feed URL on file could not be downloaded. Service dates in that copy end 2016-01-01. It may not match the feed the agency publishes today.
Service mode Bus
Partial: freshness not measured.
Methodology changed; trend restarts here
Cataloged in Minnesota.
The grade is not a count of validator errors. It also weighs freshness and rider information. How the grade works
Feed file
Feed URL: https://transitfeeds.com/p/rochester-city-lines/774/latest/download
Failed at last check (HTTP 403) Newest saved copy
Watch this feed for free: we email you before it expires or when its grade drops.
Top things to fix
Check that https://transitfeeds.com/p/rochester-city-lines/774/latest/download still serves your current feed. If the feed moved, publish the new address.
The feed URL on file, https://transitfeeds.com/p/rochester-city-lines/774/latest/download, could not be downloaded: the server answered with an error instead of the file. Trip planners download the feed from that address too. The grade here was measured on an older Mobility Database copy whose service ended 2016-01-01, so freshness is not graded until the current feed can be downloaded.
This one is about the feed as a whole, so there is no share of it to count.
⏱ Usually a server or hosting setting, not a change to the feed itself.
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
101 of 101 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 101 stops in the feed.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
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
79 of 79 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 79 trips in the feed.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Riders and need behind these fixes
- This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
- Minnesota 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-11-02.
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 URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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
- Finding
- Fix 02 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
- Finding
- Fix 03 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.
Make the change. This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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.
Fix 02 · Read the fix guide for scorecard_wheelchair_boarding_unknown
Make the change. This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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.
Fix 03 · Read the fix guide for scorecard_wheelchair_accessible_unknown
Make the change. This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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
- Schedule visibility is not known from this scorecard.
- 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
- 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
This feed is served from the TransitFeeds archive, which is no longer maintained. The most useful request is publishing the current feed from a live URL, then these fixes. Each fix names the validator notice and a guide link.
About this feed
Looking for times or routes? This page checks the data file that trip planners use. For schedules, use the agency's own website or a trip planner.
Rochester City Lines’s published feed lists 27 bus routes, 79 scheduled trips and 101 stops. The published file has not changed since our first check on 2026-06-19.
Score by category
The MobilityData validator flagged 7 kinds of issue across 13 instances (0 error, 8 warning, 5 informational).
Not graded. The feed URL on file could not be downloaded, and the Mobility Database mirror copy scored instead ended its service on 2016-01-01. That date describes the copy, not the feed the agency publishes today, so it does not count against the grade.
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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
74 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("2nd Ave. SW & 2nd St. SW (West side, Midblock)", "2nd Ave. SW & 2nd St. SW (East side, Midblock)", "2nd Ave. SW & 2nd St. SW (East side, North)", 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 101 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.
- Rochester-Minneapolis (green)
- Austin (green)
- Hayfield (green)
- Dodge Center (green)
- Byron-Kasson-Dodge Center (green)
- Dodge Center-Hayfield (green)
- Byron (green)
- Kasson (green)
- Cannon Falls (green)
- Preston (green)
- Chatfield (green)
- Winona (green)
- Owatonna (green)
- St. Charles (green)
- Wabasha (green)
- Wabasha-Lake City (green)
- Plainview (green)
- LeRoy-Grand Meadow (green)
- Zumbrota (green)
- Pine Island (green)
- Spring Valley (green)
- Stewartville (green)
- Kellogg-Wabasha (green)
- Twin Cities (green)
- Dexter (green)
- Rochester/Twin Cities (green)
| Route | Type | Line color |
|---|---|---|
| Rochester-Minneapolis | Bus | green |
| Austin | Bus | green |
| Burnsville | Bus | green (no shape in feed) |
| Hayfield | Bus | green |
| Dodge Center | Bus | green |
| Byron-Kasson-Dodge Center | Bus | green |
| Dodge Center-Hayfield | Bus | green |
| Byron | Bus | green |
| Kasson | Bus | green |
| Cannon Falls | Bus | green |
| Preston | Bus | green |
| Chatfield | Bus | green |
| Winona | Bus | green |
| Owatonna | Bus | green |
| St. Charles | Bus | green |
| Wabasha | Bus | green |
| Wabasha-Lake City | Bus | green |
| Plainview | Bus | green |
| LeRoy-Grand Meadow | Bus | green |
| Zumbrota | Bus | green |
| Pine Island | Bus | green |
| Spring Valley | Bus | green |
| Stewartville | Bus | green |
| Kellogg-Wabasha | Bus | green |
| Twin Cities | Bus | green |
| Dexter | Bus | green |
| Rochester/Twin Cities | Bus | green |
List every stop
- 2nd Ave. SW & 2nd St. SW (West side, Midblock)
- 2nd Ave. SW & 2nd St. SW (East side, Midblock)
- 2nd Ave. SW & 2nd St. SW (East side, North)
- 2nd Ave. SW & 2nd St. SW (East side, South)
- 2nd Ave. SW & 2nd St. SW (West side, South)
- 2nd Ave. SW & 3rd St. SW (East side, Midblock)
- 2nd Ave. SW & 3rd St. SW (East side, North)
- 2nd Ave. SW & 3rd St. SW (West side, Midblock)
- 2nd Ave. SW & 3rd St. SW (West side, North)
- 2nd Ave. SW & 3rd St. SW (West side, South)
- 3rd Ave. SW & 2nd St. SW (Midblock)
- 3rd Ave. SW & 2nd St. SW (North)
- 3rd Ave. SW & 2nd St. SW (South)
- 3rd Ave. SW & 3rd St. SW (Midblock)
- 3rd Ave. SW & 3rd St. SW (North)
- 3rd Ave. SW & 3rd St. SW (South)
- Austin Cenex
- Austin Riverside Arena
- Bloomington East 82nd St. & 28th Ave.
- Byron 2nd Ave. & Frontage Rd.
- Byron 4th St. & 9th Ave. NW
- Byron 4th St. & Byron Ave. NE
- Byron 9th St. & 2nd Ave. NW
- Byron 9th St. & 3rd Ave. NE
- Byron City Commuter Lot
- Cannon Falls Commuter Lot
- Chatfield Main St. & 4th St. SW
- Chatfield Sunshine Foods
- Chester Hwy. 14 & 60th Ave.
- Claremont U.S. 14 & County Rd. 1
- Dexter Lake Geo BP Station
- Dodge Center American Legion
- Dodge Center Park & Ride Lot
- Dover County Rd. 10 & County Rd. 142
- Dover Hwy. 14 & County Rd. 10
- Elgin Commuter Lot
- Eyota Carolann St. & Everett Ave.
- Eyota Front St. & Center Ave.
- Eyota Hwy. 14 & Center Ave.
- Eyota W 5th St. & Lafayette Ave.
- Fountain Post Office
- Grand Meadow Glynn's Motor Mart
- Hampton Park & Ride Lot
- Hayfield Commuter Lot
- Inver Grove Heights Rainbow Foods
- Kasson 1st St. & 2nd Ave. NE
- Kasson Commuter Lot
- Kasson 3rd St. & 8th Ave. NE
- Kasson 4th St. & 2nd Ave. SW
- Kasson 5th St. & 2nd Ave. NW
- Kasson 5th St. & 8th Ave. NW
- Kasson 7th St. & 12th Ave. NW
- Kasson 7th St. & 4th Ave. NE
- Kasson 7th St. & 8th Ave. NE
- Kasson W Main St. & 8th Ave.
- Kellogg Kwik Trip
- Lake City Public Works Parking Lot
- LeRoy City Parking Lot
- Lewiston Commuter Lot
- Marion Service Center
- Oak Center Store
- Pine Island 3rd St. & 3rd Ave. NE
- Plainview 3rd Ave. & 3rd St. SW
- Plainview County Rd. 42 & 2nd Ave. NW
- Plainview St. Joachim's
- Preston Fairgrounds
- Racine Main St. & Pine Ave.
- Reinke's Corners Hwy. 63
- Spring Valley Farmer St. & Section Ave.
- Spring Valley Kwik Trip
- Spring Valley Post Office
- Spring Valley South Side Parking Lot
- Spring Valley Sunshine Foods
- Spring Valley Tracy Rd. & Section Ave.
- Spring Valley Tracy Rd. & Warren Ave.
- St. Charles 12th St. E & Bluff Ave.
- St. Charles 13th St. & Richland Ave.
- St. Charles 13th St. & Whitewater Ave.
- St. Charles 13th St. & East Ave.
- St. Charles Brookwood Commuter Lot
- St. Charles Richland Ave. & 9th St.
- St. Charles Richland Ave. & Hwy. 14
- St. Mary's Hospital
- St. Mary's Hospital
- Stewartville 6th St. & 5th Ave. SE
- Stewartville 6th St. SE at Casey's
- Stewartville County Rd. 120 & Main St.
- Stewartville 2nd St & 2nd Ave SE
- Stewartville Hwy. 30 & 5th Ave.
- Stockton BP Station
- Utica 1st St. & 2nd Ave. NW
- Viola Thomas St. & Viola Rd.
- Wabasha County Rd. 30-Old Fairgrounds
- Winona 61 & Hwy. 14
- Zumbro Falls Water St. Baseball Field (West)
- Zumbrota 495 Main St.
- Zumbrota Hwy. 58 N Commuter Lot
- Rochester Maplewood Square Parking Lot
- Owatonna Southpark Lanes 333 18th St SE
- Lake City Marion & High Street
- Minneapolis
Over time
The producer or measurement contract changed since the prior check, so the trend restarts here. No improvement or regression is claimed across that boundary.
Feed history
Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-11-09 | 54af3348c3c6 | not recorded | Current rubric: see the trend above |
| 2026-10-02 to 2026-11-06 (35 checks) | 54af3348c3c6 | 2016-01-01 | F, 51 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-25 to 2026-10-01 (65 checks) | 54af3348c3c6 | 2016-01-01 | F, 50.9 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-13 to 2026-07-24 (9 checks) | 54af3348c3c6 | 2016-01-01 | F, 50.9 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
| 2026-06-19 to 2026-07-12 (24 checks) | 54af3348c3c6 | 2016-01-01 | F, 50.9 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
Everything we checked
10 findings, ordered by severity.
Show every finding
- Warning101 instances
101 of 101 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 (opens the GTFS Schedule reference on an external site)
- Warning79 instances
79 of 79 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 (opens the GTFS Schedule reference on an external site)
- Warning3 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 for expired_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · Read the fix guide for missing_recommended_field · 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 for missing_feed_contact_email_and_url · 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 for trip_coverage_not_active_for_next7_days · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
On some trips the stop distances run a little past the end of the route line.
The stop and shape distance values don't quite line up, so any math that uses them can drift.
Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide for trip_distance_exceeds_shape_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info4 instances
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Finding code: unknown_column · Read the fix guide for unknown_column · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide for big_gap_in_service · 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).
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 (opens the validator rules on an external site)
How we measured this
Checked for changes 13 days ago; last fetch returned HTTP 403.
The latest run did not download this feed: the host's robots.txt could not be read, and this scorecard does not request a feed until it can. The grade shown was measured on 2026-11-09.
Measured 2 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: provisional.
- Freshness and Realtime quality were not measured this run. They do not count against the grade.
- The archived feed URL on file was unreachable, so the Mobility Database's hosted mirror copy was scored instead.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
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.
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. No service end date could be read, so currency is unknown.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- No service end date could be read, so currency is unknown.
- 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 79 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
Two requirements remain for this feed to earn the conformance mark. No service end date could be read. 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 Not yet
- No service end date could be read.
- 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.
Below the Google and Apple Maps four-week coverage bar. This feed has no service end date, so Maps cannot tell how far ahead it runs. Set a feed_info end date and a calendar that covers at least the next four weeks, then re-export.
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.
A local transit-data support resource is MnDOT Transit. Minnesota's statewide transit program and data resources. This resource supports agencies; it is not a scoring authority.
- Correctness 79 / 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 Not yet published
- 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 52 / 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 Minnesota portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in Minnesota
Other scorecards in Minnesota, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
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/rochester-city-lines/2026-11-09.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-11-09. 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.