← All agencies

Feed status · checked 2026-10-17

Himeji City Island Community Buses (姫路市家島・坊勢・雪彦コミュニティバス)

Based on the feed source on file; publisher ownership is not verified

Service mode Bus

FDCBA

81.7 / 100

unchanged since 2026-10-16

Cataloged in Hyogo, Japan.

Covers 348 daysAccessibility gapsRealtime not yet published

Source feed: https://api.gtfs-data.jp/v2/organizations/himejicity/feeds/ieshima-boze-yukihiko/files/feed.zip?rid=current

Himeji's Ieshima and Boze island community buses and the Yukihiko route.

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.

Checked for changes 31 minutes ago; last changed 17 days ago.

Measured 3 of 4 score categories from the feed URL on file (publisher not verified).

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 configured feed URL. Publisher ownership of that URL is not verified.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

About this feed

Himeji City Island Community Buses (姫路市家島・坊勢・雪彦コミュニティバス)’s published feed lists 5 bus routes, 74 scheduled trips and 110 stops. Its service dates run from 2026-10-01 through 2027-09-30. The published file last changed on 2026-09-30.

Top things to fix

Fix 01

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

110 of 110 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 110 stops in the feed.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category

Fix 02

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

74 of 74 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 74 trips in the feed.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Fix 03

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.

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.

This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

⏱ A planned ID change, not a quick text cleanup.worth about +8 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

Agency: Himeji City Island Community Buses (姫路市 家島・坊勢・雪彦コミュニティバス)
Finding: scorecard_wheelchair_boarding_unknown
Feed evidence: 110 of 110 stops don't say whether a wheelchair user can board there.
Why it matters: Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Requested change: 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.
Evidence: https://gtfsscorecard.org/agency/himeji-island-community-bus/?finding=scorecard_wheelchair_boarding_unknown#finding-handoff

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. See this feed's finding-clearance log.
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. See this feed's finding-clearance log.
Fix 03
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. See this feed's finding-clearance log.

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 348 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: 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.

Hi,

Our GTFS feed (Himeji City Island Community Buses (姫路市 家島・坊勢・雪彦コミュニティバス)) scored B (81.7 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
   What: 110 of 110 stops don't say whether a wheelchair user can board there.
   Finding code: scorecard_wheelchair_boarding_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_boarding_unknown/

2. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
   What: 74 of 74 trips don't say whether the vehicle is wheelchair accessible.
   Finding code: scorecard_wheelchair_accessible_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_accessible_unknown/

3. 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.
   What: Some internal IDs use characters outside the basic text set.
   Finding code: non_ascii_or_non_printable_char

Full scorecard: https://gtfsscorecard.org/agency/himeji-island-community-bus/

Score by category

Correctness87.0 / 100

The MobilityData validator flagged 4 kinds of issue across 1451 instances (0 error, 1448 warning, 3 informational).

Freshness100.0 / 100

Service data covers the next 348 days.

Rider experience59.6 / 100

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.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

FaresLegacy fares

Fares are applied to trips.

Realtime qualityNot yet measured

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 110 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)

Routes in Himeji City Island Community Buses (姫路市家島・坊勢・雪彦コミュニティバス)'s feed
Route	Type	Line color
コミュニティバス雪彦	Bus	green
家島コミュニティバス（宮ルート）	Bus	green
家島コミュニティバス（真浦ルート）	Bus	green
坊勢コミュニティバス	Bus	green
コミュニティバス溝口お買い物便	Bus	green

List every stop

真浦クリニック前
真浦クリニック前
真浦公園
網場南
網場
網場
右ノ浦
右ノ浦
福島写真場前
福島写真場前
奥の町
奥の町
熊本マンション前
熊本マンション前
Ｂ＆Ｇ海洋センター下
Ｂ＆Ｇ海洋センター下
宮港
旅客船ターミナル
恵美酒神社南
恵美酒神社南
奈座
奈座
坊崎南西
坊崎南西
漁協前
漁協前
サービスセンター前
サービスセンター前
スポーツセンター前
スポーツセンター前
西ノ浦
西ノ浦
老人の家前
老人の家前
カズラ
カズラ
宮神社前
宮神社前
ちびっこ公園
ちびっこ公園
ぼうぜ医院前
ぼうぜ医院前
鷹ノ浦
鷹ノ浦
炭焼
佐中
我孫子
我孫子
寺河内
寺河内
山之内
山之内
中山之内
中山之内
山之内南口
山之内南口
三軒家
三軒家
附出
附出
河原口
河原口
勇繁
勇繁
木戸
木戸
上新庄
上新庄
中林口
中林口
下新庄
下新庄
諏訪
諏訪
運動広場
前之庄
赤坂
松ノ本北
松ノ本北
松ノ本
松ノ本
松ノ本南
松ノ本南
みどり丘公園
久畑
久畑
中村公民館
中村公民館
北恒屋公民館
北恒屋公民館
南恒屋公民館
南恒屋公民館
マックスバリュ溝口店
マックスバリュ溝口店
JR溝口駅前
破風
破風
網手港
芝生公園
芝生公園
日和山
みどり丘公民館
みどり丘南
堂崎
堂崎
中学校前
診療所前
診療所前
家島事務所前
家島事務所前

