Feed status · checked 2026-08-01
VINE Transit
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
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 36 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
346 of 361 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 +24 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
Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras.
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.
⏱ A quick look at the flagged files.
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
- 346 of 361 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
- 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
- Feed evidence
- Some files contain columns that are not part of the GTFS spec.
- Next action
- Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras.
- 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.
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.
Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. · 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 91 days.
- Published accessibility data
- Accessibility information is stated for 4.2% 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
- 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 138 instances (0 error, 86 warning, 52 informational).
Service data covers the next 91 days.
4% of stops state wheelchair accessibility (4% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
4% of stops state accessibility (4% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
8 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (10, F, G, 11X, 21, 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.
295 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Main St at Central Ave", "Old Sonoma Rd at S Seymour St", "2nd St at California Blvd", 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.
Fares are applied to trips.
This agency publishes realtime, but the feed needs an access key we don't have 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 361 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.
- 10 (teal)
- 11 (purple)
- 11X (red)
- 21 (gray)
- 29 (pink)
- A (brown)
- B (black)
- C (pink)
- D (yellow)
- F (orange)
- G (teal)
- E (red)
| Route | Type | Line color |
|---|---|---|
| 10 Up Valley Connector | Bus | teal |
| 11 Napa-Vallejo Connector | Bus | purple |
| 11X Napa-Vallejo Express | Bus | red |
| 21 Napa-Solano Express | Bus | gray |
| 29 Napa-BART Express | Bus | pink |
| A Browns Valley | Bus | brown |
| B Westwood | South Napa | Bus | black |
| C Jefferson | Central Napa | Bus | pink |
| D Shetler | Shurtleff | Bus | yellow |
| F Southwest Napa | Bus | orange |
| G Coombs | South Napa | Bus | teal |
| E Vintage | Bus | red |
List every stop
- Vintage High School
- Main St at Central Ave
- Old Sonoma Rd at S Seymour St
- 2nd St at California Blvd
- Old Sonoma Rd at Underhill Dr NE
- Coombs St and S Franklin St (NB)
- Pine St at Adams St
- Browns Valley Rd at Robinson Ln
- Browns Valley Rd at Hudson Ln
- Lincoln Ave at Soscol Ave
- Clinic Ole North Campus (NB)
- Jefferson St at El Capitan Way South
- Jefferson St at Sierra Ave South
- Jefferson St at Maximillian Ct
- Jefferson St at Salvador Ave
- Salvador Ave at Dale Dr
- Byway St E at Monarch Dr
- Byway St E at Reed Cir
- Byway St E at El Centro Ave
- Cask Way at Wise Dr
- Trower Ave at Lassen St
- Trower Ave at Glacier Dr
- Jefferson St at Sierra Ave (NE)
- Jefferson St at El Capitan Way North
- Lincoln Ave at York St
- Lincoln Ave at Pacific St
- Solano Ave at Lone Oak Ave
- Solano Ave at Waverly St
- Solano Ave at Park Ave
- Pueblo Ave at Solano Ave
- Pueblo Ave at Pueblo Pl
- Linda Vista Ave at Redwood Rd
- Linda Vista Ave at Trojan Rd
- Oxford St at Berks St
- Oxford St at Wales St
- Oxford St at Carol Dr
- Lincoln Ave at Jordan Ln
- Lincoln Ave Vine Trail (SE)
- Villa Ln at Trancas St
- Beard Rd at La Homa Dr
- Main St at Pueblo Ave
- Lincoln Ave Vine Trail (NW)
- East Ave at Clark St
- East Ave at 1st St
- East Ave at Montecito Blvd
- East Ave at Silverado Tr
- Kansas Ave at Kansas Ct
- Terrace Dr at Kansas Ave
- Terrace Dr at Shetler Ave
- Shurtleff Ave at Ullman Ct
- Terrace Dr at Coombsville Rd
- 3rd St at Juarez St (SE)
- 3rd St at Bailey St
- Coombs St at 4th St
- Coombs St at 5th St
- Coombs St at Elm St
- Foster Rd at Indiana St
- Foster Rd at Idaho St
- Jefferson St at Madrona St
- Pine St at Jefferson St
- 2nd St at Patchett St
- 1st St at Chelsea Avenue
- Browns Valley Rd at Thompson Ave
- Browns Valley Rd at Austin Way
- Browns Valley Rd at Thornhill Dr
- 1st St at Freeway Dr
- Yountville Veterans Home
- Terrace Dr at Liberty Dr
- Justin Siena High School
- Jefferson St at Trower Ave
- Foster Rd at Imola Ave
- Jefferson St at Laurel St
- Byway St E at Salvador Ave
- Jefferson St at Trancas St (NE)
- Claremont Way at Jefferson St (NE)
- East Ave at Highland Dr (SE)
- Main St at Central Ave
- Old Sonoma Rd at Cherryview Ct
- Austin Way at Browns Valley Rd
- 1st St at Monroe St
- Browns Valley Rd at Rowena Ln
- Browns Valley Rd at Linda Vista Ave
- Browns Valley Rd at Dezerai Ct
- Browns Valley Rd at Westview Dr
- Randolph St at 3rd St
- Hwy 29 at Lodi Ln
- East Ave at Highland Dr (NE)
- Jefferson St at Trancas St (SW)
- Jefferson St at Joshua Ct
- Trower Ave at Lloyd Dr
- 3rd St at Juarez St (NE)
- East Ave at Evans Ave
- Clark St at Silverado Trail Westbound
- Browns Valley Rd at Partrick Rd
- Shurtleff Ave at Cayetano Dr
- Danrose Drive and Kimberly Drive
- Danrose Drive and American Canyon Road (Safeway)
- 244 American Canyon Road
- 300 American Canyon Road
- Newell/American Canyon High School
- Silver Oak Trail and Shenandoah Drive
- Donaldson/Summerwood Fire Department
- Hwy 29 and Antonia Avenue
- Donaldson Way and Rio Del Mar
- Elliot Drive and Kimberly Drive
- Danrose Drive and Kimberly Drive
- Broadway and Ventana Drive
- Broadway and American Canyon Road
- Montessori School
- Napa Valley College (St. Helens)
- Starr Avenue and Hunt Avenue
- Robert Louis Stevenson Middle School
- Stockton Street and Adams Street
- St Helena Primary School
- St Helena High School
- Napa Valley College (St. Helens)
- Starr Avenue and Hunt Avenue
- Stockton Street and Adams Street
- St Helena High School
- Trancas St and Jefferson St
- Trancas St at Soscol Ave
- California Blvd at Lincoln Ave South
- California Ave at E St South
- California Ave at E St North
- California at Lincoln North
- Jefferson St at Locust St North
- Foothill Blvd at Sunrise Dr
- Laurel St at Jade Ct
- Clinic Ole North Campus (SB)
- Coombs St at Division St South
- Coombs St at Oak St South
- Coombs St and Elm St South
- Coombs St at Franklin St South
- Napa Valley Corporate Dr at Napa Valley Corporate Way North
- Napa Valley Corporate Dr at Napa Valley Corporate Way South
- Danrose Dr at Folland Dr
- Broadway Dr at Vine Terrace Way
- Danrose Drive and Northampton Drive
- Danrose Dr and Folland Dr SB
- Lincoln Ave at Jefferson Av (Napa High)
- Napa County Soscol Campus (SB)
- Lincoln Ave at Marin St
- Riversounds
- Lincoln Ave at Stevenson St
- Solano Ave at Trower N (NB)
- Imola Ave At Minahen St (WB)
- Imola Park and Ride (NB)
- Imola Park and Ride (SB)
- Gasser DR at Hartle Crt SW
- Middleton Way
- Coombs St and Laurel St South
- Jefferson St at Cinnamond St North
- Clark St at Silverado Trail Eastbound
- Foothill Blvd At Greco Dr North
- Foothill Blvd at Pine St North
- Foothill Blvd at Hilltop Blvd North
- Napa Valley College (NB)
- Laurel St at Griggs Ln (NE)
- Laurel St at Bryan Ave
- Laurel Street at Kilburn (SE)
- Kansas Ave at Soscol Ave NW
- Imola Ave at Gasser Dr EB
- Kansas Ave at Coronado Ave
- Lincoln Avenue at Main Street
- Redwood Park & Ride, A1
- Redwood Park & Ride, A2
- Redwood Park & Ride, B1
- Redwood Park & Ride, B2
- Redwood Park & Ride, B3
- Soscol Gateway Transit Ctr
- Napa High Northbound
- Jefferson St at Pueblo Ave
- Jefferson St at Sheridan Way (NE)
- Claremont Way at Kaiser (NE)
- Trancas St at Baxter Ave
- Redwood Park & Ride
- Trancas St at California Blvd
- Claremont Way at Kaiser
- Jefferson St at Sheridan Way (SW)
- Jefferson St at Pueblo Ave (NW)
- Napa High School
- Soscol Ave at Lincoln Ave South
- Soscol Ave at Tanen St
- Soscol Ave At Clinton St
- Soscol Ave at Sousa Lane
- Soscol Ave at Silverado Tr South
- Soscol Ave at Kansas Ave South
- Imola Ave at Gasser Dr
- Imola Ave and Coombs St
- Imola Ave at Foster Rd West
- Foster Rd at Indiana St North
- Old Sonoma Rd at Foster Rd
- Old Sonoma Rd at Harvest Magnet Middle School
- Old Sonoma Rd at S Seymour St
- Old Sonoma Rd at Hartson St
- Jefferson St at Locust St South
- Imola Ave at Jefferson St
- Gasser Dr at Hartle Ct
- Kansas Ave at Soscol Ave
- Soscol Ave at Silverado Tr North
- Soscol Ave at Sousa Ln
- Kansas Ave at Wilkins Ave
- Shetler Ave at Shurtleff Ave
- Laredo St at Maria Dr
- Seville Dr at Perkins St
- Camille Creek Community School
- Imola Ave at Navarre St
- Imola Ave at Parrish Rd
- Soscol Ave at Kansas Ave North
- 3rd St at Brown St (WB)
- 3rd St at Jefferson St
- Premium Outlets
- Kilburn Ave at Cornwall Ave
- Kilburn Ave at Bryan Ave
- Kilburn Ave at Chelsea Ave
- Laurel St at Kilburn Ave
- Laurel St At Laurel Ln
- Laurel St at Griggs Ln
- Foothill Blvd at Hilltop Dr
- Foothill Blvd at Pine St
- Foothill Blvd at Greco Dr
- Jefferson St at Elm St
- Pine St at Seminary St
- Franklin St at Division St
- 3rd St at Brown St
- Vallejo Ferry Terminal
- American Canyon Post Office (NB)
- Napa Valley College
- American Canyon Post Office (SB)
- Suisun City Train Depot
- Fairfield Transportation Ctr
- El Cerrito Del Norte Station (Stop C6)
- Soscol Ave at Imperial Way
- Soscol Ave at Lincoln Ave North
- Soscol Ave at Stonehouse Dr
- Soscol Ave at Costa Dr
- Soscol Ave At Pueblo Ave North
- Soscol Ave At La Homa Dr North
- Soscol Ave at Pear Tree Ln (NE)
- Trancas St at Valle Verde Dr
- Trancas St at Villa Ln (NW)
- Queen of the Valley Medical Center (WB)
- Trancas St at Jefferson St North
- Solano Ave at Devonshire Dr North
- Solano Ave at Wine Country Ave North
- Solano Ave at Mobile Dr
- Solano Ave at Newell Cir North
- Solano Ave at Orchard Ave North
- Yountville Park & Ride
- Washington St At Mission St North
- and 111 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 | 87.8 | first check |
| 2026-07-30 | 87.8 | no change |
| 2026-07-31 | 87.8 | no change |
| 2026-08-01 | 87.8 | 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
7 findings, ordered by severity.
Show every finding
- Warning346 instances
346 of 361 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)
- Warning86 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
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)
- 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)
- Info9 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)
- Info6 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)
- 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 91 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 1480; your National Transit Database ID is 90088. 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 1480 to NTD ID 90088, and keep the feed value stable. Do not change it solely to make the two values equal.
- shapes.txt covers your trips Ready
- All 510 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 4% 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 91 days.
- Accessible Not yet
- States wheelchair access on 4% 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 86 of 361 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 91 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 89 / 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 76 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Access needed to measure
- 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/vine-transit/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.