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
Lane Transit District (LTD)
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 13% of all tracked agencies and 25% of large agencies. Operates in Oregon.
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 14 minutes ago; last fetch returned HTTP 404.
Measured 4 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: medium.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- The agency's own feed URL 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.
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 159 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
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The trip updates realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
⏱ Usually a vendor support ticket.worth about +8 points
Agencies here usually clear this within about 1 week (based on 11 observed fixes).
Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The vehicle positions realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
⏱ Usually a vendor support ticket.worth about +8 points
Agencies here usually clear this within about 1 week (based on 9 observed fixes).
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.
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.
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.
Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
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.
Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
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 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 7 kinds of issue across 2463 instances (0 error, 2418 warning, 45 informational).
Service data ended 159 day(s) ago. Trip planners have likely already dropped this feed.
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.
Fares are applied to trips.
Sampled 9 times outside service hours: 0 of 3 feeds healthy.
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.
- 01 (green)
- 103 (green)
- 11 (green)
- 12 (green)
- 13 (green)
- 17 (green)
- 18 (green)
- 24 (green)
- 28 (green)
- 33 (green)
- 36 (green)
- 40 (green)
- 41 (green)
- 51 (green)
- 52 (green)
- 55 (green)
- 66 (green)
- 67 (green)
- 79x (green)
- 81 (green)
- 82 (green)
- 85 (green)
- 91 (green)
- 92 (green)
- 93 (green)
- 95 (green)
- 96 (green)
- 98 (green)
| Route | Type | Line color |
|---|---|---|
| 01 Downtown Loop | Bus | green |
| 103 EmX | Bus | green |
| 11 Thurston | Bus | green |
| 12 Gateway | Bus | green |
| 13 Centennial | Bus | green |
| 17 5th Street/Hayden Bridge | Bus | green |
| 18 Mohawk | Bus | green |
| 24 Donald | Bus | green |
| 28 Hilyard | Bus | green |
| 33 Jefferson | Bus | green |
| 36 West 18th Ave. | Bus | green |
| 40 Echo Hollow | Bus | green |
| 41 Barger/West 11th Ave. | Bus | green |
| 51 River Road | Bus | green |
| 52 Irving | Bus | green |
| 55 North Park | Bus | green |
| 66 VRC/Coburg Road | Bus | green |
| 67 Coburg Road/VRC | Bus | green |
| 79x UO/Kinsrow | Bus | green |
| 81 LCC/Harris | Bus | green |
| 82 LCC/Pearl | Bus | green |
| 85 LCC/Springfield | Bus | green |
| 91 McKenzie Bridge | Bus | green |
| 92 Lowell/LCC | Bus | green |
| 93 Veneta | Bus | green |
| 95 Junction City | Bus | green |
| 96 Coburg | Bus | green |
| 98 Cottage Grove | Bus | green |
This feed has 1135 stops.
List every stop
- E/S of 58th N of Main
- E/S of 58th S of D
- E/S of 58th S of Thurston Rd
- S/S of Thurston W of 64th
- S/S of Thurston E of 65th
- S/S of Thurston W of 66th
- S/S of Thurston W of 67th
- S/S of Thurston E of 68th
- W/S of 69th S of G
- W/S of 69th N of D
- W/S of 69th N of Main St
- N/S of Main W of 68th
- N/S of Main W of 66th
- N/S of Main E of 62nd Pl
- N/S of Main W of 60th Pl
- N/S of Main W of 58th
- S/S of Main E of 54th
- N/S of Main W of 54th
- S/S of Main E of 52nd Pl
- N/S of Main E of 52nd
- S/S of Main E of 51st
- N/S of Main E of 50th
- N/S of Main W of 49th
- S/S of Main W of 48th
- N/S of Main W of 48th
- N/S of Main E of 44th
- S/S of Main E of 44th
- S/S of Main E of 42nd
- N/S of Main W of 42nd
- S/S of Main W of 41st
- N/S of Main W of 41st
- S/S of Main E of 38th
- N/S of Main E of 38th
- N/S of Main W of 35th
- S/S of Main W of 35th
- S/S of Main E of 32nd
- N/S of Main E of 32nd
- S/S of Main E of 28th
- N/S of Main E of 28th
- S/S of Main E of 23rd
- N/S of Main E of 23rd
- N/S of Main W of 23rd
- S/S of Main E of 21st
- N/S of Main E of 20th
- N/S of Main E of 18th
- N/S of Main W of 16th
- N/S of Main W of 14th
- N/S of Main E of 12th
- N/S of Main E of 10th
- N/S of Main W of Mill
- W/S of Mohawk N of G
- S/S of South A E of 14th
- S/S of Olympic E of Mohawk
- N/S of Olympic E of 18th
- S/S of Olympic E of 18th
- N/S of Olympic W of 23rd
- S/S of Olympic W of 28th
- S/S of Marcola Rd. W of 28th
- E/S of 28th N of R
- S/S of Olympic E of 21st
- N/S of Olympic E of 23rd
- N/S of Harlow Road W of Beverly
- S/S of Harlow Rd W of Beverly
- E/S of Gateway N of Gateway Lp
- W/S of Gateway N of Gateway Lp
- E/S of Gateway N of Kruse
- E/S of 5th N of Q
- E/S of 5th S of T
- E/S of 5th S of V
- S/S of Hayden Bridge Rd E of Mintmeadow Way
- S/S of Hayden Bridge Rd E of 10th
- S/S of Hayden Bridge Rd E of 17th Place N
- S/S of Hayden Bridge Rd E of Harvest Lane
- S/S of Hayden Bridge Rd E of 15th
- W/S of 19th S of Otto
- W/S of 19th S of Rambling Drive
- W/S of 19th N of Marcola
- W/S of Q N of 18th
- N/S of Q W of 16th
- N/S of Q E of 12th
- N/S of Q W of 11th
- N/S of Q W of 10th
- N/S of Q W of 7th
- E/S of 21st N of L
- S/S of Centennial W of 21st
- S/S of Centennial E of 18th
- S/S of Centennial E of 16th
- S/S of Centennial W of Market
- N/S of Centennial W of Market
- S/S of Centennial E of 12th
- N/S of Centennial W of 12th
- S/S of Centennial E of 10th
- N/S of Centennial W of 10th
- S/S of Centennial E of 7th
- N/S of Centennial W of 7th
- N/S of Centennial W of 5th
- S/S of Centennial E of Custom
- N/S of Centennial E of 1st
- S/S of Centennial W of Pioneer Pkwy W
- N/S of Centennial W of Prescott
- S/S of Centennial E of Prescott
- N/S of Centennial W of Rainbow
- S/S of Centennial W of Rainbow Dr
- S/S of Centennial E of Aspen
- N/S of Centennial W of Aspen
- S/S of Centennial E of Anderson
- N/S of Centennial E of Anderson
- W/S of Mohawk S of Olympic
- W/S of Mohawk S of M
- E/S of Mohawk N of G
- E/S of Mohawk N of Modoc
- E/S of Mohawk N of Centennial
- E/S of Mohawk N of M
- N/S of G E of 12th
- S/S of G E of 12th
- N/S of G E of 10th
- N/S of G W of 7th
- S/S of G W of 7th
- W/S of 5th N of Moffitt
- E/S of 5th N of Moffitt
- E/S of 5th N of L
- W/S of 5th N of L
- W/S of 5th N of Broadway
- E/S of 5th S of Broadway
- W/S of 5th S of G
- E/S of 5th N of G
- E/S of 5th N of E
- S/S of Centennial W of 6th
- S/S of Thurston E of 61st
- N/S of Centennial W of Mill
- S/S of Centennial W of Mill
- N/S of Centennial W of Laura
- S/S of Centennial W of Laura
- S/S of South A W of 18th
- N/S of Harlow W of Garden Way
- S/S of Harlow E of Garden Way
- S/S of Harlow E of Honeysuckle
- N/S of Harlow W of Honeysuckle
- N/S of Harlow W of Van Duyn
- S/S of Harlow E of Randall
- N/S of Harlow W of Vincent
- S/S of Harlow W of Palomino
- N/S of Harlow E of Tomahawk
- S/S of Harlow E of Lydick
- N/S of Harlow W of Lydick
- E/S of Oakway S of Westwood
- E/S of Oakway N of Bedford
- W/S of Oakway S of Bedford
- W/S of Oakway S of St Andrews
- E/S of Oakway N of St Andrews
- E/S of Oakway S of Lariat
- W/S of Oakway S of Lariat
- E/S of Oakway S of Sandy
- W/S of Oakway N of Law
- W/S of Oakway S of Roland
- E/S of Oakway N of Roland
- S/S of Crescent W of Coburg Rd
- N/S of Crescent W of Coburg Rd
- N/S of Crescent E of Chuckanut
- S/S of Crescent E of Chuckanut
- N/S of Crescent E of Sarah
- S/S of Crescent W of Gay
- N/S of Crescent E of Coach
- S/S of Crescent E of Coach
- N/S of Crescent E of Gilham
- N/S of Crescent E of Tulip
- W/S of Gilham S of Brewer
- S/S of G E of 10th
- N/S of 6th W of Willamette
- E/S of Hilyard S of 22nd
- N/S of 18th W of Alder
- W/S of Gilham S of Terresa
- E/S of Hilyard S of 24th
- W/S of Patterson S of 19th
- W/S of Patterson N of 22nd
- W/S of Hilyard N of 26th
- W/S of Hilyard N of 28th
- W/S of Hilyard S of 30th
- W/S of Hilyard S of 34th
- W/S of Hilyard S of 36th
- W/S of W. Amazon S of 37th
- W/S of W. Amazon S of 39th Pl
- W/S of W. Amazon N of Fox Hollow
- W/S of W. Amazon N of 44th
- W/S of W. Amazon N of Larch
- W/S of W. Amazon S of Snell
- W/S of W. Amazon S of Sprague
- W/S of W. Amazon N of Martin
- S/S of Martin W of Center
- E/S of Center N of Alpine
- E/S of Center S of E. Amazon
- E/S of E. Amazon N of Snell
- E/S of E. Amazon N of Dillard
- E/S of E. Amazon N of Kincaid
- E/S of E. Amazon S of Potter
- E/S of E. Amazon S of 39th
- E/S of E. Amazon N of 37th
- E/S of E. Amazon N of 35th
- E/S of E. Amazon S of Hilyard
- E/S of Hilyard N of 28th
- E/S of Hilyard N of 19th
- E/S of Hilyard S of 17th
- S/S of 18th W of Four Oaks Grg
- N/S of 18th W of Langton
- E/S of 18th N of Churchill
- N/S of 18th E of Josh
- S/S of 18th W of Peppertree
- N/S of 18th E of Peppertree
- N/S of 18th 2nd stop W of Bailey Hill
- S/S of 18th 1st stop W of Bailey Hill
- N/S of 18th 1st stop W of Bailey Hill
- S/S of 18th W of Mistletoe
- N/S of 18th W of Mistletoe
- S/S of 18th E of Quaker
- N/S of 18th W of Quaker
- S/S of 18th W of Buck
- N/S of 18th W of Buck
- S/S of 18th E of Greiner
- N/S of 18th W of Oak Patch
- N/S of 18th W of Wilson
- S/S of 18th W of McKinley
- N/S of 18th W of City View
- S/S of 18th E of City View
- N/S of 18th W of Arthur
- S/S of 18th E of Arthur
- N/S of 18th E of Garfield
- N/S of 18th W of Grant
- S/S of 18th W of Grant
- S/S of 18th E of Chambers
- N/S of 18th E of Chambers
- N/S of 18th W of Polk
- S/S of 18th E of Polk
- N/S of 18th W of Van Buren
- S/S of 18th W of Jackson
- S/S of 18th W of Friendly
- N/S of 18th W of Friendly
- N/S of 18th W of Madison
- S/S of 18th W of Madison
- S/S of 18th E of Jefferson
- N/S of 18th E of Jefferson
- S/S of 18th E of Lawrence
- N/S of 18th W of Lincoln
- S/S of 18th W of Charnelton
- N/S of 18th W of Willamette
- S/S of 24th E of Chambers
- E/S of Chambers S of 25th
- E/S of Chambers S of North View
- W/S of Willamette S of 14th
- W/S of Willamette S of 12th
- W/S of Willamette S of 16th
- and 885 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 20 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 39.2 | first check |
| 2026-06-20 | 39.2 | no change |
| 2026-06-21 | 39.2 | no change |
| 2026-06-22 | 39.2 | no change |
| 2026-06-23 | 39.2 | no change |
| 2026-06-24 | 39.2 | no change |
| 2026-06-25 | 39.2 | no change |
| 2026-06-26 | 39.2 | no change |
| 2026-06-27 | 39.2 | no change |
| 2026-06-28 | 39.2 | no change |
| 2026-06-29 | 39.2 | no change |
| 2026-06-30 | 39.2 | no change |
| 2026-07-01 | 39.2 | no change |
| 2026-07-02 | 39.2 | no change |
| 2026-07-04 | 39.2 | no change |
| 2026-07-05 | 39.2 | no change |
| 2026-07-06 | 39.2 | no change |
| 2026-07-07 | 39.2 | no change |
| 2026-07-08 | 39.2 | no change |
| 2026-07-09 | 39.2 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality no change
What changed in this feed
Overall grade and score held steady since 2026-07-08.
Same feed file as 2026-07-08; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
- Error1 instance
Service data ended 159 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.)
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
Validator rule: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Error1 instance
The trip updates realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)
Agencies here usually clear this within about 1 week (based on 11 observed fixes).
Validator rule: scorecard_rt_trip_updates_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Error1 instance
The vehicle positions realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)
Agencies here usually clear this within about 1 week (based on 9 observed fixes).
Validator rule: scorecard_rt_vehicle_positions_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Error1 instance
The service alerts realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_rt_service_alerts_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Warning2951 instances
2951 of 2951 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)
- Warning2405 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.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1135 instances
1135 of 1135 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)
- Warning6 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)
- 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.)
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)
- 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.)
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
Validator rule: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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.)
Agencies here usually clear this within about 2 weeks (based on 8 observed fixes).
Validator rule: missing_recommended_field · Read the fix guide · 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.)
Agencies here usually clear this within about 1 week (based on 31 observed fixes).
Validator rule: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info45 instances
Platform without parent station (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'platform_without_parent_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: platform_without_parent_station · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
1024 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("E/S of 58th N of Main", "E/S of 58th S of D", "E/S of 58th S of Thurston Rd", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
NTD certification readiness Not ready
Resolve this before you certify on the D-10. Service data expired 159 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 159 days ago, so FTA would find the link out of date.
- agency_id matches your NTD ID Not aligned
- Your feed's agency_id is LTD; your National Transit Database ID is 00007. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id, so a difference here is a heads-up, not an error. Optionally set the agency_id for your service to 00007 in agency.txt (and the matching agency_id in routes.txt) so the feed lines up with your NTD record. It is a convenience, not a required feed change: FTA also links agency_id to your NTD ID on your P-50 form.
- shapes.txt covers your trips Ready
- All 2951 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 expired 159 days ago. 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
- Service data expired 159 days ago.
- 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.
Realtime reliability
The realtime feed responded on 0.0% of 105 checks over the last 16 days, with lag not reported by the feed.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
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
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.
Your state runs a transit-data program that can help: Oregon ODOT Public Transportation. ODOT's Public Transportation Division, which supports statewide GTFS. Your state publishes no quality rubric of its own, so the closest published bars a program can hold this feed to are the federal and industry ones below; the score maps to those.
- Correctness 69 / 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 0 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 60 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: stop names and headsigns.
- Realtime quality 0 / 100
- 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/lane-transit-district-ltd/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.