Feed status · checked 2026-11-21

Lane Transit District (LTD)

Based on the feed source on file; publisher ownership is not verified

Service mode Bus

64.2 / 100

unchanged since 2026-11-20

Cataloged in Oregon.

Covers 70 daysAccessibility gaps

The grade is not a count of validator errors. It also weighs freshness and rider information. How the grade works

Checked 2026-11-08: the feed URL on file had stopped working, so this record now tracks feed.ltd.org, the current address Transitland lists for this feed. The agency name and service area in that file match this record. Grades dated before this change came from an older Mobility Database mirror copy.

Top things to fix

Fix 01

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.

This was measured over a realtime sampling window, so it has no feed-wide share.

⏱ Usually a vendor support ticket.worth about +33 points in its category

Fix 02

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.

This was measured over a realtime sampling window, so it has no feed-wide share.

⏱ Usually a vendor support ticket.worth about +33 points in its category

Fix 03

Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.

The service alerts realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.

This was measured over a realtime sampling window, so it has no feed-wide share.

⏱ Usually a vendor support ticket.worth about +33 points in its category

Riders and need behind these fixes

  • No ridership snapshot was on hand when this was built, so annual rider-trips are not known.
  • Oregon 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.

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

  1. Fix 01 · Read the fix guide for scorecard_rt_trip_updates_unreachable

    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.

  2. Fix 02 · Read the fix guide for scorecard_rt_vehicle_positions_unreachable

    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.

  3. Fix 03 · Read the fix guide for scorecard_rt_service_alerts_unreachable

    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 is in 70 days.
Published accessibility data
Accessibility information is stated for 0% 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
No realtime feed was reachable during sampling.

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.

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.

Lane Transit District (LTD)’s published feed lists 28 bus routes, 2,881 scheduled trips and 1,130 stops. Its service dates run from 2026-09-06 through 2027-01-30. It publishes realtime trip updates, vehicle positions and service alerts; when we checked, 0 of 3 answered. The published file last changed on 2026-11-12.

Score by category

Correctness73.2 / 100

The MobilityData validator flagged 5 kinds of issue across 2255 instances (0 error, 2210 warning, 45 informational).

Freshness100.0 / 100

Service data covers the next 70 days.

Rider experience74.1 / 100

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.

Accessibility37.5 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

1 accessibility depth signal

  • 1019 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.

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.

FaresLegacy fares

Fares are applied to trips.

Realtime quality0.0 / 100

Sampled 3 times outside service hours: 0 of 3 configured feeds healthy; vehicle position plausibility was not measurable.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

This feed has 1130 stops.

Skip to route and stop data

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.

  • 01 (green)
  • EmX (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)
Routes in Lane Transit District (LTD)'s feed
RouteTypeLine color
01 Downtown LoopBusgreen
EmXBusgreen
11 ThurstonBusgreen
12 GatewayBusgreen
13 CentennialBusgreen
17 5th Street/Hayden BridgeBusgreen
18 MohawkBusgreen
24 DonaldBusgreen
28 HilyardBusgreen
33 JeffersonBusgreen
36 West 18th Ave.Busgreen
40 Echo HollowBusgreen
41 Barger/West 11th Ave.Busgreen
51 River RoadBusgreen
52 IrvingBusgreen
55 North ParkBusgreen
66 VRC/Coburg RoadBusgreen
67 Coburg Road/VRCBusgreen
79x UO/KinsrowBusgreen
81 LCC/HarrisBusgreen
82 LCC/PearlBusgreen
85 LCC/SpringfieldBusgreen
91 McKenzie BridgeBusgreen
92 Lowell/LCCBusgreen
93 VenetaBusgreen
95 Junction CityBusgreen
96 CoburgBusgreen
98 Cottage GroveBusgreen
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
  • N/S of Marcola Rd. W of 28th
  • 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 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
  • 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
  • W/S of Willamette S of 18th
  • E/S of Willamette S of 20th
  • and 880 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 13 checks — unchanged since 2026-11-20.

