Feed status · checked 2026-10-20
Victoria Transit (Golden Crescent Regional Planning Commission)
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
First scorecard for this agency
Cataloged in Texas.
Source feed: https://gtfs.gcrpc.org/gtfs/GCRPC-Fixed.zip
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.4, validator 8.0.1.
Checked for changes 34 minutes ago; last changed 34 minutes ago.
Measured 3 of 4 score categories from the feed URL on file (publisher not verified).
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 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.
About this feed
Victoria Transit (Golden Crescent Regional Planning Commission)’s published feed lists 6 bus routes, 96 scheduled trips and 164 stops. Its service dates run from 2026-09-01 through 2027-08-31.
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
164 of 164 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.
Fixing this covers all 164 stops in the feed.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.Likely your export tool
Some route lines list the same point twice in a row. Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
⏱ Usually one export setting.worth about +6 points in its category
Set trip_headsign to the trip's last stop or its overall destination.Likely your export tool
Some trip headsigns name a stop along the way, not the final destination. The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
⏱ Usually a bulk edit in your scheduling software.
Riders and need behind these fixes
- More than one feed record claims this National Transit Database reporter, so its rider-trips are held back rather than counted against any single feed.
- Texas as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-10-19.
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
- Finding
- Fix 02 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
- Finding
- Fix 03 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.
Fix 01 · Read the fix guide for scorecard_wheelchair_boarding_unknown
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.
Fix 02 · Read the fix guide for equal_shape_distance_same_coordinates
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.
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 315 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- Realtime information
- 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.
Score by category
The MobilityData validator flagged 2 kinds of issue across 14 instances (0 error, 6 warning, 8 informational).
Service data covers the next 315 days.
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.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 4, 5, 6).
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.
155 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("E Rio Grande @ N Azalea", "E Rio Grande @ N Laurent (North Side)", "E Rio Grande @ N Jecker", 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.
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 164 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.
- 1 (pink)
- 2 (purple)
- 3 (blue)
- 4 (orange)
- 5 (green)
- 6 (red)
| Route | Type | Line color |
|---|---|---|
| 1 Pink | Bus | pink |
| 2 Purple | Bus | purple |
| 3 Blue | Bus | blue |
| 4 Gold | Bus | orange |
| 5 Green | Bus | green |
| 6 Red | Bus | red |
List every stop
- North Walmart @ N Navarro
- N Navarro @ Loop 463
- 1800 Blk Houston
- N Ben Wilson @ E Rio Grande (Northbound)
- N Navarro @ E Nueces (Southbound)
- N Navarro @ E Nueces (Northbound)
- E Rio Grande @ N Azalea
- E Rio Grande @ N Laurent (North Side)
- E Rio Grande @ Base
- E Rio Grande @ N Jecker
- E Rio Grande @ N Laurent (South Side)
- N Main @ W Rio Grande (Southbound)
- John Stockbauer @ Lighthouse for the Blind
- E Rio Grande @ N Williams (North Side)
- E Rio Grande @ N Williams (South Side)
- N Main @ W Rio Grande (Northbound)
- W Rio Grande @ N Moody
- N Ben Wilson @ Meadowlane (Northbound)
- N Moody @ W North
- N Ben Wilson @ Meadowlane (Southbound)
- N Laurent @ Ash
- Main @ North
- N Navarro @ Ash
- 5600 Blk John Stockbauer
- N Moody @ E Commercial (Northbound)
- N Moody @ E Commercial (Southbound)
- N Main @ E Goodwin
- E Goodwin @ N Main
- N Liberty @ E Goodwin (Southbound)
- N Liberty @ E Goodwin (Northbound)
- N Ben Wilson @ Lone Tree (Southbound)
- N Laurent @ E North (Northbound)
- N Ben Wilson @ Lone Tree (Northbound)
- N Laurent @ E North (Southbound)
- N Navarro @ Kelly
- E North @ N Cleveland
- N Navarro @ E Goodwin
- S Moody @ E Santa Rosa (Southbound)
- E Goodwin @ N Navarro
- S Moody @ E Santa Rosa (Northbound)
- E North @ Avenue C (Southbound)
- E North @ Avenue C (Northbound)
- E Juan Linn @ S Liberty (Northbound)
- E Juan Linn @ S Liberty (Southbound)
- E Juan Linn @ S Navarro
- N Navarro @ Huvar
- N Ben Wilson @ Gayle (Southbound)
- E North @ Community Center (Southbound)
- E North @ Community Center (Northbound)
- N Ben Wilson @ Gayle (Northbound)
- S Moody @ E River (Southbound)
- S Moody @ E River (Northbound)
- N Ben Wilson @ E North
- W Water @ S Bridge (Northbound)
- W Water @ S Bridge (Southbound)
- E Water @ S William (Northbound)
- John Stockbauer @ Wind Crest
- E Water @ S William (Southbound)
- NE Water @ Hopkins (Northbound)
- NE Water @ Hopkins (Southbound)
- E Water @ S Cameron (Southbound)
- E Water @ S Cameron (Northbound)
- S Laurent @ Hopkins (Northbound)
- S Laurent @ Hopkins (Southbound)
- S Laurent @ Kern (Northbound)
- S Laurent @ Kern (Southbound)
- S Laurent @ Odem
- John Stockbauer @ Sharon Ann
- S Laurent @ Belinda (Southbound)
- S Laurent @ Belinda (Northbound)
- S Laurent @ Pleasant Green (Southbound)
- S Laurent @ Pleasant Green (Northbound)
- S Laurent @ Bottom
- Gulf Bend Center
- Allen Miller @ James Coleman
- Allen Miller @ Victoria Eye Center
- John Stockbauer @ Salem
- N Navarro @ Primrose
- N Navarro @ Guy Grant (Southbound)
- N Navarro @ Guy Grant (Northbound)
- DeTar North
- 4500 Blk John Stockbauer
- N Main @ Kerh (Southbound)
- N Main @ Kerh (Northbound)
- N Navarro @ Whispering Creek (Southbound)
- N Navarro @ Whispering Creek (Northbound)
- 4300 Blk John Stockbauer
- John Stockbauer @ Regency
- N Navarro @ E Larkspur
- N Main @ Conti (Northbound)
- N Main @ Conti (Southbound)
- N Navarro @ Northshire
- John Stockbauer @ Williamsburg
- N Navarro @ Jade
- E Mockingbird @ Northpark
- N Navarro @ Stanly
- E Mockingbird @ Vicksburg
- 2400 Blk E Mockingbird
- N Navarro @ Lasalle Crossing
- 2500 Blk E Mockingbird
- N Navarro @ Country Club (Southbound)
- N Navarro @ Country Club (Northbound)
- E Mockingbird @ Faith Family
- E Mockingbird @ Fannin
- Sam Houston @ Victoria Station
- N Navarro @ E Mockingbird (Northbound)
- N Main @ W Mockingbird (Southbound)
- N Main @ W Mockingbird (Northbound)
- N Navarro @ E Mockingbird (Southbound)
- Victoria Mall @ Cinemark
- N Navarro @ Fillmore
- Sam Houston @ E Polk (Northbound)
- Sam Houston @ E Polk (Southbound)
- N Navarro @ Cozzi
- Sam Houston @ N Ben Jordan
- Sam Houston @ Lenora
- Sam Houston @ E Crestwood
- N Navarro @ E Crestwood (Southbound)
- N Navarro @ E Crestwood (Northbound)
- N Main @ W Crestwood (Southbound)
- N Navarro @ Hathaway (Southbound)
- Sam Houston @ E Mistletoe
- N Main @ W Crestwood (Northbound)
- Sam Houston @ Erwin
- N Navarro @ E Rosebud
- Houston @ TDJC
- N Ben Wilson @ E Locust
- Houston @ John Stockbauer
- N Main @ Lantana (Southbound)
- N Navarro @ Imperial
- E Airline @ N Ben Jordan
- N Navarro @ Hathaway (Northbound)
- N Main @ Lantana (Northbound)
- N Navarro @ Locust
- N Laurent @ E Airline
- N Main @ E Hiller (Southbound)
- N Main @ E Hiller (Northbound)
- N Laurent @ Loma Vista
- South Walmart @ Houston
- N Navarro @ E Warren
- Houston @ Delmar
- Houston @ Gossett
- 8200 Blk NE Zac Lentz
- E Red River @ AHEC
- E Red River @ Citizens Medical Center
- E Red River @ N Ben Jordan
- N Navarro @ E Virginia
- Lone Tree @ Wayne Watkins
- Houston @ Duncan
- N Main @ Red River (Northbound)
- N Navarro @ E Red River
- N Laurent @ E Sabine
- N Main @ Red River (Southbound)
- NE Zac Lentz @ Citizens HealthPlex
- Houston @ N Ben Wilson (North Side)
- Houston @ N Ben Wilson (South Side)
- N Ben Jordan @ E Brazos
- N Navarro @ E Brazos (Northbound)
- John Stockbauer @ Lone Tree
- N Navarro @ E Brazos (Southbound)
- 2300 Blk N Ben Wilson
- N Main @ E Colorado (Southbound)
- N Main @ E Colorado (Northbound)
- N Ben Wilson @ E Rio Grande (Southbound)
Over time
This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.
Everything we checked
3 findings, ordered by severity.
Show every finding
- Warning164 instances
164 of 164 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)
- Warning6 instances
Some route lines list the same point twice in a row.
Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)
Finding code: equal_shape_distance_same_coordinates · Read the fix guide for equal_shape_distance_same_coordinates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info8 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Finding code: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
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 315 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 gcrpc-tx-us; your National Transit Database ID is 60095. 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 gcrpc-tx-us to NTD ID 60095, and keep the feed value stable. Do not change it solely to make the two values equal.
- shapes.txt covers your trips Ready
- All 96 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
One requirement remains for this feed to earn the conformance mark. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 315 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 315 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 93 / 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 75 / 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.
Part of the Texas portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in Texas
Other scorecards in Texas, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
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/golden-crescent-victoria-transit/2026-10-20.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-10-20. 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.