Feed status · checked 2026-08-01
北名古屋市 市内循環バス「きたバス」
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
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 11 hours ago; last changed 5 days ago.
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
145 of 145 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
67 of 67 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
- 145 of 145 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
- 67 of 67 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 242 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 1179 instances (0 error, 1177 warning, 2 informational).
Service data covers the next 242 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
8 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (きたバス 朝・夕便 ① ピンクライン, きたバス 朝・夕便 ② グリーンライン, きたバス 朝・夕便 ③ イエローライン, きたバス 朝・夕便 ④ オレンジライン, きたバス 昼便 ⑥ もも線, 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.
This feed has 145 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.
- きたバス 朝・夕便 ① ピンクライン (pink)
- きたバス 昼便 ⑩ ふじ線 (purple)
- きたバス 朝・夕便 ② グリーンライン (green)
- きたバス 朝・夕便 ③ イエローライン (yellow)
- きたバス 朝・夕便 ④ オレンジライン (orange)
- きたバス 朝・夕便 ⑤ パープルライン (purple)
- きたバス 昼便 ⑥ もも線 (pink)
- きたバス 昼便 ⑦ わかば線 (green)
- きたバス 昼便 ⑧ やまぶき線 (yellow)
- きたバス 昼便 ⑨ だいだい線 (orange)
| Route | Type | Line color |
|---|---|---|
| きたバス 朝・夕便 ① ピンクライン | Bus | pink |
| きたバス 昼便 ⑩ ふじ線 | Bus | purple |
| きたバス 朝・夕便 ② グリーンライン | Bus | green |
| きたバス 朝・夕便 ③ イエローライン | Bus | yellow |
| きたバス 朝・夕便 ④ オレンジライン | Bus | orange |
| きたバス 朝・夕便 ⑤ パープルライン | Bus | purple |
| きたバス 昼便 ⑥ もも線 | Bus | pink |
| きたバス 昼便 ⑦ わかば線 | Bus | green |
| きたバス 昼便 ⑧ やまぶき線 | Bus | yellow |
| きたバス 昼便 ⑨ だいだい線 | Bus | orange |
List every stop
- 西春駅東口
- 西春駅東口
- 西春駅東口
- 済衆館病院
- 済衆館病院
- 片場天王森西
- 片場天王森西
- 高田寺出口
- 高田寺出口
- 久地野北浦
- 久地野北浦
- 二子屋敷
- 二子屋敷
- シンコースポーツアクアプラザ
- 上小田井駅北
- 三洋機工入口
- 三洋機工入口
- 沖村保育園
- 沖村保育園
- 市役所東庁舎
- 市役所東庁舎
- 六ツ師宮西
- 六ツ師宮西
- 六ツ師松葉
- 六ツ師松葉
- コッツ山公園
- コッツ山公園
- 六ツ師道毛
- 六ツ師道毛
- 植物工場つくらぼ前
- 植物工場つくらぼ前
- 熊之庄小烏
- 熊之庄小烏
- 熊之庄小烏北
- 熊之庄小烏北
- 薬師寺公民館
- 薬師寺公民館
- レモン橋
- レモン橋
- 総合福祉センターもえの丘
- 総合福祉センターもえの丘
- 西春駅西口
- 西春駅西口
- 沖村沖浦
- 沖村沖浦
- 北野八竜前
- 北野八竜前
- 北野天神
- 北野天神
- 宇福寺村上
- 宇福寺村上
- 中之郷諏訪児童遊園
- 中之郷出荷場
- カサイ製作所前
- カサイ製作所前
- 弥勒寺保育園
- 弥勒寺保育園
- 名古屋芸術大学アートスクエア
- 名古屋芸術大学アートスクエア
- 法成寺公会堂
- 法成寺公会堂
- 県営西春住宅
- 県営西春住宅
- 鍜治ケ一色東一丁目
- 鍜治ケ一色東一丁目
- 鍜治ケ一色西一丁目
- 鍜治ケ一色西一丁目
- 山之腰五条
- 山之腰五条
- 名工銘鈑前
- 名工銘鈑前
- フジパン西春工場前
- フジパン西春工場前
- 西部北地域包括支援センター
- 西部北地域包括支援センター
- 健康ドーム
- 鹿田南蒲屋敷
- 鹿田南蒲屋敷
- 市役所東庁舎西
- 市役所東庁舎西
- 明工舎製作所南
- 明工舎製作所南
- あいせの里
- あいせの里
- 六ツ師町田
- 六ツ師町田
- 六ツ師女夫越
- 六ツ師女夫越
- 六ツ師女夫越北
- 六ツ師女夫越北
- ヨシヅヤ師勝店
- ヨシヅヤ師勝店
- 名古屋銀行師勝支店
- 名古屋銀行師勝支店
- カネスエ西春店
- カネスエ西春店
- 石橋大日
- 宇福寺東出
- 宇福寺東出
- せきや歯科クリニック前
- せきや歯科クリニック前
- ピアゴ西春店
- ピアゴ西春店
- 陽だまりハウス
- 陽だまりハウス
- にしはるひまわり作業所
- にしはるひまわり作業所
- 名古屋芸術大学西キャンパス
- 名古屋芸術大学西キャンパス
- 徳重杁ノ口
- 徳重杁ノ口
- 徳重・名古屋芸大駅
- 徳重・名古屋芸大駅
- 名古屋芸術大学東キャンパス
- 名古屋芸術大学東キャンパス
- ネオポリス集会所
- ネオポリス集会所
- 高田寺東の川
- 高田寺東の川
- ナフコ師勝店
- ナフコ師勝店
- 六ツ師南屋敷
- 六ツ師南屋敷
- ＪＡ西春日井師勝支店
- ＪＡ西春日井師勝支店
- ハナノキ精米工場北
- ハナノキ精米工場北
- 光寿会リハビリテーション病院
- 加島新田北浦
- 加島新田北浦
- はるひ呼吸器病院
- 豊山町青山高添
- 豊山町青山高添
- 熊之庄城ノ屋敷
- 熊之庄城ノ屋敷
- 市役所西庁舎
- 市役所西庁舎
- 中之郷南
- 片場大石
- 片場大石
- 沖村東ノ郷
- 沖村東ノ郷
- 九之坪菰口
- 九之坪菰口
- ドン・キホーテ楽市街道名古屋店
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 75.2 | first check |
| 2026-07-30 | 73.5 | down 1.7 |
| 2026-07-31 | 73.5 | no change |
| 2026-08-01 | 73.5 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
9 findings, ordered by severity.
Show every finding
- Warning1161 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)
- Warning145 instances
145 of 145 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)
- Warning67 instances
67 of 67 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)
- Warning13 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)
- Warning1 instance
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · 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
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
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
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 242 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 241 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 74 / 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/kitanagoyacity-communitybus/2026-08-01.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-08-01. 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.