Feed status · checked 2026-08-01
The Jule
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Iowa.
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 68 minutes ago; last fetch returned HTTP 404.
Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: provisional.
- Realtime quality was not measured this run. It does not count against the grade.
- The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 2619 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category
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
233 of 233 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
676 of 676 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
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
- Service data ended 2619 day(s) ago.
- Next action
- Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service 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
- Feed evidence
- 233 of 233 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
- 676 of 676 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
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.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
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_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. 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.
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. 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 was 2619 days ago.
- 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
- No fare information is published in the feed.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 6 kinds of issue across 32 instances (0 error, 32 warning, 0 informational).
Service data ended 2619 day(s) ago. Trip planners have likely already dropped this feed.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (GREY, 4M, PARK+).
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.
202 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("9th and Iowa St.", "9th St and Locust St", "Hill St and 5th St", 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.
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 233 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.
- BRWN. (gray)
- X (black)
- GRN (green)
- ORNG (yellow)
- ORNG. (yellow)
- BLUE (blue)
- GREY (gray)
- PINK (pink)
- NR (teal)
- GRN. (green)
- BRWN (gray)
- PARK+ (green)
- 4M (red)
- PRPL (purple)
| Route | Type | Line color |
|---|---|---|
| BRWN. Kohls/HyVee | Bus | gray |
| X Express Nonstop | Bus | black |
| GRN Jackson/Central | Bus | green |
| ORNG Clarke/Senior/W Locust | Bus | yellow |
| ORNG. Senior/W Locust/Loras | Bus | yellow |
| BLUE Hill/Mercy | Bus | blue |
| GREY Pennsylvania/Asbury | Bus | gray |
| PINK Rhomberg/Kerper | Bus | pink |
| NR Nightrider | Bus | teal |
| GRN. Windsor/Jackson | Bus | green |
| BRWN Kohls/HyVee | Bus | gray |
| PARK+ PARK & RIDE | Bus | green |
| 4M Four Mounds | Bus | red |
| PRPL PURPLE | Bus | purple |
List every stop
- Loras Blvd and Alta Vista St
- University Ave and Finley St
- Pennsylvania Ave and Chaney Rd
- Clarke Dr and Foye St
- Pennsylvania Ave and Butterfield Dr
- Windsor Ave and Linwood Cemetery
- West Locust at Clarke University Trail
- Windsor Ave and Goethe St
- River Edge Plaza Parking Lot
- Pennsylvania Ave and Lenox St
- Clarke Dr and Harold St
- JFK Rd and Key Way
- Walmart
- Asbury Rd and Green St
- Asbury Rd and Southway St
- Main St and 12th St
- Lake Ridge Dr
- Iowa St and 12th St
- Clarke University
- Jackson St and 30th St
- Kirkwood St. at Cox St.
- Loras Blvd and Glen Oak St
- Rhomberg Ave and Shiras St
- Windsor Ave and Clinton St
- Mindframe Theatre
- South Grandview Ave and Rockdale Rd
- Pennsylvania Ave at Lenox St
- University of Dubuque at N Algona
- Radford Ct
- Petco
- Locust St and Kirkwood St
- 32nd St and Saunders St
- Windsor Ave and Henry St
- Chanvenelle Rd at Radford Rd
- Rhomberg Ave at Fengler St
- North Grandview Ave and Delaware St
- Elm St and 16th St
- JFK Rd and Foothill Dr
- Pennsylvania Ave and Donovan Dr
- Hill St and 3rd St
- Asbury Rd and Cherry St
- Humane Society
- Putnam St and Broadway St
- W 3rd and Alpine
- JFK Rd and Carter Rd
- Clarke Drive and Madison St
- Pennsylvania Ave at Penn Place Apartments
- White St and 22nd St
- Holliday Dr at Goodwill
- 1684 Wingate Dr
- 4th St at Central Ave
- Kaufmann Ave and Crissy Dr
- Asbury Rd and Poplar St
- JFK Circle Transfer
- Loras Blvd and Cornell St
- Windsor Ave and Padre Pio Dr
- Burden St and Groveland Pl
- Shopko
- Pennsylvania Ave at Irving School
- Windsor Ave and Hennepin St
- Ice Harbor Dr
- Jackson St and 19th St
- 32nd St and Central Ave
- White St and 13th St
- Kaufmann Ave and Chaney Rd
- Grandview Ave and Algona St
- Rhomberg Ave and Windsor Ave
- Target
- Senior High School
- Rhomberg Ave and Stafford St
- Chaney Rd at The Forum
- Kerper Blvd at 16th St
- Delhi St and 5th St
- 9th and Iowa St.
- Pennsylvania Ave and Vizaleea Dr
- Access Rd at Brunskill Rd
- Blains
- Asbury Rd and Bonson Rd
- Associates Dr and Chavanelle Rd
- South Grandview at Bryant St
- Wacker Dr at Center Grove
- W 3rd and College
- Asbury Rd and Bunker Hill Rd
- Cardinal Dr and Flamingo Dr
- Mercy Hospital
- University Ave and N Booth St
- Delhi Transfer
- Locust St and Rosedale Ave
- Jackson St and 13th St
- University Ave and Prysi St
- Grandview Ave and 3rd St
- Harrison St at Burger King
- Mystique Ice Arena
- W 3rd and Booth
- Loras College at Loras Pkwy
- Cardinal Dr and Oriele Dr
- 9th St and Locust St
- Asbury Rd and Chaney Rd
- Main St and 17th St
- Rhomberg Ave and Kniest St
- Rhomberg Ave and Whittier St
- Loras Blvd and Dell St
- Central Ave and 24th St
- Mount Saint Francis
- Asbury Rd and Mullin Rd
- Elm St and 14th St
- University Ave and Finley St
- 14th St and Iowa St
- Bluff St and 5th
- White St and 15th St
- Jackson St and 15th St
- Windsor Ave and 24th St
- Kaufmann Ave and Crissy Dr
- JFK Rd and Raven Oaks Dr
- Intermodal Transfer
- Hogrefe Ave and Getty Terrace
- Central Ave and Diagonal St
- Jackson St and 26th St
- 11th St and Iowa St
- Pennsylvania Ave at Hempstead High School
- University Ave and O'Hagen St
- Eagles on Elm St
- South Grandview and Southern Avenue
- Jackson St and 21st St
- Central Ave and 30th
- Pennsylvania Ave at Flora Park
- Locust St and 6th St
- Sunset Park and JFK Rd
- HyVee on S Locust St
- Locust St and 11th St
- Lowes
- JFK Rd and Marywood Dr
- Central Ave and 19th St
- Kaufmann Ave at St. Mary's Apts
- Wingate Dr
- Rhomberg Ave and Dock St
- Rhomberg Ave and Shiras St
- Clarke Dr and Clarke Crest Dr
- Rhomberg Ave and Schiller St
- JFK Rd at Arby's
- North Grandview at HWY 20
- JFK Rd at Hoover School
- Pennsylvania Ave and Ruann Dr
- Asbury Rd and Hillcrest Rd
- Asbury Rd and Green St
- Hill St and 5th St
- Chavenelle Rd at AY McDonald
- S Grandview and Plymouth Ct
- Windsor Ave and Euclid St
- JFK Rd and Asbury Rd
- Mystique Casino
- Jackson St and 16th St
- Rhomberg Ave and Fengler St
- Main St and 2nd St
- Roosevelt Extension at Kerper Blvd
- Windsor Ave and Merz St
- Central Ave and 17th St
- Chaney Rd and Conventry Park Circle
- Davis St and Windsor Ave
- Saunders St
- Rhomberg Ave and Whittier St
- Central Ave and 13th St
- White St and 17th St
- North Grandview Ave and Algona St
- Washington Middle School
- Lake Ridge Dr and Starlite Dr
- Grandview Ave and Delaware St
- Main St and 1st St
- S Main St. at Arby's
- Diagonal St and Central Ave
- Jackson St and 19th St
- Iowa St and 6th
- Associates Dr near BioLife
- Kilgore St
- Central Ave and Kaufmann Ave
- Broadway St
- Jackson St and 28th St
- Senior High School
- Kohl's
- White St at 5th St
- Kaufmann Ave at Sisters of the Presentation
- Pennsylvania Ave at Butterfield Rd
- Jackson & 12th NW Corner
- 22nd St and Elm St
- Pennsylvania Ave and Chaney
- Jackson St and 22nd St
- Sam's Club
- Jackson St and 24th St
- JFK Rd and Rosewood Dr
- Bluff & 11th St.
- HyVee on Dodge St,
- Clarke Dr and Woodworth St
- Asbury Rd and Wilbricht Ln
- Berkley Pl and Primrose St
- 9th & Main St
- Plaza 20
- Asbury Rd and Matthew John Dr
- Loras Blvd and Locust St
- Medical Associates West Campus
- Rhomberg Ave and Hawthorne St
- Kennedy Mall at West Entrance
- Pennsylvania Ave and Hamblin Ct
- University Ave and O'Hagen St
- Burden St and Strauss St
- Jackson St and 17th St
- Locust St and Angella St
- University Ave and Wood St
- Kaufmann Ave near Evergreen Dr
- Harbor Freight
- Jackson St and 15th St
- Loras Blvd and Prairie St
- Kerper Blvd and Kerper Ct
- Pennsylvania Ave and Mission School Dr
- Clarke University South Parking Lot
- Main St and 15th St
- Flamingo Dr and Peru Rd
- Asbury Rd and Mullin Rd
- Pennsylvania Ave and McPoland Ave
- White St. and 10th St.
- Kmart
- Central Ave at 27th St
- HyVee NW Arterial
- Loras Blvd and Locust St
- Main St and 15th St
- Oak Crest Dr and Berkley Pl
- Pennsylvania Ave and Embassy Dr
- Plaza Dr.
- Pennsylvania Ave and Sylvan Dr
- Rhomberg Ave and Marshall St
- Central Ave and 15th St
- Asbury Rd and Hillcrest Rd
- Kaufmann Ave near Evergreen Dr
- Holliday Dr near Fidelity Bank
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 41.7 | first check |
| 2026-07-30 | 41.7 | no change |
| 2026-07-31 | 41.7 | no change |
| 2026-08-01 | 41.7 | 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
13 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 2619 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning676 instances
676 of 676 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)
- Warning233 instances
233 of 233 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)
- Warning213 instances
213 of 676 trips lack rider-facing destination or direction text.
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 · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning19 instances
Some values have extra spaces at the start or end.
A stray space can break a match, so a stop or route may fail to link across files.
Fix: Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this. (Usually one export setting.)
Finding code: leading_or_trailing_whitespaces · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning6 instances
Same name and description for route (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_name_and_description_for_route' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: same_name_and_description_for_route · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Finding code: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Finding code: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. Service data expired 2619 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- Service data expired 2619 days ago, so FTA would find the link out of date.
- 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 676 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. Service data expired 2619 days ago. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 2619 days ago.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.
How this agency maps to the standards
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 72 / 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 0 / 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 33 / 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/the-jule/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.