Feed status · checked 2026-07-18
Xplore Dundee
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Dundee City, 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
Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Block trips with overlapping stop times (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +18 points in its category
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
740 of 740 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
2440 of 2440 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
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.
Review the rule documentation for 'block_trips_with_overlapping_stop_times' 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.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 360 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 4 kinds of issue across 23 instances (6 error, 3 warning, 14 informational).
Service data covers the next 360 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
23 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Broughty Ferry Fort Street/Queen Street", "Craigowl View, St Martins Avenue", "Downfield St Marys Road", 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.
- 1 (white)
- 10 (white)
- 14 (white)
- 17 (white)
- 18 (white)
- 2 (white)
- 22 (white)
- 22c (white)
- 23 (white)
- 28 (white)
- 32 (white)
- 33 (white)
- 5 (white)
- 5a (white)
- 6 (white)
- AT1 (white)
- FLY (white)
| Route | Type | Line color |
|---|---|---|
| 1 | Bus | white |
| 10 | Bus | white |
| 14 | Bus | white |
| 17 | Bus | white |
| 18 | Bus | white |
| 2 | Bus | white |
| 22 | Bus | white |
| 22c | Bus | white |
| 23 | Bus | white |
| 28 | Bus | white |
| 32 | Bus | white |
| 33 | Bus | white |
| 5 | Bus | white |
| 5a | Bus | white |
| 6 | Bus | white |
| AT1 | Bus | white |
| FLY | Bus | white |
This feed has 740 stops.
List every stop
- Edinburgh Airport
- Edinburgh Airport
- Queen's Cross Church
- Queens Road
- Rubislaw Terrace
- Carden Place
- Carden Place
- Fernhill Drive
- Fernhill Drive
- Springhill Road
- Lang Stracht @ Lewis Road
- Lang Stracht @ Lewis Road
- Mile End Lane
- Mile End Lane
- Beechgrove Avenue
- Hosefield Road
- Rosebery Street
- Hosefield Avenue
- Summerhill Road
- Mastrick Drive
- Whitemyres Place
- Whitemyres Place
- Stronsay Drive
- Stronsay Drive
- Raeden Place
- Raeden Place
- Raeden Crescent
- Raeden Crescent
- Westburn Road
- Midstocket Road
- Midstocket Road
- Westburn Road @ Raeden Avenue
- Duthie Park, Gt Southern Road
- Pittodrie Stadium
- Fittie (Footdee)
- High Street, Old Aberdeen
- Denview Wynd
- Dobbie's Garden Centre
- Dobbie's Garden Centre
- Westburn Road @ Raeden Avenue
- Esplanade, Beach Boulevard
- Kingswood Gardens
- Kingswood Gardens
- Broaddykes Drive
- Broaddykes Drive
- Kingswells Drive
- Coldstone Avenue
- Kingswood Drive
- Fairley Road
- Kingswood Drive
- Wellside Walk
- Wellside Circle
- Concraig Gardens
- Wellside Wynd
- Derbeth Park
- Rousay Drive
- Dinbaith Place
- Osborne Place
- Osborne Place
- Wallfield Crescent
- Wallfield Crescent
- Holburn Junction
- Holburn Junction
- Langstane Kirk
- Langstane Kirk
- Music Hall
- Music Hall
- City Centre, Bridge Street
- City Centre, Bridge Street
- Aberdeen, His Majestys Theatre
- City Centre, Broad Street
- Union Square, St Magnus House
- Upperkirkgate
- Kingswells Crescent
- Kingswells Crescent
- Wentworth Road
- Wentworth Road
- James Arnott Drive
- James Arnott Drive
- Explorer Road
- Gemini Crescent
- Lochinver Crescent
- Thurso Crescent
- Barns of Claverhouse, Middleton Cresc.
- St Pauls Academy
- McTaggart Centre
- Kinloch Street
- Campfield Square
- Nethergate
- Lochinver Crescent
- Deveron Terrace
- Ashbank Road
- Balgray Place
- Strathmore Place
- Asda, Myrekirk
- Asda Myrekirk
- Charleston Bar
- Lothian Crescent at the Crescent
- Lothian Crescent at Balumbie Primary School
- Lochee Bank Street
- Butterburn Square
- Crematorium
- Kilbride Place
- Herbrides Drive
- Glamis Road at Carseview Gardens
- Glamis Road opposite Carseview Gardens
- Union Street
- Riverside Place
- McLean Street
- Servite House
- Gleneagles Street
- Gleneagles Street
- Wentworth Street
- Wentworth Street
- Maggies Centre
- Technology Park Opp Luna Place
- Lynch Centre
- Medi Park
- Medi Park
- Carseview Centre
- Carseview Centre
- Maggies Centre
- Clayhills Drive
- Clayhills Drive
- Technology Park Luna Place
- Lynch Centre
- Sinclair Street
- Commercial Street Keiller Centre
- Strathmore Avenue
- Old Glamis Road opp. Kingsway College
- Adamsons Court
- Tesco South Road
- Shaftesbury Terrace
- Nethergate
- Loons Road
- Rankine Street
- Court Street
- Grays Lane
- Brown Street
- Seafield Lane
- Patons Lane
- Police Station
- Mitchell Street
- Canning Street
- Morgan Street
- Overgate
- High Street
- High Street Primark
- High Street Primark
- Dunsinane Avenue
- Park Road
- Hindmarsh Avenue
- Balgray Place
- Provost Road
- Hospital Street
- Hospital Street
- Craigie Avenue
- Balgowan Avenue
- Clarence Road
- kemnay Place
- Fintry Crescent
- Craigie Avenue
- Binstead Avenue
- Walrond Street
- Roseangle
- Bell and Sime
- Pitkerro Drive
- B and Q
- Foggyley Gardens
- Balmullo Square
- Montague Street
- Trottick Mains
- Crawford Place
- Post Office
- Perth Road Step Row
- Whitehall Street
- Woodside terrace
- Inchcape Place
- Benholm Place
- Whitehall Street
- Gellatly Street
- Landsdowne Gardens
- Ritchies Lane
- Mcvicars Lane
- University
- Queens Hotel
- Scott Street
- Park Hotel
- Ninewells Hospital Bus Stance
- Albert Square
- Craigie Street
- North Ellen St
- Strathmore Avenue
- Peel Street
- Muirton Road
- Lochee Park
- Tullideph Road
- Kemback Street
- Dalkeith Road
- Old Craigie Road
- Arbroath Road opp Eden Street
- Kenilworth Avenue
- Arklay Street at Fairbairn Street
- Strathmore Street
- Tannadice Street
- South Baffin Street
- Murray Street
- Thornbank Terrace
- Lillybank Road
- Lillybank Road
- Dalgleish Road
- Blackness Road
- Scott Street
- Aberfoyle Gardens
- Ballinard Road
- Edzell Street
- Forthill Road
- Muirside Terrace
- Arbroath Road
- Edzell Street
- Ceres Crescent
- Elcho Drive
- Kintail Place
- Balgowan Square
- Duncan Terrace
- Balgowan Place
- Hawick Drive
- Ballater Place
- Balunie Terrace
- Balunie Place
- Ballindean Road
- Harry Lawson
- Whitehall Theatre
- Whitehall Theatre
- Carberry Crescent
- The Willows
- Aberlady Crescent
- Ormiston Crescent
- Hyndford Street
- Abbotsford Place
- Hyndford Place
- Bellfield Street
- Blackness Road, Balgay Park
- Blackness Road near Marchfield Road
- Forest Park Road
- Glamis Road
- West Grove Avenue
- West Park Road
- Seymour Street
- West Grove Avenue
- and 490 more (see the full list on the map or in the GeoJSON)
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
9 findings, ordered by severity.
Show every finding
- Error6 instances
Block trips with overlapping stop times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: block_trips_with_overlapping_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2440 instances
2440 of 2440 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)
- Warning740 instances
740 of 740 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)
- Warning2 instances
Some service calendars have no days of the week switched on.
Trips tied to these calendars never run; they are dead data that can mask real schedule problems.
Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)
Validator rule: service_has_no_active_day_of_the_week · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
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)
- Info14 instances
Trip headsign matches intermediate stop (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'trip_headsign_matches_intermediate_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules 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. 1 validator error to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Met
- Service data covers the next 360 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 360 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 6 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. Read the full standards crosswalk.
- Correctness 73 / 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 85 / 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/xplore-dundee/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.