Feed status · checked 2026-08-01
Greater Lynchburg Transit Co.
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Virginia.
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.3, validator 8.0.1.
Checked for changes 1 days ago; last changed 38 days 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
713 of 719 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 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
642 of 642 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Remove retired stops from the export, or add them back to the trips that should serve them.Likely your export tool
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.
⏱ A review pass in your scheduling software.worth about +8 points in its category
Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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
- 713 of 719 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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
- Feed evidence
- 642 of 642 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
- Feed evidence
- Some stops exist in the feed but no trip ever stops at them.
- Next action
- Remove retired stops from the export, or add them back to the trips that should serve them.
- 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.
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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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.
Remove retired stops from the export, or add them back to the trips that should serve them. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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 152 days.
- Published accessibility data
- Accessibility information is stated for 0.8% 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 Trillium a fix request
This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 5 kinds of issue across 121 instances (0 error, 76 warning, 45 informational).
Service data covers the next 152 days.
1% of stops state wheelchair accessibility (1% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
1% of stops state accessibility (1% marked accessible). Reflects what the feed states, not verified physical usability.
3 accessibility depth signals
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (8, 10, 12, 12X).
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.
676 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Amelon Rd./Sheetz", "Amelon Rd. & Oakwood Dr. (Inbound)", "Amelon Rd. & Oakland Dr. (Inbound)", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
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 719 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.
- 4 (blue)
- 8 (yellow)
- 11 (red)
- 12 (pink)
- 12X (pink)
- 5 (teal)
- 1A (red)
- 1B (red)
- 2 (purple)
- 3A (purple)
- 3B (purple)
- 9 (yellow)
- 10 (orange)
| Route | Type | Line color |
|---|---|---|
| 4 | Bus | blue |
| 8 | Bus | yellow |
| 11 | Bus | red |
| 12 | Bus | pink |
| 12X | Bus | pink |
| 5 | Bus | teal |
| 1A | Bus | red |
| 1B | Bus | red |
| 2 | Bus | purple |
| 3A | Bus | purple |
| 3B | Bus | purple |
| 9 | Bus | yellow |
| 10 | Bus | orange |
List every stop
- Amelon Rd./Sheetz
- Amelon Rd. & Oakwood Dr. (Inbound)
- Amelon Rd. & Oakland Dr. (Inbound)
- Dixie Airport Rd. & Liggon Rd (Inbound)
- Dixie Airport Rd. & Hidden Stables Ln. (Inbound)
- Dixie Airport Rd. & Galts Mill Rd. (Inbound)
- Wright Shop Rd. & Bryant Rd. (Inbound)
- Wright Shop Rd. & Tyree Cir. (Inbound)
- Wright Shop Rd. & Reichard Dr. (Inbound)
- Fifth St. & Polk St. (Inbound)
- Jackson St. & Garland St.
- Jackson St./3rd St.
- Bank of the James
- Commerce St. & 7th St.
- Downtown YMCA/Lighthouse
- CVCC Campus Dr. & Wards Ferry Rd. (Outbound)
- Wards Ferry Rd. Stop 4
- Fresh Market 1
- Peggy Bowen Dr./Centra Lynchburg Medical Center
- Leesville Rd./Beulah Church
- Leesville Rd./Village Rd. INBOUND
- Leesville Rd./Grandview Cir INBOUND
- Leesville Rd. & Traylor Ln. (INBOUND)
- Leesville Rd. & North St. (Inbound)
- Leesville Rd./Delray Cir. INBOUND
- Leesville Rd. & Bud Dr. (Inbound)
- Simons Run Rd. & Leesville Rd. (Inbound)
- Enterprise Dr./Paulette Cir. INBOUND
- Enterprise Dr. & Goldenrod Dr.
- Enterprise Dr. & Laxton Rd. (INBOUND)
- CVCC Inbound Stop
- Jefferson Ridge Pkwy./Riversedge Warehouse (Outbound)
- Mayflower Dr./ LU Maintenance Facility (Inbound)
- Mayflower Dr. & Young Pl. (Inbound)
- Mayflower Dr. & John Capron (Inbound)
- Mayflower Dr./Bradley Dr. INBOUND
- Bradley Dr./Pepsi Center
- GLTC Operations & Maintenance Facility (Inbound)
- Odd Fellows Rd./ Virginia Career Works (Inbound)
- Odd Fellows Rd./Across From The DMV (Inbound)
- Odd Fellows Rd./FedEx (Inbound)
- Lynchburg Police Department
- Mayflower Dr. & Loop Rd. (Outbund)
- Mayflower Dr. & Young Pl. (Outbound)
- Mayflower Dr. /LU Maintenance Facility (Outbound)
- Fort Ave./Lynchburg Pawn
- Fifth St. & Clay St. (Outbound)
- Sheetz--Forest Rd
- Sheetz
- Campbell Ave./Edmunds St.
- Rivermont Ave. & Vista Ave. (Outbound)
- Bedford Ave. & Rivermont Ave. (Inbound)
- Buchanan and 11th St
- Wadsworth St. Inbound (Park View United Methodist Church)
- Wadsworth St. Outbound (Across from Park View United Methodist Church)
- Logans Landing Apartments
- Old Mill Apartments
- Timberlake Rd./ Just Beyond Burger King (Inbound)
- Jefferson Ridge Pkwy./Tessy Plastics (Outbound)
- Jefferson Ridge Pkwy./Just Past Fire Station (Outbound)
- Jefferson Ridge Pkwy./Just before Sheetz (Inbound)
- Jefferson Ridge Pkwy./Just Past Leharris (Outbound)
- Jefferson Ridge Pkwy. In front of AMG (Outbound)
- Jefferson Ridge Pkwy./Frito-Lay Employee Entrance (Inbound)
- Jefferson Ridge Pkwy./In front of NovaTech (Inbound)
- Old forest Rd./Across From Kwik Stop (Outbound)
- Old Forest Rd./In Front Of Kwik Stop (Inbound)
- Hill St./Clearbrook
- Perrymont Ave. & Alexander St. (Outbound)
- Perrymont Ave. Across From Perrymont Elementary School
- Perrymont Ave. & Thomas Rd. (Outbound)
- Perrymont Ave. & Golf Park Dr. (Inbound)
- Perrymont Ave./Perrymont Elementary School (Inbound)
- Perrymont Ave. & Fairmont Ave. (Inbound)
- Long Meadows Dr. & Igloe Dr. (Outbound)
- Lakeside Dr./Forest Hill Cemetery (Outbound)
- Timberlake Rd./In front Of U-Haul (Outbound)
- Timberlake Rd./Across From Timber Ridge Apartments
- Timberlake Rd./In Front Of Crosspoint Church
- Timberlake Rd./ In front Of Lacaretta (Inbound)
- Timberlake Rd. / In Front Of The Wooden Chair (Inbound)
- Sussex St. & Biltmore Ave. (Inbound)
- GLTC Operations & Maintenance Facility (Outbound)
- Langhorne Rd. & Kingston Ave. (Outbound)
- Old Forest Rd./Lynchburg Gynecology (Outbound)
- Langhorne Rd. & 8th St. (Inbound)
- Wards Ferry Rd. & Melinda Dr. (Inbound)
- Wards Ferry Rd./In front Of College Park Automotive (Inbound)
- Nationwide Dr./Women's Health Clinic
- Nationwide Dr./Centra Lynchburg Medical Center
- Nationwide Dr./Gastroenterology Associates Of Central Virginia
- Maple Ridge Apartments Mailbox Stop (Inbound)
- Amelon Rd. & Amelon Expy. (Inbound)
- Amelon Rd./ Amelon Townhomes
- 7th. & Church St.
- GLTC Bus Parking Lot
- Rivermont Ave. & Columbia Ave.
- Dillard Drive/MACH Solutions
- Best Buy
- Bay 1A
- Bay 1B
- Kemper Street Transfer Station
- Bay 3
- Bay 5/11
- Bay 9
- Bay 2
- Bay 4
- Bay 8
- Bay 10
- Bay 12
- Simons Run/Tru Hotel
- Simons Run/Tru Hotel
- Rivermont Ave./5th St.
- Memorial Ave./Oakridge Blvd.
- Memorial Ave./Oakridge Blvd.
- Memorial Ave./S.Grand Ave.
- Memorial Ave./S.Grand Ave.
- Memorial Ave./Westover Blvd.
- Memorial Ave./Westover Blvd.
- Memorial Ave./Dollar General
- Memorial Ave./Dollar General
- Memorial Ave./Park Ln.
- Memorial Ave./Park Ln.
- Memorial Ave./Page St.
- Memorial Ave./Blue Ridge Therapy Assoc.
- Memorial Ave./J Mart
- Memorial Ave./J Mart
- Rivermont Ave. & Marshall St.
- Bedford Ave./Faquier St.
- Kemper Street Transfer Station
- Fort Ave. & Campbell Ave. (Inbound)
- 15Th St. & Buchanan St. (Outbound)
- 15Th St. & Pierce St. (Outbound)
- 15Th St. & Pierce St. (Inbound)
- 16th St. & Wise St. (Outbound)
- 16Th St.& Floyd St. (Outbound)
- 16th St. & Grace St. (Outbound)
- 16th St. & Monroe St. (Outbound)
- 16th St. & Taylor St. (Outbound)
- 16th St & Filmore St. (Inbound)
- 16th St. & Monroe St. (Inbound)
- 16th St. & Taylor St. (Inbound)
- Lynchburg Police Department
- Albert Lankford Dr. (Genworth, Inbound)
- Albert Lankford Dr./Genworth (Outbound)
- Atherhold Rd./ Just Past CVS
- Atherholt Rd./ The Orthopedic Clinic
- Atherholt Rd./ Across From CVS (Inbound)
- Atherholt Rd./ Centra Cardiovascular Center
- Atherholt Rd./ Forest Health and Rehab
- Atherholt Rd./ Surgery Center Of Lynchburg
- Atlanta Ave./ Wards Corner Shopping Center
- Bedford Ave./Just Past Seven Eleven (Inbound)
- Bedford Ave. & Hollins Mill Rd. (Inbound)
- Bedford Ave. & Fauquier St. (Inbound)
- Bedford Ave. & Monsview Pl. (Inbound)
- Bedford Ave./ Just Past Loudon St. (Inbound)
- Bedford Ave./In front of Dollar General (Inbound)
- Bedford Ave. & Dinwiddle St. (Inbound)
- Bedford Ave. & Magnolia St. (Outbound)
- Bedford Ave. & Cork St. (Outbound)
- Bedford Ave. & Dinwiddie St. (Outbound)
- Bedford Ave. & Grayson St. (Outbound)
- Bedford Ave. & Hawes St. (Outbound)
- Bedford Ave. & Rivermont Ave. (Outbound)
- Birchwood Dr./Hillcrest Apartments
- Birchwood Dr./Birchwood Apartments
- Hill St. & Birchwood Dr. (Inbound)
- Boonsboro Shopping Center
- Boonsboro Rd. & Greenway Ct. (Inbound)
- Boonsboro Rd. & Greenway Ct. (Inbound)
- Boonsboro Rd./Boonsboro Village
- Boonsboro Rd. & Arrow St. (Inbound)
- Boonsboro Rd. & Canterbury Ct. (Inbound)
- Boonsboro Rd. & Clayton Ave. (Inbound)
- Boonsboro Rd. & Linden Ave. (Inbound)
- Boonsboro Rd. & Link Rd. (Inbound)
- Boonsboro Rd. & Mimosa Dr. (Inbound)
- Boonsboro Rd. & Parkland Dr. (Inbound)
- Boonsboro Rd./Kroger
- Boonsboro Rd./Starbucks
- Boonsboro Rd. & Somerset Dr. (Inbound)
- Boonsboro Rd./Across From Kroger
- Boonsboro Rd./Boonsboro Hardware Store
- Boonsboro Rd. & Gorman Dr. (Outbound)
- Boonsboro Rd. & Greenway Ct. (Second Stop)
- Boonsboro Rd. & Greenway Ct. (Outbound)
- Boonsboro Rd. & Old Boonsboro Rd. (Outbound)
- Bradley Dr. & Mayflower Dr. (Outbound)
- Bradley Dr. & Odd Fellows Rd. (Outbound)
- Bradley Dr./N.B. Handy Stop (Outbound)
- Bradley Dr./Pepsi Center
- Buchanon St. & 13th St. (Inbound)
- Buchanan and 12th St
- Buchanon St. (Telephone Pole In Front Of Storage Facility)
- Buchanon St. & 14th St. (Inbound)
- Buena Vista St. & Poplar St. (Inbound)
- Buena Vista St. & Main St. (Outbound)
- Buena Vista St. & Tulip St. (Outbound)
- Cabell St. & G St. (Outbound)
- Cabell St. & I St. (Outbound)
- Cabell St. & Amherst St. (Outbound)
- Campbell Ave. & Dewitt St. (Outbound)
- Campbell Ave. & Easley St. (Outbound)
- Campbell Ave. & Edmunds St. (Outbound)
- Campbell Ave. & Fairview Ave. (Outbound)
- Campbell Ave. & 14th St. (Outbound)
- Campbell Ave. & Hanover St. (Outbound)
- Campbell Ave. & Kent St. (Outbound)
- Campbell Ave. & King St. (Outbound)
- Campbell Ave. & Otey St. (Outbound)
- Campbell Ave. & School Ln. (Outbound)
- Campbell Ave. & Durham St. (Outbound)
- Campbell Ave. & 13th St. (Outbound)
- Campbell Ave. & 12th St. (Outbound)
- Campbell Ave. & Woodrow St. (Outbound)
- Campbell Ave. & Ridge Ave. (Inbound)
- Campbell Ave. & 13th St. (Inbound)
- Campbell Ave. & Dewitt St. (Inbound)
- Campbell Ave. & Easley St. (Inbound)
- Campbell Ave. & Georgia Ave. (Inbound)
- Campbell Ave. & Hughes Ave. (Inbound)
- Campbell Ave. & Idaho Ave. (Inbound)
- Campbell Ave. & King St. (Inbound)
- Campbell Ave. & Mosby Ave. (Inbound)
- Campbell Ave. & Otey St. (Inbound)
- Campbell Ave. & Texas Ave. (Inbound)
- Campbell Ave./ Just Past 12th St. (Inbound)
- Campbell Ave./Foster Electric Co.
- Campbell Ave./In Front Of Burger King
- Candlers Mtn. Rd./Spark Hotel By Hilton
- Candlers Mountain Rd./Candler's Station
- Murray Pl./Wells Fargo (Outbound)
- Candlers Mt. Rd./ TRBC Parking Lot
- Candlers Station
- Candlers Station/Trampoline Park
- Candlers Station/Trampoline Park
- Candlers Station/Hardee's
- Candlers Station
- Caroline St. & York St. (Inbound)
- Caroline St. & Smyth St. (Outbound)
- Caroline St. & Stoneridge St. (Outbound)
- Pulaski St. & Lovell St. (Dearington Apartments)
- Chambers St. & 1st. St. (Outbound)
- Chambers St. & 2nd St. (Outbound)
- Chambers St. & 5th St. (Outbound)
- Chambers St. & Hunt St. (Dearington Apartments)
- Chambers St. & Lovell St. (Dearington Apartments)
- Chambers St. & Pulaski St. (Dearington Apartments)
- Chambers St. & 1st. St. (Inbound)
- and 469 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 81.4 | first check |
| 2026-07-30 | 81.4 | no change |
| 2026-07-31 | 81.4 | no change |
| 2026-08-01 | 81.4 | 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-31.
Same feed file as 2026-07-31; 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
9 findings, ordered by severity.
Show every finding
- Warning713 instances
713 of 719 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 · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning642 instances
642 of 642 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 · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning75 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.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: 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)
- Warning1 instance
This feed describes flexible (demand-responsive) service but has no booking_rules.txt.
Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.
Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)
Finding code: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info34 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info8 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · Read the fix guide · 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.
Flex zones are published but no booking_rules.txt is present.
Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).
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 152 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) 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 642 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
This feed is close to the conformance mark. States wheelchair access on 1% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 152 days.
- Accessible Not yet
- States wheelchair access on 1% 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 75 of 718 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 153 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.
- Correctness 86 / 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 60 / 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.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check 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/greater-lynchburg-transit-co/2026-08-01.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-08-01. 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.