Feed status · checked 2026-09-05
Hatsukaichi City Bus (廿日市市自主運行バス)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Hiroshima, Japan.
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.3, validator 8.0.1.
Checked for changes 2 hours ago; last changed 2 hours ago.
Measured 4 of 4 score categories from the official feed URL on file.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- 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.
Top things to fix
Add the required column named in the finding to the flagged file.Likely your export tool
A file is missing a column that GTFS requires. Apps may reject the whole file, so riders could lose the affected routes or stops.
⏱ Often an export setting; ask your vendor if it recurs.worth about +12 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
329 of 329 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
204 of 204 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
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.
- Feed evidence
- A file is missing a column that GTFS requires.
- Next action
- Add the required column named in the finding to the flagged file.
- 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
- Feed evidence
- 329 of 329 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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
- Feed evidence
- 204 of 204 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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.
Add the required column named in the finding to the flagged file. · 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 164 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
- Fare information is published using GTFS Fares v1.
- Realtime information
- One or more realtime feeds were reachable; live-arrival coverage is not known.
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 9 kinds of issue across 6133 instances (3 error, 6111 warning, 19 informational).
Service data covers the next 164 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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
Fares are applied to trips.
Sampled 9 times outside service hours: 3 of 3 configured feeds healthy; vehicle position plausibility was not measurable.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 329 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.
- 廿日市市さくらバス 阿品ルート (green)
- 廿日市さくらバス 原ルート (green)
- 廿日市市さくらバス 吉和ルート (green)
- 佐伯さくらバス 玖島線 (green)
- 廿日市市さくらバス 宮内ルート (green)
- 廿日市市さくらバス 阿品台ルート (green)
- 廿日市市さくらバス 佐方ルート (green)
| Route | Type | Line color |
|---|---|---|
| 廿日市市さくらバス 阿品ルート | Bus | green |
| 廿日市さくらバス 原ルート | Bus | green |
| 廿日市市さくらバス 吉和ルート | Bus | green |
| 佐伯さくらバス 玖島線 | Bus | green |
| 廿日市市さくらバス 宮内ルート | Bus | green |
| 廿日市市さくらバス 阿品台ルート | Bus | green |
| 廿日市市さくらバス 佐方ルート | Bus | green |
List every stop
- 玖波分れ
- 玖波分れ
- 河津
- 河津
- 中山
- 中山
- 浜本工芸前
- 浜本工芸前
- 佐伯中学校前
- 佐伯中学校前
- 佐伯高校前
- 佐伯高校前
- 津田神社
- 津田神社
- 十王堂
- 十王堂
- さいき文化センター
- さいき文化センター
- 佐伯支所
- 佐伯支所
- 津田
- 津田
- 津田小学校下
- 津田小学校下
- 郷西
- 郷西
- 内山
- 内山
- 岩倉キャンプ場前
- 岩倉キャンプ場前
- 下岩倉
- 下岩倉
- 岩倉
- 岩倉
- 中栗栖
- 中栗栖
- 栗栖
- 栗栖
- 上栗栖
- 上栗栖
- 小瀬川温泉前
- 小瀬川温泉前
- 北山トンネル
- 北山トンネル
- 悪谷
- 悪谷
- 羅漢温泉
- 羅漢温泉
- 出合
- 出合
- 出合水門口
- 出合水門口
- 黒打橋
- 黒打橋
- 下飯山
- 下飯山
- 冠高原下
- 冠高原下
- 冠高原入口
- 冠高原入口
- 一軒屋
- 一軒屋
- 幟町村
- 幟町村
- 上頓原
- 上頓原
- 頓原
- 頓原
- 下頓原
- 下頓原
- 潮原温泉
- 潮原温泉
- 下潮原
- 下潮原
- 上中津谷
- 上中津谷
- 匹見分れ
- 匹見分れ
- 中津谷
- 中津谷
- 大向
- 大向
- 上花原
- 上花原
- 花原
- 花原
- 吉和ふれあい交流センター
- 吉和ふれあい交流センター
- 市垣内
- 市垣内
- 上田中原
- 上田中原
- 吉和田中原
- 吉和田中原
- 田中原地蔵
- 田中原地蔵
- 熊崎
- 熊崎
- 駄荷
- 下石原
- 下石原
- 穴が迫
- 穴が迫
- 友和学校ロータリー
- 友和学校ロータリー
- 宮園二丁目
- 宮園二丁目
- 宮園八丁目
- 宮園八丁目
- 宮内河本
- 地御前三丁目
- ふじタウン中
- ふじタウン中
- ふじタウン南
- ふじタウン南
- 桜尾
- 桜尾
- 下大久保
- 下大久保
- 大久保
- 大久保
- 永原
- 永原
- 上永原
- 上永原
- 杉の森
- 杉の森
- 宮園西
- 宮園西
- 宮園上
- 宮園上
- 四季が丘一丁目
- 四季が丘一丁目
- 四季が丘中央
- 四季が丘中央
- 四季が丘南
- 四季が丘南
- 四季が丘
- 四季が丘
- 天神
- 小坂
- 小坂
- 上小坂
- 上小坂
- 正之原
- 正之原
- 上正之原
- 上正之原
- 楢原
- 楢原
- 玖島
- 玖島
- 泉水入口
- 泉水入口
- 玖島花咲く館
- 玖島花咲く館
- 四季が丘南口
- 四季が丘南口
- 廿日市
- 廿日市
- 榎浦橋
- 平良大橋
- 平良大橋
- 田尻
- 田尻
- 阿品台東小学校
- 阿品台東小学校
- 阿品台公園前
- 阿品台公園前
- 廿日市西高校前
- 廿日市西高校前
- 阿品台北中央
- 阿品台北中央
- 阿品台北
- 阿品台北
- ふじタウン北
- ふじタウン北
- 津田口
- 津田口
- ＪＲ阿品駅
- 日赤看護大学
- 新焼山橋
- 新焼山橋
- スポーツセンター
- スポーツセンター
- 廿日市市役所
- 廿日市市役所
- 廿日市市役所
- 廿日市市役所
- クヴェーレ吉和
- クヴェーレ吉和
- 特別支援学校入口
- 阿品台一丁目
- 阿品台一丁目
- 阿品台三丁目
- 阿品台三丁目
- 阿品台四丁目
- 阿品台四丁目
- 阿品台第六公園
- 阿品台第六公園
- ナタリーマリナタウン
- 広電阿品駅
- 宮内分れ
- 宮内分れ
- 宮内分れ
- 宮内分れ
- 一景苑
- 一景苑
- 陽光台中央
- 陽光台中央
- 陽光台中央
- JA広島総合病院
- JA広島総合病院
- 広電廿日市駅
- 大東住宅前
- 山陽女学園西
- 佐方保育園前
- 佐方下
- 佐方中
- 佐方
- 佐方上
- 月見台団地
- 緑ヶ丘団地口
- 屋代
- 緑ヶ丘入口
- 佐方四丁目東
- 佐方四丁目
- 山陽女学園北
- 山陽女学園前
- ＪＲ廿日市駅南口
- 地御前
- 地御前
- 野坂中学校南
- 野坂中学校南
- キラキラ公園
- キラキラ公園
- 野坂公園
- 野坂公園
- 六本松南
- 六本松南
- 六本松北
- 宮内一丁目
- 峰高一丁目
- 地御前神社
- 地御前神社
- ゆめタウン廿日市
- JR廿日市駅北口
- 市民活動センター
- 宮園上東
- 宮園上東
- and 79 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
13 findings, ordered by severity.
Show every finding
- Error3 instances
A file is missing a column that GTFS requires.
Apps may reject the whole file, so riders could lose the affected routes or stops.
Fix: Add the required column named in the finding to the flagged file. (Often an export setting; ask your vendor if it recurs.)
Finding code: missing_required_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5876 instances
Some rows in stop_times.txt leave the timepoint column blank.
That column says whether a time is a real checkpoint or an estimate. Blank leaves apps guessing, and they may show your estimates as promises.
Fix: Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1. (Usually one export setting.)
Finding code: missing_timepoint_value · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning329 instances
329 of 329 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 · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning219 instances
Some internal IDs use characters outside the basic text set.
These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.
Fix: Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language. (A planned ID change, not a quick text cleanup.)
Finding code: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning204 instances
204 of 204 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 · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning204 instances
204 of 204 trips have no headsign, the text that tells riders where the bus is going.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning8 instances
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.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning7 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.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info11 instances
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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info6 instances
Platform without parent station (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'platform_without_parent_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: platform_without_parent_station · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 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 · 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
Two requirements remain for this feed to earn 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 164 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.
Realtime reliability
The realtime feed responded on 100.0% of 8 checks over the last 1 day, with 22s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Clears the Google and Apple Maps four-week coverage bar. This feed has 164 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 3 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 54 / 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 37 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 100 / 100
- 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/hatsukaichi-city-bus/2026-09-05.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-09-05. 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.