2026-11-09: 64.22026-11-10: 64.22026-11-11: 64.22026-11-12: 64.22026-11-13: 64.22026-11-14: 64.22026-11-15: 64.22026-11-16: 64.22026-11-17: 64.22026-11-18: 64.22026-11-19: 64.22026-11-20: 64.22026-11-21: 64.2
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-11-0964.2 first check
2026-11-1064.2 no change
2026-11-1164.2 no change
2026-11-1264.2 no change
2026-11-1364.2 no change
2026-11-1464.2 no change
2026-11-1564.2 no change
2026-11-1664.2 no change
2026-11-1764.2 no change
2026-11-1864.2 no change
2026-11-1964.2 no change
2026-11-2064.2 no change
2026-11-2164.2 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change
  • Realtime quality no change

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.

Feed history by published file
CheckedPublished fileService dates throughGrade at the time
2026-11-12 to 2026-11-21 (10 checks)da0e8b6d71cb2027-01-30Current rubric: see the trend above
2026-11-09 to 2026-11-11 (3 checks)9bfaa5ede0ce2027-01-30Current rubric: see the trend above
2026-10-02 to 2026-11-06 (35 checks)84ccd5ec5bef2026-01-31F, 39.2 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade
2026-07-25 to 2026-10-01 (65 checks)84ccd5ec5bef2026-01-31F, 39.2 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-13 to 2026-07-24 (9 checks)84ccd5ec5bef2026-01-31F, 39.2 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade
2026-06-19 to 2026-07-12 (24 checks)84ccd5ec5bef2026-01-31F, 39.2 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
  • 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.)

    Finding code: scorecard_rt_trip_updates_unreachable · Read the fix guide for scorecard_rt_trip_updates_unreachable · 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.)

    Finding code: scorecard_rt_vehicle_positions_unreachable · Read the fix guide for scorecard_rt_vehicle_positions_unreachable · 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.)

    Finding code: scorecard_rt_service_alerts_unreachable · Read the fix guide for scorecard_rt_service_alerts_unreachable · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)

  • Warning2115 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 for mixed_case_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1130 instances

    1130 of 1130 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)

  • Warning172 instances

    172 of 2881 trips have no headsign, the text that tells riders where the bus is going. A trip counts when it has trip_headsign or a stop_headsign at every stop.

    When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

    Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)

    Finding code: scorecard_missing_headsigns · Read the fix guide for scorecard_missing_headsigns · See GTFS Best Practices (opens GTFS Best Practices on an external site)

  • Warning88 instances

    The feed contains route shapes no trip uses.

    Harmless to riders, but it bloats the feed and suggests stale export data.

    Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)

    Finding code: unused_shape · Read the fix guide for unused_shape · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning6 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 for stop_too_far_from_shape · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    Some route long names repeat the route's short name inside them.

    Apps show both names together, so riders see the number twice, like '5 5 Downtown'.

    Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)

    Finding code: route_long_name_contains_short_name · 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.)

    Finding code: platform_without_parent_station · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

How we measured this

Checked for changes 18 hours ago; last changed 9 days ago.

Measured 4 of 4 score categories from the feed URL on file (publisher not verified).

How we measured this

Confidence in this measurement: high.

  • All four score categories were measured this run.
  • Realtime was sampled in one bounded window of 3 snapshots.
  • The feed was downloaded from the configured feed URL. Publisher ownership of that URL is not verified.

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.5, validator 8.0.1.

NTD GTFS readiness Ready

Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.

Published Ready
Published at a public URL.
Valid Ready
Passes validation with no errors.
Current Ready
Service data covers the next 70 days.
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) Different (allowed)
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. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id LTD to NTD ID 00007, and keep the feed value stable. Do not change it solely to make the two values equal.
shapes.txt covers your trips Ready
All 2881 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

One requirement remains for this feed to earn the conformance mark. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 70 days.
Accessible Not yet
States wheelchair access on 0% of stops and 100% 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 200 checks in the 25 days to 2026-11-22, 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. The window ends at the newest observation, which is not always today: if the monitor stops, this window stops with it.

Clears the Google and Apple Maps four-week coverage bar. This feed has 69 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

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 Oregon ODOT Public Transportation. ODOT's Public Transportation Division, which supports statewide GTFS. This resource supports agencies; it is not a scoring authority.

Correctness 73 / 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 100 / 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 74 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality 0 / 100
GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Part of the Oregon portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Oregon

Other scorecards in Oregon, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

Lane Transit District (LTD): GTFS feed quality grade D, 64.2 of 100, checked 2026-11-21. GTFS 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-11-21.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-21. 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.