Feed status · checked 2026-07-18
Anjo City Ankuru Bus (安城市あんくるバス)
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.
Checked for changes 1 hours ago; last changed 1 hours 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
282 of 282 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
126 of 126 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 317 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 3202 instances (0 error, 3199 warning, 3 informational).
Service data covers the next 317 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
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (あんくるバス0循環線左まわり, あんくるバス1安祥線, あんくるバス7作野線, あんくるバス8北部線).
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.
- あんくるバス0循環線右まわり (white)
- あんくるバス0循環線左まわり (gray)
- あんくるバス1安祥線 (red)
- あんくるバス2桜井線 (pink)
- あんくるバス3南部線 (teal)
- あんくるバス4高棚線 (yellow)
- あんくるバス5東部線 (blue)
- あんくるバス6西部線 (purple)
- あんくるバス7作野線 (green)
- あんくるバス8北部線 (orange)
- あんくるバス9桜井西線 (red)
| Route | Type | Line color |
|---|---|---|
| あんくるバス0循環線右まわり | Bus | white |
| あんくるバス0循環線左まわり | Bus | gray |
| あんくるバス1安祥線 | Bus | red |
| あんくるバス2桜井線 | Bus | pink |
| あんくるバス3南部線 | Bus | teal |
| あんくるバス4高棚線 | Bus | yellow |
| あんくるバス5東部線 | Bus | blue |
| あんくるバス6西部線 | Bus | purple |
| あんくるバス7作野線 | Bus | green |
| あんくるバス8北部線 | Bus | orange |
| あんくるバス9桜井西線 | Bus | red |
This feed has 282 stops.
List every stop
- 柿碕
- 柿碕
- 宇頭駅南
- 宇頭駅南
- 別所団地
- 東別所
- コアラドライブ安城
- 新田北
- 新田北
- 中部福祉センター
- 北安城駅東
- 北安城駅東
- 新田
- 新田
- 東新町
- 東新町
- 教育センター
- 教育センター
- 新安城駅南口
- イトーヨーカドー安城店
- イトーヨーカドー安城店
- 荒曽根住宅
- 荒曽根住宅
- 作野公民館
- 作野公民館
- 段留公園
- 段留公園
- 作野福祉センター
- 作野福祉センター
- 篠目町大西
- 篠目町大西
- 三河安城駅北口
- 井杭山
- 井杭山
- 養下公園
- 養下公園
- 安城公園
- 美園
- 美園
- 美園公園
- 美園公園
- 東刈谷駅北口
- 依佐美住宅
- 依佐美住宅
- 美園郵便局
- 美園郵便局
- 緑町
- 緑町
- ＪＡ二本木支店
- ＪＡ二本木支店
- 二本木公民館
- 二本木公民館
- 横山町寺田
- 横山町寺田
- 桜町
- 桜町
- 市役所・文化センター
- 中部小学校
- 中部小学校
- 農林高校前
- 農林高校前
- 池浦西
- 池浦西
- 篠目公園
- 篠目公園
- 篠目三丁目
- 篠目三丁目
- 作野小北
- 作野小北
- 住吉
- 住吉
- 八千代病院
- ピアゴ東栄店
- ピアゴ東栄店
- 東栄公園
- 東栄公園
- アンフォーレ
- アンフォーレ
- 東大道
- 東大道
- 石橋
- 石橋
- 石橋公園
- 石橋公園
- 重原田公園
- 井畑
- 井畑
- 北部公民館
- 野池
- 東栄二丁目
- 東栄二丁目
- 新安城駅北口
- 今本町
- ＪＲ安城駅
- 猿渡橋
- 不乗森神社西
- 里町内会
- 北部小学校
- 今村郵便局
- 御林
- 御林
- 小川の里
- 山中
- 山中
- 和泉工業団地東
- 和泉工業団地東
- 庄司作
- 庄司作
- 朝日町西
- 朝日町西
- アグリライフ支援センター
- アグリライフ支援センター
- 南分署前
- 南分署前
- 南高校
- 南高校
- 特別支援学校
- 特別支援学校
- アピタ安城南店
- アピタ安城南店
- 堀内公園駅西
- 堀内公園駅西
- 堀内町北
- 堀内町北
- 今村公園西
- 今村公園西
- 油ヶ淵水辺公園前
- 油ヶ淵水辺公園前
- 安城神社
- 朝日町東
- でんまるしぇ
- でんまるしぇ
- ららぽーと安城
- 日の出
- 日の出
- 南安城駅
- 南安城駅
- 南町
- 南町
- 安城更生病院
- 秋葉公園
- 秋葉公園
- 秋葉住宅西
- 秋葉住宅西
- 市役所
- 川島
- 村高
- 河野
- 河野
- 歴史博物館
- 歴史博物館
- 西尾
- 西尾
- 松井整形前
- 松井整形前
- 赤松北
- 赤松北
- 安城コロナワールド
- 安城コロナワールド
- 山崎
- 上条
- 安祥福祉センター
- アオキスーパー東明店
- アオキスーパー東明店
- 南桜井駅
- 野寺本證寺前
- 野寺本證寺前
- 藤井西
- 藤井西
- 藤井東
- 木戸
- 総合福祉センター
- 総合福祉センター
- 寺領
- 岩根
- 岩根
- 小川
- 小川
- 桜井中央公園
- 桜井中央公園
- 桜井駅東
- 桜井駅東
- 桜井駅
- 桜井駅北
- 桜井駅北
- 城山公園
- 城山公園
- 円光寺
- 円光寺
- 堀内公園
- 堀内公園
- 南中学校
- 南中学校
- 古井町内会
- 古井町内会
- 古井駅
- 古井駅
- 古井北
- 古井新町
- 古井新町
- 古井住宅
- 古井住宅
- 碧南市民病院
- 東端
- 東端保育園
- 殿町
- 根崎西
- 百々目木
- 百々目木
- 根崎東
- 欠間
- 新井
- 城ヶ入
- 明祥プラザ・マーメイドパレス
- 和泉丈山苑
- 和泉丈山苑
- 上之切
- 上之切
- 和泉北
- 和泉北
- デンパーク
- デンパーク東
- デンパーク東
- 小堤
- 小堤
- 赤松向
- 赤松向
- 赤松
- 赤松
- 昭林公園
- 昭林公園
- 高棚
- 高棚郵便局
- 高棚口
- 榎前
- 榎前北
- 榎前北
- 蔵前
- 福釜町内会
- 福釜町内会
- 百石
- 百石
- 西部福祉センター
- 西中学校
- 西中学校
- 五十石
- 五十石
- 小矢場
- 小矢場
- 箕輪町内会
- and 32 more (see the full list on the map or in the GeoJSON)
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
- Warning3184 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)
- Warning282 instances
282 of 282 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)
- Warning126 instances
126 of 126 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)
- 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.)
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
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.)
Validator rule: 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).
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 317 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 317 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/anjo-ankuru-bus/2026-07-18.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-18. 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.