Feed status · checked 2026-08-01
Williamsburg Area Transit Authority (WATA)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Virginia.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.
Checked for changes 9 hours ago; last changed 41 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
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 1128 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
Review the rule documentation for 'start_and_end_range_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Start and end range out of order (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +18 points in its category
Add the required column named in the finding to the flagged file.Likely your export tool
A file is missing a column that GTFS requires. Apps may reject the whole file, so riders could lose the affected routes or stops.
⏱ Often an export setting; ask your vendor if it recurs.worth about +12 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 1128 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
- Start and end range out of order (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'start_and_end_range_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
- A file is missing a column that GTFS requires.
- Next action
- Add the required column named in the finding to the flagged file.
- 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.
Review the rule documentation for 'start_and_end_range_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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.
Add the required column named in the finding to the flagged file. · 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 1128 days ago.
- Published accessibility data
- Accessibility information is stated for 0.3% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send 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 12 kinds of issue across 146 instances (17 error, 75 warning, 54 informational).
Service data ended 1128 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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 2, 12, 12A, 3, 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.
262 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Battery Blvd at Riverside Hospital", "Bypass Rd. at Days Inn", "Jamestown Rd at CVS", 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 326 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 (gray)
- 11 (blue)
- 9 (brown)
- 8 (gray)
- 7 (gray)
- 6 (brown)
- 4 (purple)
- 3 (orange)
- 2 (teal)
- 12 (green)
- 12A (green)
- 5 (red)
| Route | Type | Line color |
|---|---|---|
| 1 Lee Hall | Bus | gray |
| 11 Lackey | Bus | blue |
| 9 Toano | Bus | brown |
| 8 W & M | Bus | gray |
| 7 Mooretown | Bus | gray |
| 6 Jamestown | Bus | brown |
| 4 Longhill | Bus | purple |
| 3 Merrimac | Bus | orange |
| 2 Richmond | Bus | teal |
| 12 12 - Ironbound | Bus | green |
| 12A 12A - Ironbound | Bus | green |
| 5 5 - Monticello | Bus | red |
List every stop
- Pocahontas Trl at Colonial Manor
- Battery Blvd at Riverside Hospital
- Bypass Rd. at Days Inn
- Jamestown Rd at CVS
- Discovery Park Blvd at Discovery Park
- Richmond Rd at Premium Outlets
- High St at Parking Deck
- Barhamsville Rd at Old Stage Rd
- Richmond Rd at Peninsula Mulch
- Richmond Rd at Old Point National
- Compton Dr at Kaplan Arena
- Mooretown Rd at Bulifants Blvd
- Mooretown Rd at Colony Dr
- Queens Path at Riverside
- Pilot Way at Taco Bell
- Jamestown Rd at Cary St
- Monarch Crossing at Promenade
- Ironbound Rd at Harris Teeter
- Monticello Ave at Publix
- Treyburn Dr at Brookdale
- Richmond Rd at Shell
- Centerville Rd at Forest Glen 1
- Longhill Rd at Jolly Pond Vet
- DePue Dr at Plumeri Park
- Merrimac Trl at Fastenal
- Merrimac Trl at Gala Upholstery
- Merrimac Trl at 2nd St
- Capitol Landing Rd at Merrimac Trl
- Capitol Landing Rd at Red Roof Inn
- Capitol Landing Rd at Merrimac Trl
- Merrimac Trl at Trail Plaza
- Penniman Rd at Custis Dr
- Richmond Rd at Wellesley
- Richmond Rd at Fireside
- Richmond Rd at Kyoto
- Richmond Rd at VA Peanuts
- Richmond Rd at Rt 60 Barbeque
- Richmond Rd at Taco Bell
- Richmond Rd at Stratford Rd
- Richmond Rd at Herndon Jenkins
- Scotland St at Tribe Square
- Richmond Rd at Richmond Hall
- Ironbound Rd at Salvation Army
- Courthouse St at Buffalo Wild Wings
- Richmond Rd at Peter Chang
- Pocahontas Trl at Creative Kids
- Pocahontas Trl at BG Construction
- Pocahontas Trl at Merrill Lynch
- Pocahontas Trl at BG Bavaria Lot
- Pocahontas Trl at Creative Kids
- Queens Path at Riverside
- Old Williamsburg Rd at Woods of Yorktown
- Old Williamsburg Rd at Rising Sun OB
- Old Williamsburg Rd at Lackey Clinic
- Mounts Bay Rd at JCC Gov Center
- Battery Blvd at Harris Teeter
- Merrimac Trl at VP Regional Jail
- Longfellow Rd at YNWS Gate 3
- Yorktown Rd at Hamilton Redoubt
- Old Williamsburg Rd at Dogwood Rd
- Old Williamsburg Rd at Rising Sun IB
- Old Williamsburg Rd at Woods of Yorktown
- Barham Blvd at Yorktown Square
- Barham Blvd at Rivermeade
- Eagle Way at Jamestown High
- Centerville Rd at Harris Teeter
- Richmond Rd at Olde Towne Rd
- Jamestown Rd at Lemon Hall
- Pocahontas Trl at Fort Magruder
- Pocahontas Trl at Green Mtn Pkwy
- Centerville Rd at Opportunity Way
- John Tyler Hwy at Mcdonalds
- John Tyler Hwy at Westray Downs
- John Tyler Hwy at St Georges
- Colonial Pkwy at The Settlement
- Jamestown Rd at London Company
- Jamestown Rd at Consulate Health
- Jamestown Rd at Ironbound Rd
- Jamestown Rd at Colony Square
- Centerville Rd at Jolly Pond Rd
- Centerville Rd at Jones Dr
- Centerville Rd at Longhill Station
- Centerville Rd at JSG Corporation
- New Town Ave at Legacy Hall
- Jamestown Rd at Campus Center
- Centerville Rd at Adams Hunt
- Centerville Rd at Fox Ridge
- Longhill Rd at New Zion Church
- Longhill Rd at New Zion Church
- Centerville Rd at Adams Hunt
- Toano Dr at Burnt Ordinary 2
- Richmond Rd at Mcleans Grocery
- Richmond Rd at Hankins Ind Park
- Richmond Rd at CVS
- Richmond Rd at Toano Middle
- Merrimac Trl at Orange Dr
- Merrimac Trl at Colonial Pines
- Merrimac Trl at Colonial Health
- Alexander Lee Pkwy at Peoples Place
- Ukrop Way at WM Parking Deck
- Ukrop Way at Commons Dining
- Pocahontas Trl at WATA
- Pocahontas Trl at Country Inn
- Penniman Rd at James York Plaza
- Penniman Rd at Magruder Elm
- Penniman Rd at Dodge Dr
- Penniman Rd at Vineyard Ln
- Merrimac Trl at Armstrong Dr
- York St at Quarterpath Place
- York St at Patrick Henry
- E Rochambeau Dr at Great Wolf Lodge
- E Rochambeau Dr at Wal-Mart
- Mooretown Rd at Marketcenter
- Mooretown Rd at Old Taylor Rd
- Mooretown Rd at Ewell Rd 2
- Mooretown Rd at Ewell Rd 1
- Mooretown Rd at Anvil Campground
- Mooretown Rd at Governors Green
- Mooretown Rd at Embassy Suites
- Mooretown Rd at Kingsgate Shops
- Bypass Rd at Comfort Inn
- Bypass Rd at Homewood Suites
- N Henry St at Highland Park
- Bypass Rd at Country Inn
- Bypass Rd at Cracker Barrel
- Mooretown Rd at Embassy Suites
- Mooretown Rd at Governers Green
- Mooretown Rd at Anvil Campground
- Mooretown Rd at Ewell 4
- Mooretown Rd at Ewell 3
- Mooretown Rd at Old Taylor Rd
- Sentara Cir at Sentara Main
- Sentara Cir at Sentara Geddy
- Mooretown Road at Sentara Cir
- Lightfoot Rd at Antique Mall
- Monticello Ave at Target
- Monticello Ave at Trader Joes
- Ironbound Rd at Plumeri Park
- Treyburn Dr at Sterling Manor
- Treyburn Dr at Diagnostic Center
- Jamestown Rd at Village Green
- Williamsburg Crossing at Food Lion
- Strawberry Plains Rd at Midlands
- Strawberry Plains Rd at Berkeley Middle
- Monticello Ave at Post Office
- Monticello Ave at Courthouse Commons
- Monticello Ave at Marketplace Shops
- Monticello Ave at Veterans Park
- Steeplechase Dr at Steeplechase
- Richmond Rd at Mcdonalds
- Richmond Rd at Chesapeake Bank
- Richmond Rd at The Pottery
- Richmond Rd at Colonial Towne
- Richmond Rd at 7-Eleven
- Richmond Rd at Norge Shops
- Richmond Rd at Post Office
- Richmond Rd at John Deer
- Richmond Rd at Hunters Creek
- Chickahominy Rd at Toano Trace
- Chickahominy Rd at Power Lines
- Chickahominy Rd at Friendship Dr
- Chickahominy Rd at Little Creek Dam
- Chickahominy Rd at Browns Dr
- Chickahominy Rd at Friendship Dr
- Chickahominy Rd at Power Lines
- Chickahominy Rd at 3339 Block
- Chickahominy Rd at Toano Trace
- Richmond Rd at Business Park
- Barhamsville Rd at BP Food Mart
- Barhamsville Rd at LaGrange Pkwy
- Richmond Rd at Luck Stone
- Croaker Rd at Station at Norge
- Croaker Rd at JCC Library
- Richmond Rd at C&F Bank
- Richmond Rd at Norge Hall
- Richmond Rd at 7-Eleven
- Richmond Rd at Go-Karts Plus
- Richmond Rd at The Pottery
- Richmond Rd at 7-Eleven
- Richmond Rd at New York Deli
- Richmond Rd at Pavillion Shops
- Centerville Rd at Handy Ice
- Centerville Rd at Jones Dr
- Centerville Rd at Forest Glen 2
- Longhill Rd at Dominion Village
- Longhill Rd at Warhill Sports
- Longhill Rd at Lafayette High
- Longhill Rd at Lafayette Blvd
- Longhill Rd at Williamsburg Plantation Dr
- Longhill Rd at Rolling Meadows
- Ashbury Rd at JCC Rec Center
- Ironbound Rd at Parker View
- Courthouse St at WJCC Courthouse
- New Town Ave at Velocity
- Ironbound Rd at Carinos Seafood
- Ironbound Rd at Tewning Rd
- Depue Dr at Plumeri Park
- Depue Dr at Eastern State
- Longhill Rd at Fords Colony
- Longhill Rd at Lafayette High
- Longhill Rd at Longhill Gate
- Longhill Rd at Longhill Grove
- Centerville Rd at Handy Ice
- Centerville Rd at Mobile Estates
- Capitol Landing Rd at Bypass Rd
- Capitol Landing Rd at Sals Ristorante
- Merrimac Trl at Merrimac Crossing
- Merrimac Trl at Colonial Towne
- Merrimac Trl at Priorslee Ln
- Penniman Rd at Queens Creek Rd
- Water Country Pkwy at Wyndham Garden
- Whittakers Trace at Dicks Sports
- Whittakers Trace at Target
- Merrimac Trl at Douglas Dr
- Tam-O-Shanter Blvd at Merrimac Trl
- Merrimac Trl at CVS
- Merrimac Trl at Parkway Apts
- Merrimac Trl at Colonial Towne
- Capitol Landing Rd at Int Village
- Visitor Center Dr at CW Visitor Center
- N Henry St at Highland Park
- Richmond Rd at WAWA
- S Henry St at WM Grad Plex
- Jamestown Rd at Indian Springs
- Monticello Ave at Ritas Ice
- Warwick Blvd at Lee Hall Church
- Pocahontas Trl at Blow Flats Rd
- Pocahontas Trl at Happy Shopper
- Pocahontas Trl at James River Elm
- Pocahontas Trl at Carters Grove
- Pocahontas Trl at BG England Lot
- Pocahontas Trl at Kingsmill
- Pocahontas Trl at BB&T Bank
- Pocahontas Trl at Fort Magruder
- York St at The Flats
- Pocahontas Trl at Wendys
- Pocahontas Trl at BG Brewery
- Pocahontas Trl at Howard Dr
- Pocahontas Trl at Mount Gilead
- Pocahontas Trl at Dollar General
- Pocahontas Trl at Heritage Park
- Pocahontas Trl at Brookside
- Pocahontas Trl at Happy Shopper
- Pocahontas Trl at Skiffes Creek
- Pocahontas Trl at WalMart Dist
- Warwick Blvd at Falls Reach Pkwy
- Elmhurst St at Lee Hall
- Richmond Rd at Forest Heights
- Olde Towne Rd at Social Services
- Richmond Rd at Airport Rd
- and 76 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 | 35.1 | first check |
| 2026-07-30 | 35.1 | no change |
| 2026-07-31 | 35.1 | no change |
| 2026-08-01 | 35.1 | 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
16 findings, ordered by severity.
Show every finding
- Error15 instances
Start and end range out of order (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'start_and_end_range_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: start_and_end_range_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error2 instances
A file is missing a column that GTFS requires.
Apps may reject the whole file, so riders could lose the affected routes or stops.
Fix: Add the required column named in the finding to the flagged file. (Often an export setting; ask your vendor if it recurs.)
Finding code: missing_required_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Service data ended 1128 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)
- Warning1005 instances
1005 of 1005 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)
- Warning325 instances
325 of 326 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)
- Warning34 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)
- Warning27 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning9 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)
- Warning3 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)
- Warning1 instance
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date7_days · 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
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)
- Info37 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)
- Info7 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)
- Info1 instance
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · 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 Not ready
Resolve this before you certify on the D-10. 2 validator errors to resolve. Service data expired 1128 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 2 validator errors to resolve.
- Current Not ready
- Service data expired 1128 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 1005 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. 2 validator errors to resolve. Service data expired 1128 days ago. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 2 validator errors to resolve.
- Current Not yet
- Service data expired 1128 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 34 of 326 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.
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. The feed also carries 17 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
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 37 / 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 60 / 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/williamsburg-area-transit-authority-wata/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.