Over time

Overall score across the last 16 checks — unchanged since 2026-10-16.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-10-02	81.7	first check
2026-10-03	81.7	no change
2026-10-04	81.7	no change
2026-10-05	81.7	no change
2026-10-06	81.7	no change
2026-10-07	81.7	no change
2026-10-08	81.7	no change
2026-10-09	81.7	no change
2026-10-10	81.7	no change
2026-10-11	81.7	no change
2026-10-12	81.7	no change
2026-10-13	81.7	no change
2026-10-14	81.7	no change
2026-10-15	81.7	no change
2026-10-16	81.7	no change
2026-10-17	81.7	no change

What changed since your last check

Correctness no change
Freshness no change
Rider experience no change

Feed history

Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.

Feed history by published file
Checked	Published file	Service dates through	Grade at the time
2026-10-02 to 2026-10-17 (16 checks)	`5b297a0a7e66`	2027-09-30	Current rubric: see the trend above
2026-09-30 to 2026-10-01 (2 checks)	`5b297a0a7e66`	2027-09-30	B, 81.7 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-08-19 to 2026-09-29 (38 checks)	`8148bcfeac89`	2027-03-31	B, 81.9 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-25 to 2026-08-18 (25 checks)	`5421e6a9e7c7`	2027-03-31	B, 81.9 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-19 to 2026-07-24 (4 checks)	`5421e6a9e7c7`	2027-03-31	B, 81.9 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade

What changed in this feed

Overall grade and score held steady since 2026-10-16.

Same feed file as 2026-10-16; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.

Everything we checked

6 findings, ordered by severity.

Show every finding

Warning1446 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)
Warning110 instances
110 of 110 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)
Warning74 instances
74 of 74 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)
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.)
Finding code: mixed_case_recommended_field · Read the fix guide for mixed_case_recommended_field · 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 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)

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 348 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 348 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 87 / 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 60 / 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 Japan portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Hyogo

Other scorecards in Hyogo, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

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.

Badge HTML

<a href="https://gtfsscorecard.org/agency/himeji-island-community-bus/"><img src="https://gtfsscorecard.org/agency/himeji-island-community-bus/badge.svg" width="320" height="58" alt="Himeji City Island Community Buses (姫路市 家島・坊勢・雪彦コミュニティバス): current GTFS data quality score from GTFS Scorecard"></a>

Badge Markdown

[![Himeji City Island Community Buses (姫路市 家島・坊勢・雪彦コミュニティバス): current GTFS data quality score from GTFS Scorecard](https://gtfsscorecard.org/agency/himeji-island-community-bus/badge.svg)](https://gtfsscorecard.org/agency/himeji-island-community-bus/)

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/himeji-island-community-bus/2026-10-17.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-17. 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.

GTFS Scorecard. (2026). Himeji City Island Community Buses (姫路市 家島・坊勢・雪彦コミュニティバス) GTFS feed-quality record, dated 2026-10-17 (grade B (81.7/100), rubric v1.4, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 5b297a0a7e66…). https://gtfsscorecard.org/data/artifacts/himeji-island-community-bus/2026-10-17.json

@misc{gtfsscorecard-himeji-island-community-bus-2026-10-17,
  title        = {Himeji City Island Community Buses (姫路市 家島・坊勢・雪彦コミュニティバス) GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/himeji-island-community-bus/2026-10-17.json}},
  note         = {Checked 2026-10-17; rubric v1.4; gtfs-validator 8.0.1; reader archive profile raw-v1; grade B (81.7/100)}
}

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.

Himeji City Island Community Buses (姫路市 家島・坊勢・雪彦コミュニティバス)