Feed status · checked 2026-10-23
goBay (Hawke's Bay Regional Council)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Cataloged in Hawke's Bay, New Zealand.
Source feed: https://www.gobay.co.nz/assets/HBRC-GTFS-January-2026.zip
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.4, validator 8.0.1.
Measured 3 of 4 score categories from the official feed URL on file.
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 official feed URL on file.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
About this feed
goBay (Hawke's Bay Regional Council)’s published feed lists 11 bus routes, 352 scheduled trips and 514 stops.
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
514 of 514 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.
Fixing this covers all 514 stops in the feed.
⏱ 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
352 of 352 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Fixing this covers all 352 trips in the feed.
⏱ 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.
This one is about the feed as a whole, so there is no share of it to count.
⏱ Two fields, set once in export settings.worth about +15 points in its category
Riders and need behind these fixes
- Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
- The served-area need overlays cover the United States and Canada, so none of them applies to this feed.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
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.
- Finding
- Fix 01 in Top things to fix: its feed evidence and the requested 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
- Finding
- Fix 02 in Top things to fix: its feed evidence and the requested 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
- Finding
- Fix 03 in Top things to fix: its feed evidence and the requested 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
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.
Fix 01 · Read the fix guide for scorecard_wheelchair_boarding_unknown
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.
Fix 02 · Read the fix guide for scorecard_wheelchair_accessible_unknown
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.
Fix 03 · Read the fix guide for scorecard_missing_feed_info_dates
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 97 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 7 kinds of issue across 188 instances (0 error, 155 warning, 33 informational).
Service data covers the next 97 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
3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (2, 3, 8).
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.
150 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("100 Flaxmere Ave", "1000 Soutland Rd", "1001 Gordon Rd", 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.
This feed has 514 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.
- 1A (teal)
- 1 (teal)
- 2 (orange)
- 3 (pink)
- 4 (yellow)
- 6 (green)
- 7 (yellow)
- 8 (gray)
- 11 (blue)
- 6A (green)
- 7A (yellow)
| Route | Type | Line color |
|---|---|---|
| 1A Napier - Hastings via Pakowhai Road | Bus | teal |
| 1 Hastings - Napier - Havelock North | Bus | teal |
| 2 Napier - Taradale - EIT | Bus | orange |
| 3 Napier, Maraenui and Tamatea | Bus | pink |
| 4 Napier, Airport, Bayview | Bus | yellow |
| 6 Flaxmere - Akina | Bus | green |
| 7 Flaxmere - Karamu | Bus | yellow |
| 8 Hastings Circular | Bus | gray |
| 11 Napier, Hastings, Te Mata | Bus | blue |
| 6A Flaxmere - Akina (HBHS) | Bus | green |
| 7A Flaxmere - Hastings (HBHS) | Bus | yellow |
List every stop
- 601 Lowe Street
- 100 Flaxmere Ave
- 1000 Soutland Rd
- 1001 Gordon Rd
- 1001 Southland Rd
- 1002 Grove Road
- 1004 Outram Rd
- 101 Flaxmere Ave
- 1014 Outram Road
- 1015 Frederick St W
- 1016 Frederick St W
- 102 Dundee Drive
- 102 Guppy Road
- 103 Murdoch Road W
- 103 Omahu Road, outside TWL
- 105 Arataki Rd
- 105 Guppy Road
- 106 Murdoch Road
- 106-108 Southhampton St
- 107 Middle Rd
- 107 Russell Robertson Drive
- 109 Southhampton St W
- 11 Freyberg Ave
- 1120 Omahu Road, outside Higgens
- 1123 Omahu Road
- 115 Harold Holt Ave
- 12 Maadi Road
- 1207 Louie Street
- 1208 Omahu Road
- 126 Avondale Road
- 126 Brookvale Rd
- 126 Harold Holt Ave
- 128 Chatham Rd
- 1283 Omahu Road, outside Hustlers Signage
- 13 Bill Hercock St
- 13 Osier Rd
- 1330 Omahu Road
- 1361 Omahu Road, outside Turfreys
- 137 Guppy Road
- 14 Leicester Avenue - Opp Pak n Save
- 14 Osier Rd
- 140 Nuffield Ave
- 1409 Omahu Road
- 1416 Omahu Road, outside Carters Tyre Service
- 145 Arataki Rd
- 146 Guppy Road
- 1462 Omahu Road
- 15 Berwick St
- 150 Riverbend Road
- 152 Auckland Rd
- 155 Auckland Rd
- 161 Harold Holt Ave
- 166 Avondale Rd
- 166 Nuffield Ave
- 167 Wellesley Road
- 170 Guppy Road
- 172 Riverbend Road Stop
- 177 Guppy Road
- 18 Berwick St
- 184 Flaxmere Ave
- 186 Nuffield Ave
- 1D Austin St, outside Yamaha Motors
- 20 Railway Rd
- 204 Southampton St E
- 207 Auckland Road
- 208 Nottingley Road Stop
- 208 Willowpark Road North
- 21 Lancaster St
- 214 Chatham Rd
- 215 Nottingley Road
- 22 Peterhead Ave Stop
- 220 Flaxmere Ave Stop, outside Flaxmere Christian Fellowship
- 227 Georges Drive Stop
- 23 Bright Crescent Stop
- 24 Alexander Ave
- 254 Flaxmere Ave
- 26 Charles Street
- 26 Coronation Street, outside old Church
- 26 Diaz Drive
- 26-28 York Ave
- 27 Ranfurly St
- 28 Guppy Road
- 28 Kirkwood Rd
- 29 Diaz Drive Stop
- 290 Flaxmere Ave
- 3 Ranfurly St
- 3-5 Russell Robertson Drive
- 30 Palmerston Road
- 302 Willowpark Rd
- 302-304 Nelson St N
- 303 Murdoch Road
- 303 Nelson Street N
- 304 Takapu Road
- 307 Willowpark Rd
- 309 Takapu Rd
- 319 Flaxmere Ave Stop
- 32 Upham Street
- 320A Flaxmere Ave
- 322B Portsmouth Rd
- 33 Maadi Road
- 36 Te Aute Rd
- 361 Flaxmere Ave
- 37 Guppy Road
- 37 Russell Robertson Drive
- 37 Southwark Avenue
- 4 Peterhead Ave Stop
- 400 Karamu Rd S
- 402 Huia Street
- 402 Nottingley Road Stop
- 404 Takahe Street
- 405 Huia Street
- 405 Orchard Rd
- 406 Frederick St W
- 407 Nottingley Road
- 408 Southhampton St W
- 408 Willowpark Road North
- 409 Frederick St W
- 413 Hastings St
- 414 Massey St
- 415 Massey St
- 42 Bill Hercock Street
- 42 Southwark Avenue Stop
- 420 Murdoch Road
- 423 Murdoch Rd W
- 43 Pandora Road
- 44 Walton Way
- 45 Arataki Rd
- 46 Orotu Drive Stop
- 47 Bill Hercock Street Stop
- 47 McGrath St, outside Downey's Butchery
- 5 Arataki Rd, opposite Summerset Village
- 5 Nash St
- 501 (outside Ellison Road pedestrian entrance)
- 507 Southland Rd
- 509 Huia St
- 510 Huia Street
- 510 Nelson St W
- 52 Dundee Drive
- 529 Main North Road
- 537 Lowe Street
- 540 Lowe Street
- 55 Diaz Drive Stop
- 568 Lowe Street
- 58 Upham Street
- 6 Dundee Drive
- 60 Palmerston Road
- 60-62 Iona Rd
- 600 Gordon Road, Ebbet Park entrance
- 602 Grove Road
- 603 Grove Road
- 604 Nelson St
- 604 Nottingley Road Stop
- 605 Orchard Rd
- 607 Nelson St N
- 609 Nottingley Road
- 610 Massey St (opposite current stop)
- 62 - 66 Whakatu Road
- 63 Flaxmere Ave
- 64 Flaxmere Ave
- 65 Caernarvon Drive
- 65 Guppy Road
- 66 Bill Hercock Street
- 66-68 Te Aute Road
- 67 Kirkwood Rd
- 7 Dundee Drive
- 700 Huia Street
- 700 Karamu Rd S
- 702 Willowpark Road North
- 703 Willowpark Rd
- 704 Lumsden Road
- 707 Nelson St N
- 709 Huia St
- 71 Arataki Rd
- 714 Karamu Rd Stop, outside Speedy Signs
- 72 Alexander Ave
- 72 Guppy Road
- 73 Russell Robertson Drive
- 76 Orotu Drive
- 77 Bill Hercoclk Street, outside Pirimai Plaza Dairy
- 78 Kirkwood Rd
- 79 Harold Holt Ave Stop
- 79 Whakatu Road
- 79A Diaz Drive
- 8 Coronation St
- 807 Frederick St W
- 808 Frederick St W
- 810 Maraeakakaho Rd
- 811 Maraekakaho Road
- 814 Kiwi Street
- 814 Outram Rd
- 817 Outram Rd
- 82 Diaz Drive
- 82 Dundee Drive
- 82 McGrath St
- 83 Meeanee Quay
- 84 Harold Holt Ave
- 85 Bledisloe Rd
- 88 Charles Street
- 90 Gloucester St
- 902A Willowpark Road North
- 907 Willowpark Rd
- 908 - 910 Maraekakaho Rd
- 911 Maraekakaho road
- 922 Gordon Road
- After 1243 Omahu Road
- Around 200 Chatham Rd, outside Ron Giorgi Park I
- Around 200 Chatham Rd, outside Ron Giorgi Park II
- 226 Auckland Road
- Bay Plaza
- 4-6 Orotu Drive
- Station Street at Burger King
- Canning Road opp 111
- Canning Road outside 111
- Corner of Coronation St and Te Atu St
- Flaxmere Hub Stop 1
- Flaxmere Hub Stop 2
- Hardinge Road opp 66
- Hawke's Bay Airport
- Iona Rd outside 132
- Iona Road outside 133
- 87 Wharerangi Rd
- Corner of Reynolds and Middle Road, outside 151
- Outside Kmart Napier
- Mahora Shops - 606 Frederick St
- Mahora Shops - 607 Frederick St W
- McLean Park, outside 36
- Middle Road, opposite 122
- Kennedy Road, opp Napier Salvation Army
- Opp. 161 Harold Holt Ave
- Opp Hastings Boys High School
- Opp. Hastings Library
- Opp. Princess Alexandra Village
- Opp. 1/505B Southland Rd
- Opp. 10 Orotu Drive
- Opposite 1000 Grove Road
- Opposite 1002 Copeland Rd
- Opposite 102 Wilson Road
- Opposite 1210 Omahu Road
- Opposite 126 Chatham Rd
- Opposite 1262 Louie Street
- Opposite 1367 Omahu Road, outside Metal Craft Fencing
- Opposite 167 Wellesley Road
- Opposite 204 Southampton St E
- Opposite 214 Chatham Rd
- Opposite 225 Georges Drive
- Opposite 28 Railway Rd
- Opposite 303 Murdoch Road
- Opposite 328 Portsmouth Rd
- Opposite 36 Kirkwood Rd
- Opposite 405 Orchard Rd
- and 264 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
12 findings, ordered by severity.
Show every finding
- Warning514 instances
514 of 514 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning352 instances
352 of 352 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning125 instances
On some trips the stop distances run a little past the end of the route line.
The stop and shape distance values don't quite line up, so any math that uses them can drift.
Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide for trip_distance_exceeds_shape_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning24 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 for stop_without_stop_time · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 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 for expired_calendar · 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.)
Finding code: missing_recommended_file · Read the fix guide for missing_recommended_file · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · Read the fix guide for route_color_contrast · 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.)
Finding code: scorecard_missing_feed_info_dates · Read the fix guide for scorecard_missing_feed_info_dates · 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.)
Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info32 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 for unknown_column · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
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 for unknown_file · 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).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
One requirement remains for this feed to earn 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 97 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 24 of 514 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 97 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 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.
Part of the New Zealand portfolio: the same scorecards for every feed we track in that group, on one free page.
Show your grade
Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.
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/gobay-hawkes-bay/2026-10-23.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-10-23. 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.