Feed status · checked 2026-07-18
Green Line 702
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in West Berkshire, United Kingdom.
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.2, validator 8.0.1.
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
181 of 181 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
418 of 418 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
Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool
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.
⏱ Two fields, set once in export settings.worth about +15 points in its category
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. 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.
Add feed_info.txt with feed_start_date and feed_end_date to your export. · 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 is in 43 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- 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.
Score by category
The MobilityData validator flagged 1 kind of issue across 1 instance (0 error, 1 warning, 0 informational).
Service data covers the next 43 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 not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
10 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("St Bernards Convent", "Langley, London Road/High Street", "St Leonards Hill", 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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 703 (white)
- 701 (white)
- 702 (white)
| Route | Type | Line color |
|---|---|---|
| 703 | Bus | white |
| 701 | Bus | white |
| 702 | Bus | white |
This feed has 181 stops.
List every stop
- Boys School
- Legoland, Staff Entrance
- Heatherwood Roundabout
- Gainsborough Drive
- Legoland, Main Entrance
- Heatherwood Roundabout - west
- Gainsborough Drive
- Heatherwood Hospital Entrance
- Heatherwood Hospital Entrance
- Boys School
- Arthur Road
- Arthur Road
- Windsor, Castle Hill
- Windsor, Parish Church
- Windsor, Parish Church
- Windsor, Theatre Royal
- King Edward VII Hospital
- King Edward VII Hospital
- Imperial Court
- Windsor, Imperial Court
- Prince Albert PH
- Prince Albert PH
- Woodland Avenue
- St Leonards Hill
- St Leonards Hill
- Trevelyan School
- Trevelyan School
- All Saints' Church
- All Saints' Church
- Grove Road
- Grove Road
- Ascot High Street
- Ascot High Street
- Heatherwood Hospital - east
- Heatherwood Hospital - east
- York House
- Knights Place
- Stag Meadow
- Stag Meadow
- Legoland Roundabout
- Legoland Roundabout
- High Standing Hill
- High Standing Hill
- Winkfield Road
- Winkfield Road
- St Bernards Convent
- St Bernards Convent
- Kaywood Close
- Kaywood Close
- Upton Court Road Junction
- Upton Court Road Junction
- Drake Avenue
- Drake Avenue
- Cedar Way
- Cedar Way
- Ditton Park Road
- Ditton Park Road
- Langley, London Road/High Street
- Langley, London Road/High Street
- Sutton Lane
- Sutton Lane
- Crown Meadow
- Crown Meadow
- Red Lion
- Red Lion
- Colnbrook, Ye Olde George
- Colnbrook, Ye Olde George
- Star & Garter
- Coleridge Crescent West
- Coleridge Crescent West
- Poyle Road Junction
- Poyle Road Junction
- Galleymead Road
- Galleymead Road
- Dover Road
- Westgate Retail Park
- Leigh Road
- Twinches Lane North
- Salt Hill Three Tuns
- Slough Grammar School
- Uxbridge Road Sainsbury's
- Sorting Office
- Sorting Office
- Albert Street
- Albert Street
- Windsor Road, McDonalds
- Windsor Road, McDonalds
- Slough, Wellington Street
- Landmark Place
- Library
- Slough, Queensmere Car Park
- St Andrews Way
- Everitts Corner
- Burnham Lane
- Windmill Road
- Salt Hill Park
- Landmark Place
- Uxbridge Road Sainsbury's
- Skimped Hill Lane - Health Centre
- Bracknell Bus Station
- The Ring - Parish Church
- Bay Road
- Bay Road
- Bullbrook Ethyl Labs
- Bullbrook Ethyl Labs
- Drovers Way
- Drovers Way
- Allsmoor Lane
- Allsmoor Lane
- The Brackens
- The Brackens
- The Royal Foresters Hotel
- The Royal Foresters Hotel
- Fernbank Corner
- Fernbank Corner
- Fernbank Corner
- Goaters Road
- Goaters Road
- The Gold Cup PH
- The Gold Cup PH
- Ascot Heath
- Ascot Heath
- Royal Hunt Public House
- Royal Hunt Public House
- Beechwood Close
- Beechwood Close
- Plaistow Green
- Plaistow Green
- The Rough
- The Rough
- Brookside, Old Post Office
- Brookside, Old Post Office
- Primary School
- Cranbourne Corner
- Cranbourne Corner
- Primary School
- Chilston Manor
- Chilston Manor
- The Old Hatchet
- Fleur De Lis
- The Old Hatchet
- Fleur De Lis
- Crouch Lane
- Crouch Lane
- Winkfield, The Squirrel
- Winkfield, The Squirrel
- Cemetery Junction
- Cemetery Junction
- Cholmeley Road
- Cholmeley Road
- Kings Road
- Eldon Road
- Eldon Road
- Huntley and Palmers
- Huntley and Palmers
- Liverpool Road
- Liverpool Road
- Reading College
- Reading College
- Reading Station
- Reading Station
- Kensington, High Street/Wrights Lane
- Hyde Park Corner
- Hyde Park Corner
- Knightsbridge Barracks
- Kensington Station
- Victoria
- Buckingham Palace Road Bressenden Place
- Victoria, Buck'ham Palace Rd
- Hammersmith, Hammersmith Bridge Road
- Hammersmith, Hammersmith Bridge Road
- Kensington (Olympia) Station
- Latymer Court
- Hammersmith Road
- Moor Bridge
- Moor Bridge
- Phillimore Gardens
- Royal Albert Hall
- Royal Albert Hall
- Knightsbridge Barracks
- Heathrow Airport, Terminal 5
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
6 findings, ordered by severity.
Show every finding
- Warning418 instances
418 of 418 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.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning181 instances
181 of 181 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.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference 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.)
Validator rule: missing_recommended_file · 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.)
Validator rule: 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.)
Validator rule: 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.)
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
This feed is close to the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 43 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 43 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. Read the full standards crosswalk.
- Correctness 96 / 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.
- Freshness 57 / 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.
- Rider experience 38 / 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/green-line-702/2026-07-18.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-07-18. 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.