Feed status · checked 2026-11-21

Shreveport and Bossier City

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

Service mode Bus

48.4 / 100

Methodology changed; trend restarts here

Cataloged in Louisiana.

Covers 49 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 sportran.rideralerts.com, 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

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

Shreveport and Bossier City’s published feed lists 24 bus routes, 814 scheduled trips and 833 stops. Its service dates run from 2026-11-13 through 2027-01-09. 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-13.

Score by category

Correctness54.0 / 100

The MobilityData validator flagged 8 kinds of issue across 359 instances (0 error, 359 warning, 0 informational).

Freshness81.7 / 100

Service data covers the next 49 days.

Rider experience52.5 / 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.

Accessibility0 / 100

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

2 accessibility depth signals

  • 13 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Hearne / East K, Russell Road, MLK, Highland, Kings Hwy, and more).

    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.

  • 799 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Linwood Ave & Dalzell St (Inbound)", "Dr. Martin Luther King Dr & Ice Cream St", "Linwood Ave & Texas Ave (Outbound)", 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: 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 833 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.

  • Hearne / East K (teal)
  • Line/Linwood (orange)
  • Hearne/Jewella (orange)
  • Youree Dr/ S'Po (brown)
  • N Market/MLK (brown)
  • Greenwood/Pines (gray)
  • Kings Hwy (purple)
  • Lakeshore/Fairg (orange)
  • Line Ave (red)
  • Linwood (blue)
  • North Bossier (pink)
  • Russell Road (pink)
  • Downtown Circul (green)
  • Shreveport Hub (green)
  • Southern Hills (green)
  • Walker/ Pines R (black)
  • Pines Rd/ W. Be (green)
  • MLK (green)
  • Metro Loop 31 (blue)
  • Metro Loop 32 (green)
  • Bossier Hub Con (purple)
  • East Bossier (black)
  • Fairground/Lake (purple)
  • Highland (pink)
