Feed status · checked 2026-07-23
Owari Asahi Asapy-go (尾張旭市営バス あさぴー号)
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 4 of 4 score categories from the agency's own feed.
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 9 snapshots.
- 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
169 of 169 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
76 of 76 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 130 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 7 kinds of issue across 4039 instances (0 error, 4033 warning, 6 informational).
Service data covers the next 130 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
2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (あさぴー号①西ルート左回り, あさぴー号②西ルート右回り).
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.
Sampled 9 times outside service hours: 3 of 3 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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- あさぴー号①西ルート左回り (gray)
- あさぴー号②西ルート右回り (gray)
- あさぴー号③東ルート左回り (teal)
- あさぴー号④東ルート右回り (teal)
| Route | Type | Line color |
|---|---|---|
| あさぴー号①西ルート左回り | Bus | gray |
| あさぴー号②西ルート右回り | Bus | gray |
| あさぴー号③東ルート左回り | Bus | teal |
| あさぴー号④東ルート右回り | Bus | teal |
This feed has 169 stops.
List every stop
- 市役所
- 市役所
- 市役所
- 市役所
- 名古屋産業大前
- 名古屋産業大前
- 城山公園
- 城山公園
- 平子公民館
- 平子公民館
- 長池北
- 長池北
- 城山小前
- 城山小前
- 城山町城山
- 城山町城山
- 平子町長池上
- 平子町長池上
- 県営住宅
- 県営住宅
- 平子町中通
- 平子町中通
- 城前町茅池
- 城前町茅池
- 旭前駅北
- 旭前駅北
- 白鳳町一丁目
- 白鳳町一丁目
- 桜ヶ丘町三丁目
- 桜ヶ丘町三丁目
- 桜ヶ丘町一丁目
- 桜ヶ丘町一丁目
- 労災病院口
- 労災病院口
- 旭労災病院
- 大森北
- 大森北
- 小幡緑地東園
- 小幡緑地東園
- どうだん亭
- どうだん亭
- 東名西公園
- 東名西公園
- 印場駅
- 西部浄化センター
- 西部浄化センター
- 渋川福祉センター西
- 渋川福祉センター西
- 瑞鳳橋
- 瑞鳳橋
- 東山町
- 東山町
- 庄南町
- 庄南町
- 本地住宅南
- 本地住宅南
- 本地住宅
- 南新町中畑
- 南新町中畑
- 本地ヶ原
- 本地ヶ原
- 北本地ヶ原町
- 北本地ヶ原町
- 晴丘
- 晴丘
- 愛知医大
- 南栄町タチヤ前
- 新池交流館
- 新池交流館
- 南本地ヶ原町
- 南本地ヶ原町
- 本地原小
- 本地原小
- 緑町緑ヶ丘
- 緑町緑ヶ丘
- 長坂町西
- 長坂町西
- 吉岡公園南
- 吉岡公園南
- 印場橋南
- 印場橋南
- 東印場橋
- 東印場橋
- 旭野高東
- 旭野高東
- 旭前駅
- 城前町四丁目
- 城前町四丁目
- 西大道町
- 西大道町
- 文化会館北
- 文化会館北
- 北山町北山
- 北山町北山
- 東中学校西
- 東中学校西
- 南原山町赤土
- 南原山町赤土
- 西山保育園北
- 西山保育園北
- 井田町西
- 井田町西
- 北山町六反田
- 北山町六反田
- 稲葉町
- 稲葉町
- 多世代交流館
- 多世代交流館
- 稲葉町南
- 稲葉町南
- 市民プール
- 市民プール
- 晴丘北
- 晴丘北
- 晴丘町東
- 晴丘町東
- 本地ヶ原東公園
- 本地ヶ原東公園
- 西本地橋バロー前
- 西本地橋バロー前
- 三郷公民館北
- 三郷公民館北
- 三郷小南
- 三郷小南
- 狩宿町やまひこ前
- 狩宿町三丁目
- 狩宿町三丁目
- 瀬戸川
- 瀬戸川
- 東部市民センター
- 東部市民センター
- シーナシーナ尾張旭前
- 三郷駅北
- 三郷駅北
- 東栄町交差点
- 東栄町交差点
- 東大久手
- 東大久手
- 東栄小東
- 東栄小東
- 根の鼻町集会所
- 根の鼻町集会所
- 旭台第1号公園北
- 旭台第1号公園北
- 旭台3丁目
- 旭台3丁目
- 旭台西
- 旭台西
- 柏井北公園
- 柏井北公園
- 森林公園
- 上水道管理センター北
- 上水道管理センター北
- 旭ヶ丘町旭ヶ丘
- 旭ヶ丘町旭ヶ丘
- 旭ヶ丘町長洞
- 旭ヶ丘町長洞
- 旭ヶ丘ふれあい会館北
- 旭ヶ丘ふれあい会館北
- 旭平和墓園東
- 旭平和墓園東
- 旭ヶ丘町山の手
- 旭ヶ丘町山の手
- あたご保育園前
- あたご保育園前
- 北原山町バロー前
- 尾張旭駅
- 保健福祉センター
- 保健福祉センター
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
10 findings, ordered by severity.
Show every finding
- Warning4022 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)
- Warning169 instances
169 of 169 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)
- Warning76 instances
76 of 76 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)
- Warning8 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)
- Warning1 instance
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Validator rule: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info4 instances
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)
- 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 130 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 130 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 73 / 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 100 / 100
- 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/owari-asahi-asapy-go/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.