Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires · Correct or claim this listing
Feed status · checked 2026-07-13
Orbus (Otago Regional Council)
Based on the feed this agency publishes
First scorecard for this agency
Ahead of 49% of all tracked agencies and 46% of mid-size agencies. Operates in Otago, New Zealand. Comparisons use agencies currently tracked worldwide.
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.1, 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
908 of 908 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
2577 of 2577 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 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.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
⏱ A small file for most flat-fare systems.worth about +15 points in its category
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. 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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
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. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. 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 536 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 13 kinds of issue across 700 instances (0 error, 668 warning, 32 informational).
Service data covers the next 536 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.
2 accessibility depth signals
27 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (10, 10, 10, 10, 10, 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.
712 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Cumberland St, outside Countdown", "Cumberland St, outside New World", "Abbotsford Rd, cnr Severn St", 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.
Orbus provides live tracking in its rider tools, but no keyless public GTFS-Realtime endpoint was verified. 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.
- 10 (green)
- 10 (green)
- 10 (green)
- 10 (green)
- 10 (green)
- 10 (green)
- 14 (gray)
- 14 (gray)
- 15 (gray)
- 15 (gray)
- 18 (gray)
- 18 (gray)
- 18 (gray)
- 18 (gray)
- 18 (gray)
- 18 (gray)
- 19 (pink)
- 19 (pink)
- 19 (pink)
- 19 (pink)
- 1 (white)
- 1 (white)
- 1 (white)
- 1 (white)
- 33 (pink)
- 33 (pink)
- 33 (pink)
- 37 (orange)
- 37 (orange)
- 39 (orange)
- 39 (orange)
- 3 (yellow)
- 3 (yellow)
- 40 (yellow)
- 40 (yellow)
- 44 (teal)
- 44 (teal)
- 50 (teal)
- 50 (teal)
- 50 (teal)
- 55 (pink)
- 55 (pink)
- 5 (yellow)
- 5 (yellow)
- 5 (yellow)
- 5 (yellow)
- 5 (yellow)
- 61 (yellow)
- 61 (yellow)
- 63 (purple)
- 63 (purple)
- 70 (white)
- 70 (white)
- 70 (white)
- 70 (white)
- 77 (orange)
- 77 (orange)
- 78 (orange)
- 78 (orange)
- 8 (red)
- 8 (red)
- 95 (yellow)
- 95 (yellow)
- 96 (yellow)
- 1 (gray)
- 1 (gray)
- 1 (gray)
- 2 (teal)
- 2 (teal)
- 2 (teal)
- 3 (yellow)
- 3 (yellow)
- 4 (pink)
- 4 (pink)
- 4 (pink)
- 4 (pink)
- 5 (pink)
- 5 (pink)
- 6 (brown)
- 6 (brown)
| Route | Type | Line color |
|---|---|---|
| 10 Shiel Hill to Opoho | Bus | green |
| 10 Opoho to Shiel Hill | Bus | green |
| 10 Shiel Hill to City | Bus | green |
| 10 Opoho to City | Bus | green |
| 10 City to Opoho | Bus | green |
| 10 City to Shiel Hill | Bus | green |
| 14 City to Port Chalmers | Bus | gray |
| 14 Port Chalmers to City | Bus | gray |
| 15 Ridge Runner Northbound | Bus | gray |
| 15 Ridge Runner Southbound | Bus | gray |
| 18 Portobello to City | Bus | gray |
| 18 City to Portobello | Bus | gray |
| 18 Harington Point to City | Bus | gray |
| 18 City to Harington Point | Bus | gray |
| 18 Portobello to City via Musselburgh | Bus | gray |
| 18 City to Harington Point via Musselburgh | Bus | gray |
| 19 Waverley to Belleknowes | Bus | pink |
| 19 Belleknowes to Waverley | Bus | pink |
| 19 Waverley to Belleknowes | Bus | pink |
| 19 Belleknowes to Waverley | Bus | pink |
| 1 City to Palmerston | Bus | white |
| 1 Palmerston to City | Bus | white |
| 1 City to Warrington | Bus | white |
| 1 Warrington to City | Bus | white |
| 33 Corstorphine to Wakari | Bus | pink |
| 33 Wakari to Corstorphine | Bus | pink |
| 33 Corstorphine to City | Bus | pink |
| 37 Concord to Logan Park | Bus | orange |
| 37 Logan Park to Concord | Bus | orange |
| 39 Green Island to Otago Boys High School | Bus | orange |
| 39 Otago Boys High School to Green Island | Bus | orange |
| 3 Ocean Grove to Ross Creek | Bus | yellow |
| 3 Ross Creek to Ocean Grove | Bus | yellow |
| 40 Green Island to Kings/Queens High | Bus | yellow |
| 40 Kings/Queens High to Green Island via Corstorphine | Bus | yellow |
| 44 St Kilda to Halfway Bush | Bus | teal |
| 44 Halfway Bush to St Kilda | Bus | teal |
| 50 St Clair Park to Helensburgh | Bus | teal |
| 50 Helensburgh to St Clair Park | Bus | teal |
| 50 St Clair Park to City | Bus | teal |
| 55 St Kilda to Brockville | Bus | pink |
| 55 Brockville to St Kilda | Bus | pink |
| 5 Calton Hill to Pine Hill via South Road | Bus | yellow |
| 5 Pine Hill to Calton Hill via South Road | Bus | yellow |
| 5 Calton Hill to Pine Hill via Hillside Road | Bus | yellow |
| 5 Pine Hill to Calton Hill via Hillside Road | Bus | yellow |
| 5 Calton Hill to City | Bus | yellow |
| 61 Kenmure to City | Bus | yellow |
| 61 City to Kenmure | Bus | yellow |
| 63 Balaclava to Logan Park | Bus | purple |
| 63 Logan Park to Balaclava | Bus | purple |
| 70 Brighton to Green Island | Bus | white |
| 70 Brighton to KVC via Green Island | Bus | white |
| 70 Green Island to Brighton | Bus | white |
| 70 KVC to Brighton via Green Island | Bus | white |
| 77 Mosgiel to City | Bus | orange |
| 77 City to Mosgiel | Bus | orange |
| 78 Mosgiel to City Express | Bus | orange |
| 78 City to Mosgiel Express | Bus | orange |
| 8 St Clair to Normanby | Bus | red |
| 8 Normanby to St Clair | Bus | red |
| 95 Logan Park High School to Pine Hill via Opoho | Bus | yellow |
| 95 Pine Hill to Logan Park High School | Bus | yellow |
| 96 Dunedin North Intermediate to Pine Hill | Bus | yellow |
| 1 Sunshine Bay to Remarkables Shops | Bus | gray |
| 1 Remarkables Shops to Sunshine Bay | Bus | gray |
| 1 Remarkables Shops to Sunshine Bay | Bus | gray |
| 2 Frankton Hub to Arrowtown | Bus | teal |
| 2 Arrowtown to Frankton Hub | Bus | teal |
| 2 Arrowtown to Frankton Hub via Events Centre | Bus | teal |
| 3 Quail Rise to Kelvin Heights | Bus | yellow |
| 3 Kelvin Heights to Quail Rise | Bus | yellow |
| 4 Jacks Point to Arrowtown via Queenstown | Bus | pink |
| 4 Arrowtown to Jacks Point via Queenstown | Bus | pink |
| 4 Jacks Point to Arrowtown via Wakatipu High and Queenstown | Bus | pink |
| 4 Arrowtown to Jacks Point via Queenstown and Wakatipu High | Bus | pink |
| 5 Lake Hayes Estate to Queenstown | Bus | pink |
| 5 Queenstown to Lake Hayes Estate | Bus | pink |
| 6 Queenstown to Hilton | Ferry | brown |
| 6 Hilton to Queenstown | Ferry | brown |
This feed has 908 stops.
List every stop
- Cumberland St, outside Countdown
- Cumberland St, outside New World
- Abbotsford Rd, cnr Severn St
- Abbotsford Rd, cnr Waldron Cres
- Albany St, Clubs & Societies
- Aberdeen Rd, 12
- Albany St, Central Library
- Aberdeen Rd, 54
- Albany St, Museum Reserve
- Andersons Bay Rd, 559
- Andersons Bay Rd, 521
- Andersons Bay Rd, 271
- Andersons Bay Rd, 486
- Ashmore St, 111
- Ashmore St, 27
- Ashmore St, 7
- Ashmore St, 97
- Halfway Bush Terminus
- Balmacewen Rd, 10
- Balmacewen Rd, 178
- Balmacewen Rd, 185
- Balmacewen Rd, 206
- Bank St, Pet Doctors
- Bank St, Layby
- Bay View Rd, 111
- Bay View Rd, 71
- Bay View Rd, 87
- St Clair Terminus
- Belford St, 144
- Belford St, 68
- Belford St, 98
- Belford St, Reserve
- Belgrave Cres, 71 Highgate
- Bath St, 23
- Bath St, 18
- Borlases Rd, cnr Blueskin Rd
- Borlases Rd, opposite anchor
- Brighton Rd, cnr McColl Rd
- Brighton Rd, cnr Edna St
- Brighton Rd, 1016
- Brighton Rd, 44
- Brighton Rd, 349
- Brighton Rd, 45
- Brighton Rd, 487
- Brighton Rd, 587
- Brighton Rd, 590
- Brighton Rd, 723
- Brighton Rd, 791
- Brighton Rd, 820
- Brighton Rd, 980
- Brighton Rd, cnr Allen Rd
- Brighton Rd, 10
- Brighton Rd, cnr Creamery Rd
- Brighton Rd, cnr Main South Rd
- Brighton Rd, 369
- Brighton Rd, cnr Wavy Knowes Dr
- Brighton Rd, 336
- Brighton Rd, cnr Friendship Dr
- Brighton Rd, 488
- Brighton Rd, opposite Allen Rd
- Brighton Rd, 863
- Brighton Rd, Island Park
- Brighton Rd, Cemetery
- Brighton Rd, opposite Viscount Rd
- Brighton Rd, 331
- Brighton Rd, opposite Cemetery
- Brighton Rd, 944
- Brockville Rd, 110
- Brockville Rd, 162
- Brockville Rd, 224
- Brockville Rd, 248
- Brockville Rd, 48
- Brockville Rd, 276
- Brockville Rd, 165
- Brockville Rd, 19
- Brockville Rd, 193
- Brockville Rd, 247
- Brockville Rd, 263
- Brockville Rd, 47
- Brockville Rd, 101
- Brockville Rd, 295
- Brockville Terminus
- Bryant St, 3
- Gordon Rd, 13
- Careys Bay Hotel
- Carnock Rd, cnr Stepney Ave
- Castle St, 289
- Castle St, 201
- Chapman St, 119
- Chapman St, 120
- Chapman St, 160
- Chapman St, 37
- Chapman St, 46
- Chapman St, 65
- Chapman St, 102
- Chapman St, opposite 160
- Gordon Rd, 6
- Kokomuka Ave, cnr Stepney Ave
- Corstorphine Rd, 12
- Corstorphine Rd, 136
- Corstorphine Rd, 143
- Corstorphine Rd, 193
- Corstorphine Rd, 31
- Corstorphine Rd, 81
- Corstorphine Rd, cnr Sidey St
- Crichton St, 9
- Crichton St, 6
- Cumberland St, 894
- Dale St, 2
- Dale St, 7
- Dall St, 1A
- David St, 3
- David St, 42
- David St, 51
- David St, 76
- Drivers Rd, 34A
- Drivers Rd, 39
- Drivers Rd, 4
- Drivers Rd, cnr Tolcarne Ave
- Duke St, 18
- Duke St, 24
- Duke St, opposite Queen St
- Dundas St, 141
- Dundas St, 113
- Dundas St, 118
- Dundas St, 158
- Earls Rd, 65
- Eastbank St, 8
- Easther Cres, 33
- Easther Cres, 7
- Eglinton Rd, 154
- Elgin Rd, 165
- Eglinton Rd, opposite Peel St
- Eglinton Rd, cnr High St
- Elgin Rd, 27
- Elgin Rd, 44
- Elgin Rd, 71
- Exmouth St, 5B
- Factory Rd, 29
- Factory Rd, 18
- Factory Rd, 75
- Factory Rd, 47
- Factory Rd, 66
- Mosgiel Terminus
- Factory Rd, 86
- Forbury Rd, 117
- Forbury Rd, 166
- Forbury Rd, 147
- Forbury Rd, 181
- Forbury Rd, 198
- Forbury Rd, 213
- Forbury Rd, 232
- Forbury Rd 94
- Forbury Rd, opposite 74
- Forresbank Ave (Wakari Terminus)
- Fulton Rd, 385
- Malvern St, 397
- Garden Village Terminus
- George St, 1076
- George St, 590
- George St, 607
- George St, 664
- George St, 745
- George St, 12
- George St, 77-79
- George St, 788
- George St, 811
- George St, 888
- George St, 984
- George St Normal School
- George St, 472
- George St, Knox Church garden
- George St, 1011
- George St, 72
- George St, 3
- Glenholm St, 57
- Glenholm St, opposite 55
- Glenmore St, 38
- Glenmore St, 39
- Glenmore St, 6
- Glenmore St, opposite 6
- Glenpark Ave, 71
- Glenpark Ave, 72
- Glenpark Ave, 130
- Glenpark Ave, 50
- Glenpark Ave, opposite 56
- Glenpark Ave, 35
- Glenpark Ave, 129
- Gordon Rd, Countdown
- Gordon Rd, Glasgow St Busbay
- Gordon Rd, 46
- Gordon Rd, 63
- Gordon Rd, 64
- Gordon Rd, 85
- Gordon Rd, 94
- Gordon Rd, cnr Bruce St
- Gordon Rd, 25
- Gordon Rd, Clocktower
- Great King St North, Botanic Gardens
- Great King St, 686
- Great King St, 806
- Greenhill Ave, 3
- Harbour Tce, 58
- Harbour Tce, 41
- Harington Point Rd, cnr Tamatea Rd
- Harington Point Rd, cnr Golf Course Rd
- Harington Point Rd, 897
- Harington Point Rd, cnr Pipikaretu Rd
- Harington Point Rd, 238
- Harrington St, cnr Fox St
- Harrington St, 27
- Harrington St, 26
- Helensburgh Rd, 261
- Helensburgh Rd, 266
- Helensburgh Rd, 298
- Helensburgh Rd, 281
- High St, opposite High St School
- High St, 184
- High St, 246
- High St, 249
- High St, 310
- High St, 327
- High St, 382
- High St, 403
- High St, 412
- High St, 440
- Eglinton Rd, cnr Queens Drive
- Highcliff Rd, 1
- Highcliff Rd, 114
- Highcliff Rd, 157
- Highcliff Rd, 160
- Highcliff Rd, 193-195
- Highcliff Rd, 196
- Highcliff Rd, 242
- Highcliff Rd, 247
- Highcliff Rd, 281
- Highcliff Rd, 38
- Highcliff Rd, 51
- Highcliff Rd, 73
- Highcliff Rd, 80
- Highcliff Rd, 113
- Highgate, 216
- Highgate, 227
- Highgate, 271
- Highgate, 280
- Highgate, 343
- Highgate, 354
- Highgate, 399
- Highgate, 408
- Highgate, 460
- and 658 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
- Warning2577 instances
2577 of 2577 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)
- Warning908 instances
908 of 908 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)
- Warning594 instances
Stop too far from shape using user distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning32 instances
Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_diff_coordinates_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning28 instances
Missing bike allowance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_bike_allowance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: missing_bike_allowance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 instances
Equal shape distance same coordinates (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_same_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: equal_shape_distance_same_coordinates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
Two or more routes share the same name.
Riders can't tell the routes apart in apps.
Fix: Give each route a distinct short or long name. (One field per route.)
Validator rule: duplicate_route_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules 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
Missing feed contact email and url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Validator rule: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Validator rule: unused_shape · 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)
- Info25 instances
Big gap in service (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'big_gap_in_service' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info4 instances
Service window outside feed period (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_window_outside_feed_period' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3 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.)
Validator rule: unknown_column · Read the fix guide · 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)
Some fixes we can make for you
These are the safe mechanical fixes, applied to a copy of your feed. They change only what is certain and leave everything else untouched. Review the diff before you publish.
Trimmed surrounding whitespace 1 change
For example: 'route_long_name': 'Shiel Hill to City ' -> 'Shiel Hill to City'
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 536 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 563 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 50 / 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 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.
- 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 live badge on your agency site or feed README. It updates daily 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/orbus-otago/2026-07-13.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-13. 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.