Routes in Shreveport and Bossier City's feed
RouteTypeLine color
Hearne / East K Hearne / East Kings HwyBusteal
Line/Linwood Line / LinwoodBusorange
Hearne/Jewella Hearne / JewellaBusorange
Youree Dr/ S'Po Youree / West Bert KounsBusbrown
N Market/MLK North Market / MLKBusbrown
Greenwood/Pines Greenwood / Pines RoadBusgray
Kings Hwy Kings HighwayBuspurple
Lakeshore/Fairg Lakeshore DriveBusorange
Line Ave Line AvenueBusred
Linwood Linwood AvenueBusblue
North Bossier North Bossier LoopBuspink
Russell RoadBuspink
Downtown Circul Downtown CircularBusgreen
Shreveport Hub Southwest ConnectorBusgreen
Southern HillsBusgreen
Walker/ Pines R Walker/ Pines Rd 24Busblack
Pines Rd/ W. Be West ShreveportBusgreen
MLK Dr. Martin Luther King JrBusgreen
Metro Loop 31 Metro Loop 31Busblue
Metro Loop 32Busgreen
Bossier Hub Con Bossier Hub ConnectorBuspurple
East BossierBusblack
Fairground/Lake FairgroundsBuspurple
HighlandBuspink
List every stop
  • Linwood Ave & Dalzell St (Inbound)
  • Dr. Martin Luther King Dr & Ice Cream St
  • Linwood Ave & Texas Ave (Outbound)
  • Meriwether Rd & West Perimeter Rd (Inbou
  • Meriwether Rd & West70th St (Inbound)
  • Jewella Ave & Circle K (Northbound)
  • Olive St & Highland Ave
  • Old Minden & Preston Rd (Outbound)
  • Clear Horizons Apartments (Inbound)
  • Bossier Transfer Stop
  • Intermodal
  • SW Transfer Hub
  • Gateway Hub
  • Murphy St & Allen Ave (Outbound)
  • Murphy St & Pierre Ave (Outbound)
  • Murphy St & Norma Ave (Outbound)
  • Murphy St & Madison Ave (Outbound)
  • Hearne Ave & Murphy St (Outbound)
  • Hearne Ave & Dunlap St (Outbound)
  • Hearne Ave & Lakeshore Dr (Outbound)
  • Hearne Ave & West College St (Outbound)
  • Hearne & Stonewall (Outbound)
  • Hearne Ave & Catherine St (Outbound)
  • Hearne Ave & Penick St (Outbound)
  • Hearne Ave & Kings Hwy (Outbound)
  • Hearne Ave & Emery St (Outbound)
  • Hearne Ave & Regent St (Outbound)
  • Hearne Ave & Midway Ave (Outbound)
  • Hearne Ave & Malcolm St (Outbound)
  • Hearne Ave & Corbitt St (Outbound)
  • Hearne Ave & Morningside Dr (Outbound)
  • Hearne Ave & Hollywood Ave (Outbound)
  • Hearne Ave & Waggoner St (Outbound)
  • Hearne Ave & Hillcrest (Outbound)
  • Hearne Ave & Sunnybrook (Outbound)
  • Hearne Ave & Amherst St (Outbound)
  • Hearne Ave & Elmhurst (Outbound)
  • West 70th St & Southern Oaks Apts (Inbou
  • West 70th St & Wyngate Blvd (Inbound)
  • West 70th St & Union St (Outbound)
  • West 70th St & Linwood Ave (Outbound)
  • West 70th St & Linwood Ave (Inbound)
  • West 70th St & Wallace Ave (Outbound)
  • West 70th St & Fox Creek Apts (Inbound)
  • Mansfield Rd & Elmhurst St (Inbound)
  • Hearne Ave & Hillcrest Ave (Inbound)
  • Hearne Ave @ Super 1 (Inbound)
  • Hearne Ave & Hollywood Ave (Inbound)
  • Hearne Ave & Morningside (Inbound)
  • Hearne Ave & Corbitt St (Inbound)
  • Hearne Ave & Midway Ave (Inbound)
  • Hearne Ave & Regent St (Inbound)
  • Hearne Ave & Emery St (Inbound)
  • Hearne Ave & Edgar St (Inbound)
  • Hearne Ave & Willis Knighton (Inbound)
  • Hearne Ave & Catherine St (Inbound)
  • Hearne & Stonewall (Inbound)
  • Hearne Ave & W College St (Inbound)
  • Hearne Ave & Lakeshore (Inbound)
  • Hearne Ave & Dunlap St (Inbound)
  • Murphy St & Andrew Ave (Inbound)
  • Murphy Ave & Madison Ave (Inbound)
  • Murphy St & Norma Ave (Inbound)
  • Murphy Ave & Pierre Ave (Inbound)
  • Murphy St & Allen Ave (Inbound)
  • Allen Ave & Weinstock St (Outbound)
  • Allen Ave & Milam St (Outbound)
  • Allen Ave & Abbie St (Outbound)
  • Allen Ave & Garden St (Outbound)
  • Ford St & Pierre Ave (Outbound)
  • Ford St & Leroy St (Outbound)
  • Alston & Webster (Outbound)
  • Alston & Clay St (Outbound)
  • North Holzman & Alston (Outbound)
  • North Holzman & Ford St (Outbound)
  • Earnest B. Miller & Oregon (Outbound)
  • Earnest B Miller & JS Clark (Outbound)
  • Ford St & Hearne Ave (Outbound)
  • Hearne Ave & Aero Dr (Outbound)
  • Hearne Ave & Forum Dr (Outbound)
  • Amazon (Outbound)
  • North Market & Barton St (Outbound)
  • STOP 00000026
  • Dr. Martin Luther King Dr & Montana (Out
  • MLK Dr & Willis St (Outbound)
  • Dr. Martin Luther King Dr. & Russell Rd
  • Dr. Martin Luther King Dr. & Jones Mabry
  • Jones Mabry Rd & Freddie St (Outbound)
  • Jones Mabry Rd & Hanna St (Outbound)
  • Legardy St & Green Oaks (Outbound)
  • Legardy St & Freddie St (Outbound)
  • Willie Mays & Caldwell St (Outbound)
  • Willie Mays & Avocado St (Outbound)
  • Audrey Ln & Peach St (Outbound)
  • Audry Ln & 5th St (Outbound)
  • 5th St & David Raines (Outbound)
  • David Raines & Peach St (Outbound)
  • MLK & David Raines (Inbound)
  • David Raines & Skelly St (Inbound)
  • David Raines & Tulsa St (Inbound)
  • David Raines Rd & Kings Garden Ln (Inbou
  • Round Grove & Markham St (Inbound)
  • Round Grove & Audrey Ln (Inbound)
  • Audrey Ln & Kelsey St (Inbound)
  • Audrey Ln & Hersey D. Wilson Dr (Inbound
  • Hersey D Wilson Dr & Linear St (Inbound)
  • Hersey D Wilson Dr & Legardy St (Inbound
  • Legardy St & Kelsey St (Inbound)
  • North Market & Dr. Martin Luther King Dr
  • North Market & Kitty Ln (Inbound)
  • North Market & Capital One (Inbound)
  • North Market St & County Market (Inbound
  • North Market & Barton St (Inbound)
  • North Market & McDonald’s (Inbound)
  • Fullerton & Hearne Ave (Inbound)
  • Hearne Ave & Forum Dr (Inbound)
  • Hearne Ave & Aero Dr (Inbound)
  • JS Clark (Inbound)
  • Ford St & Earnest B. Miller (Inbound)
  • Holtzman Ave & Grover St (Inbound)
  • Clay St & Canaan Towers Apts (Inbound)
  • Alston & Webster (Inbound)
  • Ford St & Leroy St (Inbound)
  • Ford St & Allen Ave (Inbound)
  • Allen Ave & Garden St (Inbound)
  • Allen Ave & Abbie St (Inbound)
  • Allen Ave & Milam St (Inbound)
  • Allen Ave & Weinstock St (Inbound)
  • Pete Harris & Peabody St (Outbound)
  • Pete Harris & Hope St (Outbound)
  • Pete Harris & Fannin St (Outbound)
  • Caddo St & Baker St (Outbound)
  • Caddo St & Louisiana Ave (Outbound)
  • Caddo St & Edwards St (Outbound)
  • Market St & Cadillac St (Northbound)
  • North Market & Fortson St (Outbound)
  • Market St & Kansas City Ave (Northbound)
  • Kansas City & Hawn (Outbound)
  • Kansas City & Burt St (Outbound)
  • Shreveportran Headquarters Westbound (Ou
  • Jack Wells & Simmonds (Outbound)
  • Jack Wells & Mayfair (Outbound)
  • Jack Wells & North Thomas (Outbound)
  • Hearne Ave & Grimmett Dr (Outbound)
  • Grimmett Dr & Algonquin Trail (Outbound)
  • Northwood 2 Apartments (Outbound)
  • Grimmett Dr Apartments (Outbound)
  • Nelson St & North Market (Outbound)
  • North Market & Royal Inn (Outbound)
  • North Market & Vo-Tech (Outbound)
  • Dr. Martin Luther King Dr. & Legardy St
  • Dr. Martin Luther King Dr. & Audrey Ln (
  • Dr. Martin Luther King Dr. & Hill St (Ou
  • Dr. Martin Luther King Dr. Transfer Stop
  • Dr. Martin Luther King Dr. & SUSLA (Outb
  • Cypress Landing Apartments (Outbound)
  • Dr. Martin Luther King Dr. & Downing St
  • Ironwood & Roy Rd (Outbound)
  • Hilry Huckaby & Caliburn (Outbound)
  • Hilry Huckaby & Sidney St (Outbound)
  • Hilry Huckaby & Redstone (Outbound)
  • SUSLA & Dr. Martin Luther King Dr (Outbo
  • Dr. Martin Luther King Dr. & David Raine
  • Dr. Martin Luther King Dr.& Hill St (Inb
  • Dr. Martin Luther King Dr. & Audrey (Inb
  • Dr. Martin Luther King Dr. & Linear St (
  • Dr. Martin Luther King Dr. & Legardy St
  • Dr. Martin Luther King Dr. & Joe Louis (
  • Dr. Martin Luther King Dr. & Russell Rd
  • Dr. Martin Luther King Dr & Ice Cream St
  • Dr. Martin Luther King Dr & Montana (Inb
  • North Market & Nelson St (Inbound)
  • Grimmett Dr Apartments (Inbound)
  • Northwood 2 Apartments (Inbound)
  • North Hearne @ Bench(Inbound)
  • North Thomas & Jack Wells (Inbound)
  • Jack Wells & Mayfair (Inbound)
  • Jack Wells & Simmonds (Inbound)
  • Kansas City & Burt St (Inbound)
  • Kansas City & Hawn (Inbound)
  • Kansas City & Grimmett Dr (Inbound)
  • Kansas City & McKinney Ave (Inbound)
  • Market St & Montgomery St (Southbound)
  • North Market & North Common St (Inbound)
  • Market St & Ricou St (Southbound)
  • Caddo St & Edwards St (Inbound)
  • Caddo St & Louisiana Ave (Inbound)
  • Caddo St & Baker St (Inbound)
  • Pete Harris & Garden St (Inbound)
  • Pete Harris & Jewell St (Inbound)
  • East 70th St & Southern Ave (Outbound)
  • East 70th St & Fairfield Ave (Outbound)
  • East 70th St & Line Ave (Outbound)
  • East 70th St & Bethany St (Outbound)
  • East70th St & Creswell Rd (Outbound)
  • East70th St & Fern Ave (Outbound)
  • E 70th St @ Chili's (Inbound)
  • E. 70th St @ La-Z-Boy (Inbound)
  • 1396 E 70th St, (Inbound)
  • 1001 E. 70th St (Inbound)
  • E.70th St & Line Ave (Inbound)
  • East 70th St & Fairfield Ave (Inbound)
  • E 70th St & University Dr (Outbound)
  • Youree Dr & Walmart (Outbound)
  • LSUS (Inbound)
  • University Pl & Youree Dr (Inbound)
  • Youree Dr & University Apts (Inbound)
  • Youree Dr & Portico Shopping Center (Inb
  • Youree Dr & Regal Dr (Inbound)
  • Regal Dr & JCPenney's
  • East Kings & East 70th St (Inbound)
  • East Kings & Gator Dr (Inbound)
  • East Kings & King Crossing (Inbound)
  • East Kings & Drug Emporium (Inbound)
  • Southfield Dr & Anniston (Inbound)
  • Southfield Dr & Youree Dr (Inbound)
  • Pierremont Rd & Fern Ave (Inbound)
  • Pierremont Rd & Creswell Ave (Inbound)
  • Pierremont Rd & Line Ave (Inbound)
  • Pierremont Rd & Fairfield (Inbound)
  • Southern Ave & East60th St (Inbound)
  • Southern Ave & East 66th St (Inbound)
  • Southern Ave & East 69th St (Inbound)
  • Texas Ave & Grand Ave (Outbound)
  • Fairmont Apartment (Inbound)
  • Texas St & Common St (Outbound)
  • Diamond Jacks Casino
  • Benton Spur & Benton Rd (Outbound)
  • Benton Rd & East Texas St/Bossier Civic
  • East Texas St & Bossier City Hall (Outbo
  • East Texas Saint & Beckett St (Outbound)
  • East Texas & Thrifty Liquor (Outbound)
  • East Texas & Six Fountain Dr (Outbound)
  • East Texas & Mary Kay St (Outbound)
  • East Texas & Regina St (Outbound)
  • East Texas & Swan Lake (Outbound)
  • East Texas & Villaggio (Outbound)
  • Village at the Downs (Outbound)
  • BPCC/CSC (Outbound)
  • Louisiana Downs (Inbound)
  • BPCC/CSC (Inbound)
  • Village at the Downs (Inbound)
  • Texas St at Sergios (Inbound)
  • Swan Lake & East Texas (Inbound)
  • Swan Lake & O'Keefe (Inbound)
  • Shed Rd & Laudon (Inbound)
  • Shed Rd & Lampkin (Inbound)
  • Shed Rd & Alpine St (Inbound)
  • Shed Rd & Shiloh St (Inbound)
  • Shed Rd & Hood St (Inbound)
  • and 583 more (see the full list on the map or in the GeoJSON)

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.

Feed history by published file
CheckedPublished fileService dates throughGrade at the time
2026-11-2194eff7a32cfc2027-01-09Current rubric: see the trend above
2026-11-13 to 2026-11-20 (8 checks)94eff7a32cfc2027-01-09D, 60.9 under rubric 1.5, an earlier scoring contract; not comparable with today’s grade
2026-11-09 to 2026-11-12 (4 checks)d71f3c4533042027-01-09F, 51.4 under rubric 1.5, an earlier scoring contract; not comparable with today’s grade
2026-10-18 to 2026-11-06 (19 checks)508d50d65f482099-12-31F, 34.7 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade
2026-07-26 to 2026-10-17 (80 checks)508d50d65f482099-12-31F, 34.7 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-15 to 2026-07-25 (8 checks)508d50d65f482099-12-31F, 34.7 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade
2026-06-20 to 2026-07-14 (25 checks)508d50d65f482099-12-31F, 34.7 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade

Everything we checked

14 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)

  • Warning833 instances

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

  • Warning814 instances

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

  • Warning267 instances

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

  • Warning34 instances

    Some scheduled trips move faster between stops than a bus can.

    Usually a typo'd stop time; riders get arrival times no bus can meet.

    Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)

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

  • Warning19 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)

  • Warning15 instances

    Route short name too long (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

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

  • Warning11 instances

    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)

  • Warning7 instances

    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)

  • Warning5 instances

    On some trips the stops fall along the route line in a different order than the schedule lists.

    Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.

    Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)

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

  • 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 18 hours ago; last changed 8 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 49 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 814 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 0% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 49 days.
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 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 48 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 54 / 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 82 / 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 52 / 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 Louisiana portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Louisiana

Other scorecards in Louisiana, 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.

Shreveport and Bossier City: GTFS feed quality grade F, 48.4 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/shreveport-and-bossier-city/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.