Feed status · checked 2026-10-15
Kurobe City Bus (黒部市 新幹線生地・石田三日市・愛本・電動ミニバス)
Based on the official feed source on file
Service mode Bus
unchanged since 2026-10-14
Cataloged in Toyama, 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.4, validator 8.0.1.
Checked for changes 3 hours ago; last changed 84 days 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 6 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.
About this feed
Kurobe City Bus (黒部市 新幹線生地・石田三日市・愛本・電動ミニバス)’s published feed lists 5 bus routes, 59 scheduled trips and 112 stops. Its service dates run from 2026-04-01 through 2027-03-31. It publishes realtime trip updates and vehicle positions; when we checked, all of them answered. The published file has not changed since our first check on 2026-07-23.
Top things to fix
Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Foreign key violation (flagged by the MobilityData validator). See the linked rule for what this affects.
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.
⏱ Varies.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
112 of 112 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 112 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
59 of 59 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 59 trips in the feed.
⏱ A default or per-trip field in your export.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.
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_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 03 · 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.
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 167 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 8 kinds of issue across 1350 instances (2 error, 1346 warning, 2 informational).
Service data covers the next 167 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 6 times outside service hours: 2 of 2 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 112 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.
- 愛本本線 (purple)
- 栃屋大橋循環線 (green)
- 新幹線生地線 (green)
- 石田三日市線 (pink)
- 電動ミニバス (yellow)
| Route | Type | Line color |
|---|---|---|
| 愛本本線 | Bus | purple |
| 栃屋大橋循環線 | Bus | green |
| 新幹線生地線 | Bus | green |
| 石田三日市線 | Bus | pink |
| 電動ミニバス | Bus | yellow |
List every stop
- 生地駅
- 魚の駅「生地」
- YKKセンターパーク
- 愛本新上区公民館
- YKK黒部古御堂工場
- YKK黒部栃沢工場
- 古御堂
- 北野
- 沓掛
- 西小路北
- 沖
- YKK AP黒部荻生製造所
- 沓掛東
- 池田リハビリテーション病院
- 千光寺前
- 東栄土木前
- Ｉ－ＴＯＷＮ
- Ｉ－ＴＯＷＮ
- YKKAP30ビル
- YKK体育館
- 愛本新中区公民館
- あおーよ
- 黒部自動車学校
- プラント
- 道の駅KOKOくろべ
- 堀切市営住宅
- 町堀切
- 岡団地
- 石田交流プラザ
- 浦野バス停
- はまなす児童公園
- 三島公民館
- 黒部市役所
- 愛本新下区公民館
- 東三日市駅口
- 東三日市
- 北新
- パッシブタウン
- 椚町西
- 椚町東
- 東部児童センター
- 東三日市駅
- 大黒町公民館
- 此川運輸前
- 下立まちおこしセンター
- 東屋前
- 下立第五区集会所
- 愛本駅
- ぷらっと
- 石坂医院
- 熊野交差点
- 浦山分団屯所前
- 市営住宅
- イラッセ
- 大阪屋ショップ
- 下村公民館
- ポンプ格納庫前
- 防火水槽前
- 宇奈月サービスセンター
- 大橋公民館
- 両瀬公民館
- 中坪公民館
- 八社公民館
- 若埜ふれあいセンター前
- 東町
- 越野公民館
- 袖野
- 西町
- 前田歯科クリニック
- 愛本姫社
- 地産の黒部
- グリーンタウン
- 古川接骨院
- 中村公民館
- 若栗団地交差点
- 浦川端
- 上浦川端
- 栃屋駅
- ちどりのき台
- 桧葉ノ木川交差点
- 愛本橋
- 十三区
- 十二区公民館
- 熊野ポンプ格納庫前
- 熊野
- 荒町
- 荒町西
- 犬山東
- 犬山団地
- 中ノ口公民館口
- 電鉄石田駅前
- 浜石田東
- 下坂商店
- さくら団地
- 海水浴場口
- 新町中央
- 浜石田西
- にいかわ総合支援学校
- アルファ塾石田校前
- 立野公民館
- 立野
- JAくろべ本店口
- 黒部市役所前
- 天神新公民館口
- 法福寺前
- 黒部駅前
- 市民病院
- 黒部宇奈月温泉駅
- メルシー
- メルシー
- 明日コミニケ口
- 旧JA愛本支所
Over time
Overall score across the last 14 checks — unchanged since 2026-10-14.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-10-02 | 72.9 | first check |
| 2026-10-03 | 64.5 | down 8.4 |
| 2026-10-04 | 64.5 | no change |
| 2026-10-05 | 72.9 | up 8.4 |
| 2026-10-06 | 72.9 | no change |
| 2026-10-07 | 72.9 | no change |
| 2026-10-08 | 72.9 | no change |
| 2026-10-09 | 72.9 | no change |
| 2026-10-10 | 72.9 | no change |
| 2026-10-11 | 72.9 | no change |
| 2026-10-12 | 72.9 | no change |
| 2026-10-13 | 72.9 | no change |
| 2026-10-14 | 72.9 | no change |
| 2026-10-15 | 72.9 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality 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-15 (14 checks) | 4f55eddf3d45 | 2027-03-31 | Current rubric: see the trend above |
| 2026-07-25 to 2026-10-01 (65 checks) | 4f55eddf3d45 | 2027-03-31 | C, 72.9 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-23 to 2026-07-24 (2 checks) | 4f55eddf3d45 | 2027-03-31 | D, 69.4 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
What changed over time
On 2026-10-02 this feed started at grade C. On 2026-10-03 the grade moved from C to D. On 2026-10-05 the grade moved from D to C. As of 2026-10-15 it holds grade C.
A plain-language history of this feed, newest first.
- 2026-10-05 Grade went D to C, realtime rose 42 points.
- 2026-10-03 Grade went C to D, realtime fell 42 points.
Everything we checked
12 findings, ordered by severity.
Show every finding
- Error2 instances
Foreign key violation (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: foreign_key_violation · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1326 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)
- Warning112 instances
112 of 112 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)
- Warning59 instances
59 of 59 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)
- Warning15 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)
- Warning2 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · Read the fix guide for missing_recommended_field · 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 for missing_feed_contact_email_and_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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 for stop_too_far_from_shape · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info11 instances
About 11 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide for scorecard_stop_names_all_caps · See GTFS Best Practices (opens GTFS Best Practices 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
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
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 167 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 200 checks in the 25 days to 2026-10-15, with 15s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment. The window ends at the newest observation, which is not always today: if the monitor stops, this window stops with it.
Clears the Google and Apple Maps four-week coverage bar. This feed has 166 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 2 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 58 / 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 51 / 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.
Part of the Japan portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in Toyama
Other scorecards in Toyama, 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/kurobe-city-bus/2026-10-15.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-15. 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.