Feed status · checked 2026-07-18
Unibus (Bournemouth)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Bournemouth, Christchurch and Poole, 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
Re-export with a validity window that reaches at least 60 days out.Likely your export tool
Service data runs out in 8 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
⏱ One export setting.worth about +72 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
1090 of 1090 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
4226 of 4226 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.
Re-export with a validity window that reaches at least 60 days out. · 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_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 8 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.
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 3 kinds of issue across 500 instances (0 error, 500 warning, 0 informational).
Service data runs out in 8 day(s). Publish an updated feed soon or riders will lose trip planning.
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
48 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("St Swithun's Roundabout", "St James School", "St Peter's Church [AA1]", 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.
- 11 (white)
- 12 (white)
- 13 (white)
- 13A (white)
- 15 (white)
- 16 (white)
- 17 (white)
- 18 (white)
- 1A (white)
- 1B (white)
- 1C (white)
- 21 (white)
- 22 (white)
- 36 (white)
- 5 (white)
- 6 (white)
- N1 (white)
- N2 (white)
- N5 (white)
- U1 (white)
- U3 (white)
- X3 (white)
- m1 (white)
- m2 (white)
| Route | Type | Line color |
|---|---|---|
| 11 | Bus | white |
| 12 | Bus | white |
| 13 | Bus | white |
| 13A | Bus | white |
| 15 | Bus | white |
| 16 | Bus | white |
| 17 | Bus | white |
| 18 | Bus | white |
| 1A | Bus | white |
| 1B | Bus | white |
| 1C | Bus | white |
| 21 | Bus | white |
| 22 | Bus | white |
| 36 | Bus | white |
| 5 | Bus | white |
| 6 | Bus | white |
| N1 | Bus | white |
| N2 | Bus | white |
| N5 | Bus | white |
| U1 | Bus | white |
| U3 | Bus | white |
| X3 | Bus | white |
| m1 | Bus | white |
| m2 | Bus | white |
This feed has 1090 stops.
List every stop
- Stour Road
- Stour Road
- Priory Corner
- Stony Lane
- Stony Lane
- Livingstone Road
- Livingstone Road
- Purewell Cross
- Purewell Cross
- Dennistoun Avenue
- Dennistoun Avenue
- Airfield Way
- Airfield Way
- Christchurch Trade Park
- Christchurch Trade Park
- Meteor Shopping Park
- Meteor Shopping Park
- Somerford Sainsbury's
- Meteor Shopping Park
- St Joseph's School
- St Joseph's School
- Hunt Road Flats
- Hunt Road Flats
- Hunt Road Shop
- Hunt Road Shop
- Hillary Road
- Hillary Road
- Tensing Road
- Tensing Road
- Knowles Close
- Knowles Close
- Purewell Medical Centre
- Stony Lane
- Christchurch Railway Station
- Christchurch Railway Station
- Fairfield
- Christchurch, Bargates [F]
- Gleadowe Avenue
- Kings Avenue
- Kings Avenue
- Riverland Court
- Riverland Court
- Twynham Avenue
- Brierley Avenue
- Albert Road
- Canford Bottom, Fryers Copse
- Lonsdale Road
- Lonsdale Road
- Colehill Lane
- Brabazon Drive
- Stony Lane
- Peregrine Road
- Bodowen Road
- Bodowen Road
- Hayes Lane Top
- Jumpers Corner
- Gardner Road
- Gardner Road
- Jumpers Road
- Jumpers Road
- Dragoon Way
- Dragoon Way
- Avenue Road
- Avenue Road
- Queen Elizabeth School
- Christchurch, Fountain Way [MM]
- Christchurch, Barrack Road [C]
- Jessopp Road
- Jessopp Road
- Foxcroft Drive
- Hayes Close
- Two Riversmeet Centre
- Ashley Heath Roundabout
- Ashley Heath Roundabout
- Wimborne Square [B]
- Wimborne Police Station
- Wimborne Police Station
- Quarter Jack Surgery
- Quarter Jack Surgery
- St John's Hill
- Wimborne, Avenue Road
- Gordon Road
- Gordon Road
- Parmiter Road
- Parmiter Road
- Leigh Road, Tops Nursery
- Leigh Road, Tops Nursery
- Hayes Close
- Foxcroft Drive
- Canford Bottom, Fryers Copse
- Hayes Lane Top
- Hayes Lane Top
- Colehill First School
- Colehill First School
- Colehill Pharmacy
- Colehill Pharmacy
- Colehill Post Office
- Colehill Post Office
- Cobbs Road
- Cobbs Road
- Onslow Gardens
- Onslow Gardens
- Wimborne, top of St John's Hill
- Wimborne, top of St John's Hill
- St John's Church
- St John's Church
- Coach & Horses
- Coach & Horses
- Station Road
- Station Road
- Colehill Lane
- Fox Lane
- Fox Lane
- Stapehill Garden Centre
- Stapehill Garden Centre
- Uddens Cross
- Uddens Cross
- Ferndown Industrial Estate
- Ferndown Industrial Estate
- Hill Top Garage
- Hill Top Garage
- Pure Drop Inn
- Pure Drop Inn
- Church Road
- Ferndown Town Centre
- Victoria Road/Wimborne Road
- Victoria Road/Wimborne Road
- Church Road
- Albert Road
- Ferndown Town Centre
- Chander Close
- Chander Close
- Old Pines Close
- Old Pines Close
- Dudsbury Avenue
- Dudsbury Avenue
- Chapelgate Garage
- Chapelgate Garage
- Winnards Close
- Winnards Close
- Fairfield
- Christchurch, High Street [A]
- Christchurch, High Street [B]
- Christchurch, Bargates [E]
- Jumpers Corner
- All Saints Church
- All Saints Church
- Chichester Way
- Chichester Way
- De Haviland Way
- De Haviland Way
- Mudeford Junior School
- Mudeford Junior School
- Caroline Avenue
- Caroline Avenue
- Purewell Medical Centre
- Purewell Medical Centre
- Stony Lane Railway Arch
- Stony Lane Railway Arch
- Sandy Plot
- Sandy Plot
- Gordon Way
- Gordon Way
- The Oak Inn
- The Oak Inn
- Burton Green
- Burton Green
- Burton Hall Place
- Burton Primary School
- Priory View Road
- Burton, Birch Avenue
- Burnham Road
- Barlands Close
- Heathlands Close
- The Runway Industrial Park
- The Runway Industrial Park
- Brabazon Drive
- Blenheim Drive
- Blenheim Drive
- Grebe Close
- Grebe Close
- Peregrine Road
- Ricardo Crescent
- Ricardo Crescent
- Bure Haven Drive
- Bure Haven Drive
- Mudeford, Avon Beach Approach
- Mudeford, Avon Beach Approach
- Parley Cross, Crossroads
- Parley Cross, Crossroads
- Dudsbury Gardens
- Dudsbury Gardens
- Brierley Avenue
- Becket Crescent
- Becket Crescent
- Bohemia Gardens
- Bohemia Gardens
- Canford Paddock, Beaumaris Road
- Canford Paddock, Beaumaris Road
- Fitzwilliam Close
- Fitzwilliam Close
- King Richard Drive
- King Richard Drive
- Knights Road
- Viscount Walk
- Viscount Walk
- King John Avenue
- King John Avenue
- Bearwood Co-op
- Bearwood Co-op
- St John's Church
- St John's Church
- Discovery Court
- University, Wallisdown Road
- St Mark's Church
- Bournemouth University, Talbot Campus [G]
- Valley View
- Mickleham Close
- Marianne Road
- University, Wallisdown Road
- Barters Lane
- Cotes Avenue
- Cotes Avenue
- Kitchener Crescent Top
- Kitchener Crescent Top
- Waterloo Road/Sopers Lane
- French Road
- French Road
- Plumer Road
- Plumer Road
- Waterloo Estate, Milne Road
- Waterloo Estate, Milne Road
- Methuen Road
- Methuen Road
- Broadstone, Broadway
- Broadstone, Broadway
- Waterloo Road/Sopers Lane
- St Anthony's Church
- St Anthony's Church
- Mission Road
- Mission Road
- Beech Wood Close
- Beech Wood Close
- Selby Close
- Selby Close
- Gladelands Way
- Broadstone, Maxwell Road
- Beacon Road
- Mallow Close
- Bryony Close
- and 840 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
- Warning4226 instances
4226 of 4226 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)
- Warning1090 instances
1090 of 1090 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)
- Warning322 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)
- Warning177 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.)
Validator rule: expired_calendar · 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
Service data runs out in 8 day(s).
When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)
Validator rule: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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. Service data runs out in 8 days; renew to qualify. 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 Not yet
- Service data runs out in 8 days; renew to qualify.
- 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.
At risk for the Google and Apple Maps four-week coverage bar. This feed has 8 days of service left. Maps needs at least four weeks (28 days) of upcoming service, so your agency will fall out of trip planners soon. Re-export with a longer calendar.
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 80 / 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 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.
- 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/unibus-bournemouth/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.