Feed status · checked 2026-07-23
北名古屋市 市内循環バス「きたバス」
Based on the feed this agency publishes
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.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
197 of 197 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
79 of 79 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 161 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 5 kinds of issue across 1669 instances (0 error, 1667 warning, 2 informational).
Service data covers the next 161 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
7 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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- きたバス 朝・夕便 ①もえの丘線 (teal)
- きたバス 昼便 ⑩つつじ（南部）線 (purple)
- きたバス 朝・夕便 ②鍜治ケ一色線 (teal)
- きたバス 朝・夕便 ③中之郷線 (yellow)
- きたバス 朝・夕便 ④六ツ師道毛線 (pink)
- きたバス 朝・夕便 ⑤片場・沖村線 (purple)
- きたバス 昼便 ⑥さくら（北部）線 (pink)
- きたバス 昼便 ⑦はなみずき（西部）線 (green)
- きたバス 昼便 ⑧かえで（中部）線 (orange)
- きたバス 昼便 ⑨けやき（東部）線 (brown)
| Route | Type | Line color |
|---|---|---|
| きたバス 朝・夕便 ①もえの丘線 | Bus | teal |
| きたバス 昼便 ⑩つつじ（南部）線 | Bus | purple |
| きたバス 朝・夕便 ②鍜治ケ一色線 | Bus | teal |
| きたバス 朝・夕便 ③中之郷線 | Bus | yellow |
| きたバス 朝・夕便 ④六ツ師道毛線 | Bus | pink |
| きたバス 朝・夕便 ⑤片場・沖村線 | Bus | purple |
| きたバス 昼便 ⑥さくら（北部）線 | Bus | pink |
| きたバス 昼便 ⑦はなみずき（西部）線 | Bus | green |
| きたバス 昼便 ⑧かえで（中部）線 | Bus | orange |
| きたバス 昼便 ⑨けやき（東部）線 | Bus | brown |
This feed has 197 stops.
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
8 findings, ordered by severity.
Show every finding
- Warning1634 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)
- Warning197 instances
197 of 197 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)
- Warning79 instances
79 of 79 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)
- Warning31 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)
- 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.)
Validator rule: 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.)
Validator rule: 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.)
Validator rule: 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.)
Validator rule: 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 161 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 161 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 78 / 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-07-23.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-23. 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.