Feed status · checked 2026-10-20
Shizuoka City Yui and Kanbara Hospital Line (静岡市由比・蒲原病院線)
Based on the official feed source on file
Service mode Bus
unchanged since 2026-10-19
Cataloged in Shizuoka, Japan.
Source feed: https://api.gtfs-data.jp/v2/organizations/shizuokacity/feeds/yui-kanbara/files/feed.zip?rid=current
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 45 days ago.
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
Shizuoka City Yui and Kanbara Hospital Line (静岡市由比・蒲原病院線)’s published feed lists 2 bus routes, 17 scheduled trips and 42 stops. Its service dates run from 2026-04-01 through 2027-06-30. The published file has not changed since our first check on 2026-09-05.
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
42 of 42 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 42 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
17 of 17 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 17 trips in the feed.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Give each route a distinct short or long name.
Two or more routes share the same name. Riders can't tell the routes apart in apps.
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.
⏱ One field per route.worth about +4 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.
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 253 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.
Score by category
The MobilityData validator flagged 2 kinds of issue across 2 instances (0 error, 1 warning, 1 informational).
Service data covers the next 253 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.
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 42 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)
| Route | Type | Line color |
|---|---|---|
| 由比蒲原病院線 | Bus | green |
| 由比蒲原病院線 | Bus | green |
List every stop
- 西神沢
- 西神沢
- 神沢
- 神沢
- 蒲原駅
- 中村
- 中村
- 小金
- 小金
- 蒲原体育館前
- 蒲原体育館前
- 砂防事務所入口
- 砂防事務所入口
- 蒲原本町
- 蒲原本町
- 新蒲原駅
- 新蒲原駅
- 軽金入口
- 軽金入口
- 由比駅
- 富士見橋
- 富士見橋
- 蒲原病院
- 新町
- 入山入口東
- 入山入口
- 由比川橋
- 由比北田
- 町屋原
- 西山入口
- 今宿東
- 今宿
- 今宿上
- 平
- 由比駅上
- 中央ガレージ前
- 由比むつみ市場前
- JAしみず由比支店前
- 由比川橋西
- 由比本陣公園前
- 由比自治会前
- 神沢川酒造場前
Over time
Overall score across the last 19 checks — unchanged since 2026-10-19.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-10-02 | 85.4 | first check |
| 2026-10-03 | 85.4 | no change |
| 2026-10-04 | 85.4 | no change |
| 2026-10-05 | 85.4 | no change |
| 2026-10-06 | 85.4 | no change |
| 2026-10-07 | 85.4 | no change |
| 2026-10-08 | 85.4 | no change |
| 2026-10-09 | 85.4 | no change |
| 2026-10-10 | 85.4 | no change |
| 2026-10-11 | 85.4 | no change |
| 2026-10-12 | 85.4 | no change |
| 2026-10-13 | 85.4 | no change |
| 2026-10-14 | 85.4 | no change |
| 2026-10-15 | 85.4 | no change |
| 2026-10-16 | 85.4 | no change |
| 2026-10-17 | 85.4 | no change |
| 2026-10-18 | 85.4 | no change |
| 2026-10-19 | 85.4 | no change |
| 2026-10-20 | 85.4 | 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.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-10-02 to 2026-10-20 (19 checks) | c9d588a371b2 | 2027-06-30 | Current rubric: see the trend above |
| 2026-09-05 to 2026-10-01 (23 checks) | c9d588a371b2 | 2027-06-30 | B, 85.4 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
What changed in this feed
Overall grade and score held steady since 2026-10-19.
Same feed file as 2026-10-19; 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
4 findings, ordered by severity.
Show every finding
- Warning42 instances
42 of 42 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)
- Warning17 instances
17 of 17 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)
- Warning1 instance
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.)
Finding code: duplicate_route_name · 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 253 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 253 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 96 / 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 Shizuoka
Other scorecards in Shizuoka, 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.
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/shizuoka-yui-kanbara-hospital-line/2026-10-20.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-20. 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.