Feed status · checked 2026-09-05
Nishio City Rokumangoku Kururin Bus (西尾市六万石くるりんバス)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Aichi, 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 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.
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
227 of 227 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
77 of 77 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
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
- 227 of 227 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
- 77 of 77 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
- Feed evidence
- Some internal IDs use characters outside the basic text set.
- Next action
- 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.
- 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.
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 207 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 6 kinds of issue across 2429 instances (0 error, 2426 warning, 3 informational).
Service data covers the next 207 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
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (六万石くるりんバス 0市街地線).
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.
This feed has 227 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.
- 六万石くるりんバス 0市街地線 (red)
- 六万石くるりんバス 1三和線 (yellow)
- 六万石くるりんバス 2室場線 (pink)
- 六万石くるりんバス 3平坂中畑線 (brown)
- 六万石くるりんバス 4寺津矢田線 (gray)
- 六万石くるりんバス 5米津線 (green)
- 六万石くるりんバス 6西野町線 (blue)
- 六万石くるりんバス 7福地線 (purple)
| Route | Type | Line color |
|---|---|---|
| 六万石くるりんバス 0市街地線 | Bus | red |
| 六万石くるりんバス 1三和線 | Bus | yellow |
| 六万石くるりんバス 2室場線 | Bus | pink |
| 六万石くるりんバス 3平坂中畑線 | Bus | brown |
| 六万石くるりんバス 4寺津矢田線 | Bus | gray |
| 六万石くるりんバス 5米津線 | Bus | green |
| 六万石くるりんバス 6西野町線 | Bus | blue |
| 六万石くるりんバス 7福地線 | Bus | purple |
List every stop
- 中畑東
- 中畑
- 中畑橋
- 中畑西
- 中畑鵜ノ首
- 奥背戸
- 平坂北町
- 平坂小西
- 平坂西口
- 平坂午築地
- 文化会館
- 文化会館
- 平坂港前
- 平坂熊野後
- 羽塚西
- 羽塚口
- 羽塚
- 経塚
- 山下
- 住崎北
- 住崎北
- 下町住宅東
- 下町住宅東
- 住崎南
- 住崎南
- 歴史公園西
- 歴史公園西
- 新在家
- 新在家
- 矢田小南
- 矢田小南
- 上矢田北
- 富山北
- 上矢田南
- 下矢田
- 徳永東
- 田地山住宅
- 東脇
- 巨海住宅
- 上町東
- 上町東
- 刈宿
- 巨海
- 寺津本町
- 寺津神社前
- 寺津ふれあいセンター西
- 寺津保育園前
- 北寺津
- 寺津二ツ家
- 寺津二丁目
- 道光寺
- 道光寺
- 鶴城会館
- 鶴城会館
- 戸ケ崎
- 戸ケ崎
- 桜町前駅南
- 桜町前駅南
- 新渡場
- 五郎田
- 八百目
- 南中根北
- 南中根
- 宮浦
- 米津小南
- 中央通り
- 中央通り
- 図書館・岩瀬文庫西
- 図書館・岩瀬文庫西
- 中央児童館
- 中央児童館
- 神明下
- 神明下
- 堀ノ内
- 堀ノ内
- 上町住宅
- 上町住宅
- 横町屋敷
- 横町屋敷
- 西野町ふれあいセンター
- 紅樹院
- 碧南鷲塚
- 今川下落
- 今川下落
- 鵜ケ池北
- 鵜ケ池北
- 鶴城中西
- 鶴城中西
- 鎌谷
- 天竹
- 横手
- 平口
- 笹曽根
- 市子
- 八ケ尻
- 行用
- 針曽根
- 下道目記
- 鶴城小南
- 鶴城小南
- 上道目記
- 福地中北
- 緑町
- 米津ふれあいセンター東
- 西尾駅
- 米津駅
- 桜町
- 桜町
- 桜町前駅西
- 桜町前駅西
- 八ツ面ふれあいセンター
- 八ツ面ふれあいセンター
- 八ツ面小西
- 八ツ面小西
- 市民病院
- 熊味
- 熊味
- 保健センター
- 保健センター
- 保健センター南
- 保健センター南
- 法務局西尾支局南
- 法務局西尾支局南
- 市役所
- 郵便局西
- 郵便局西
- 保健所西
- 保健所西
- 福祉センター
- 福祉センター
- 西尾口駅
- 西尾口駅
- 八ツ面
- 八ツ面住宅南
- 八ツ面住宅南
- 道の駅にしお岡ノ山
- 江原
- 三和ふれあいセンター西
- 花ノ木保育園東
- 花ノ木保育園東
- 尾花
- 東部中
- 下永良
- つくしが丘
- 駒場北
- 駒場北
- 家武
- 家武
- 室場ふれあいセンター
- 室場ふれあいセンター
- ホワイトウェイブ
- ホワイトウェイブ
- 宅野島
- 宅野島
- 今川北
- 今川北
- 小焼野
- 中央体育館
- 中央体育館
- 丁田
- 市役所西
- 市役所西
- 今川西
- 今川西
- 今川
- 今川
- 福北小北
- 福北小北
- 鵜ケ池
- 十郎島
- 憩の農園
- 今川南
- 今川南
- 斉藤
- 福地駅南
- 若王子
- 富山
- 富山
- 矢田小東
- 矢田小東
- 国森
- 消防本部南
- 消防本部南
- 勤労会館
- 中畑保育園
- 中畑小東
- 田貫
- 下町
- 下町住宅
- 御城下
- 御城下
- 歴史公園北
- 歴史公園北
- 四條橋
- 四條橋
- 矢曽根西
- 矢曽根西
- 鶴城ふれあいセンター
- 江原東
- 江原東
- 岡島
- 岡島
- 駒場
- 駒場
- 米野橋
- 西浅井南
- 西浅井
- 高落
- 高落北
- 新村
- 永吉南
- 永吉南
- 東浅井
- 東浅井
- 岡崎中島
- 黄金堤
- 黄金堤
- 家武東
- 平原
- 西尾本町
- 西尾本町
- 法光寺
- 法光寺工業団地前
- 中畑小南
- 中畑小北
- 住崎
- 住崎
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
9 findings, ordered by severity.
Show every finding
- Warning2414 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)
- Warning227 instances
227 of 227 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)
- Warning77 instances
77 of 77 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)
- Warning10 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)
- Warning1 instance
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 · 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
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)
- 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
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 207 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 207 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 77 / 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 52 / 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/nishio-rokumangoku-kururin-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.