Feed status · checked 2026-07-19
Itoigawa Bus (糸魚川バス)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
Catalogued in Niigata, 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.2, 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
588 of 588 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
294 of 294 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
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.
⏱ A planned ID change, not a quick text cleanup.worth about +8 points in its category
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.
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.
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.
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 255 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 32353 instances (0 error, 32353 warning, 0 informational).
Service data covers the next 255 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.
1 accessibility depth signal
9 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (01 青海糸魚川線, 03 青海通り線, 11 中尾長者温泉線, 13 能生線（西廻り）, 15 仙納線, 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.
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.
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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 02 おうみ巡回線 (purple)
- 08 中央大通り線 (brown)
- 11 中尾長者温泉線 (orange)
- 04 今井線 (gray)
- 15 仙納線 (orange)
- 14 島道線 (purple)
- 09 市街地巡回線 (red)
- 07 早川線 (teal)
- 05 根知線 (purple)
- 18 白馬岳登山バス（蓮華線） (yellow)
- 10 美山公園・博物館線 (teal)
- 12 能生糸魚川線 (red)
- 13 能生線（西廻り） (green)
- 06 西海線 (teal)
- 01 青海糸魚川線 (pink)
- 03 青海通り線 (teal)
| Route | Type | Line color |
|---|---|---|
| 02 おうみ巡回線 | Bus | purple |
| 08 中央大通り線 | Bus | brown |
| 11 中尾長者温泉線 | Bus | orange |
| 04 今井線 | Bus | gray |
| 15 仙納線 | Bus | orange |
| 14 島道線 | Bus | purple |
| 09 市街地巡回線 | Bus | red |
| 07 早川線 | Bus | teal |
| 05 根知線 | Bus | purple |
| 18 白馬岳登山バス（蓮華線） | Bus | yellow |
| 10 美山公園・博物館線 | Bus | teal |
| 12 能生糸魚川線 | Bus | red |
| 13 能生線（西廻り） | Bus | green |
| 06 西海線 | Bus | teal |
| 01 青海糸魚川線 | Bus | pink |
| 03 青海通り線 | Bus | teal |
This feed has 588 stops.
List every stop
- 大沢
- 石曾根
- 石曾根
- 電化口
- 電化口
- 北斗町
- 北斗町
- 青海港町
- 青海港町
- 青海駅入口
- 青海駅入口
- きらら青海入口
- きらら青海入口
- 名引西
- 名引西
- 新名引
- 新名引
- 新寺地
- 新寺地
- 新中島
- 新中島
- 新田海
- 新田海
- 田海東
- 田海東
- 田沢小学校前
- 田沢小学校前
- 新須沢
- 新須沢
- 須沢南
- 須沢南
- 新姫川橋
- 新姫川橋
- 姫川橋詰
- 姫川橋詰
- 寺島西
- 寺島西
- 新寺島
- 新寺島
- 横町五丁目
- 横町五丁目
- ハローワーク前
- ハローワーク前
- 横町一丁目
- 横町一丁目
- 四ツ角
- 四ツ角
- 四ツ角
- 四ツ角
- 本町十字路
- 本町十字路
- 糸魚川駅日本海口
- 正覚寺前
- 正覚寺前
- 寺町一丁目
- 寺町一丁目
- 寺町一丁目
- 寺町一丁目
- 寺町二丁目
- 寺町二丁目
- 寺町三丁目
- 寺町三丁目
- 寺町四丁目
- 寺町四丁目
- 寺町五丁目
- 寺町五丁目
- 押上一丁目
- 押上一丁目
- 南押上
- 南押上
- 糸魚川地域振興局前
- 糸魚川地域振興局前
- 下平牛
- 下平牛
- 糸魚川高校入口
- 糸魚川高校入口
- 糸魚川高校入口
- 厚田入口
- 厚田入口
- 押上二丁目
- 押上二丁目
- 竹ヶ花
- 竹ヶ花
- 糸魚川総合病院
- 糸魚川総合病院
- 前川
- 前川
- 大和川
- 大和川
- 大和川小学校前
- 大和川小学校前
- 田伏
- 田伏
- 梶屋敷駅前
- 梶屋敷駅前
- 梶屋敷四ツ角
- 梶屋敷四ツ角
- あらたはま西
- あらたはま西
- あらたはま
- あらたはま
- 中宿
- 中宿
- 西中浜
- 西中浜
- 中浜
- 中浜
- 間脇
- 間脇
- 浦本駅前
- 浦本駅前
- 崩山
- 崩山
- 鬼伏
- 鬼伏
- 鬼舞
- 鬼舞
- 木浦
- 木浦
- 木浦東
- 木浦東
- 大平寺入口
- 大平寺入口
- 能生案内所
- 能生案内所
- 栄町
- 栄町
- 桜木
- 桜木
- 能生駅前
- 能生駅前
- きらら青海
- 本町一丁目
- 本町一丁目
- 青海駅
- 青海事務所前
- 青海事務所前
- 名引支館前
- 名引支館前
- 名引東
- 名引東
- 寺地坂上
- 寺地坂上
- 田海川西
- 田海川西
- 田海川東
- 田海川東
- 青海中学校前
- 青海中学校前
- 至誠会・ふくがくちの里前
- 至誠会・ふくがくちの里前
- 横地
- 横地
- 高畑支館前
- 高畑支館前
- 高畑
- 高畑
- 横マクリ
- 横マクリ
- 総合福祉会館ふれあい
- 須沢東
- 須沢東
- 八千川橋
- 八千川橋
- 姫川港入口
- 姫川港入口
- 健康づくりセンターはぴねす
- 健康づくりセンターはぴねす
- 須沢臨海公園入口
- 須沢臨海公園入口
- 須沢児童遊園前
- 須沢児童遊園前
- 青海寺町
- 青海寺町
- 青海小学校前
- 青海小学校前
- 名引
- 名引
- 深田
- 深田
- 寺地
- 寺地
- 青海中学校入口
- 青海中学校入口
- 山添社公園前
- 山添社公園前
- 田海
- 田海
- 健康センター前
- 健康センター前
- 今村新田入口
- 今村新田入口
- ほっこり館前
- ほっこり館前
- 中谷内
- 糸魚川高等職業訓練校前
- 糸魚川高等職業訓練校前
- 西中
- 西中
- 梶屋
- 梶屋
- 梶屋北
- 梶屋北
- 頭山
- 頭山
- 八千川地内※自由乗降区間
- 八千川地内※自由乗降区間
- 別所
- 山寺上入口
- 山寺上入口
- 山口
- 山口
- シーサイドバレースキー場前
- シーサイドバレースキー場前
- 大神堂入口
- 大神堂入口
- 上町屋
- 上町屋
- 上町屋下
- 上町屋下
- 根知地区公民館前
- 根知地区公民館前
- 和泉
- 井口上
- 井口上
- 井口
- 井口
- 上野
- 上野
- 下沢
- 下沢
- 山崎
- 山崎
- 東中
- 東中
- 東橋西
- 東橋西
- 栗山
- 栗山
- 仁王堂
- 仁王堂
- 中村入口
- 中村入口
- 古町
- 古町
- 仁王堂入口
- 仁王堂入口
- 根小屋
- 根小屋
- 根知駅前
- and 338 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 2 checks — unchanged since 2026-07-18.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-18 | 80.5 | first check |
| 2026-07-19 | 80.5 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-18.
Same feed file as 2026-07-18; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
4 findings, ordered by severity.
Show every finding
- Warning32204 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.)
Validator rule: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning588 instances
588 of 588 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)
- Warning294 instances
294 of 294 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)
- Warning149 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)
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 255 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 255 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 84 / 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.
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/itoigawa-bus/2026-07-19.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-07-19. 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.