Feed status · checked 2026-07-19
Narita City Community Bus (成田市コミュニティバス)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Chiba, 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
498 of 498 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 164 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 4 kinds of issue across 2996 instances (0 error, 2986 warning, 10 informational).
Service data covers the next 164 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
3 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.
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.
- 遠山ルート (pink)
- 大室循環ルート (blue)
- 水掛ルート (white)
- 豊住ルート (green)
- しもふさ循環ルート (purple)
- 津富浦ルート (orange)
- 北須賀ルート (red)
| Route | Type | Line color |
|---|---|---|
| 遠山ルート | Bus | pink |
| 大室循環ルート | Bus | blue |
| 水掛ルート | Bus | white |
| 豊住ルート | Bus | green |
| しもふさ循環ルート | Bus | purple |
| 津富浦ルート | Bus | orange |
| 北須賀ルート | Bus | red |
This feed has 498 stops.
List every stop
- 西大須賀
- 西大須賀
- 滑河観音前
- 滑河観音前
- 滑川新宿
- 滑川新宿
- 成田市役所下総支所
- 滑河駅前
- 薬師堂
- 薬師堂
- 郷部橋
- 郷部橋
- 郷部南
- 郷部南
- 押畑坂下
- 押畑坂下
- 押畑坂上（成田病院入口）
- 押畑坂上（成田病院入口）
- 遠山公民館入口
- 遠山公民館入口
- 押畑大坂
- 押畑大坂
- 宝田小橋
- 宝田小橋
- 親作
- 親作
- 桜谷津
- 桜谷津
- 宝田白井
- 宝田白井
- 宝田小坂
- 宝田小坂
- 下福田
- 下福田
- 長沼入口
- 長沼入口
- 長沼
- 長沼
- 長沼保育園
- 長沼保育園
- 新駒井野星神社前
- 新駒井野星神社前
- 長沼坂上
- 長沼坂上
- 堺松
- 堺松
- 宮下
- 宮下
- 区民会館入口
- 区民会館入口
- 常蓮寺前
- 常蓮寺前
- ＪＡ成田市豊住支所前
- ＪＡ成田市豊住支所前
- 北部共同利用施設前
- 北部共同利用施設前
- 北羽鳥交差点
- 北羽鳥交差点
- 空仕前
- 空仕前
- 竜台入口
- 竜台入口
- セントアンナ在宅介護支援センター入口
- セントアンナ在宅介護支援センター入口
- 竜台車庫
- 竜台車庫
- 十日川排水機場前
- 十日川排水機場前
- 安西共同利用施設前
- 安西共同利用施設前
- 安西
- 安西
- 抱松共同利用前
- 抱松共同利用前
- 須賀神社前
- 須賀神社前
- 新宿入口
- 新宿入口
- 芦ケ場団地
- 芦ケ場団地
- 日豊団地入り口
- 日豊団地入り口
- ビバランド入口
- ビバランド入口
- 本三里塚なかまち公園
- 本三里塚なかまち公園
- 成井村中
- 成井村中
- 成井回転場
- 成井回転場
- 地蔵原新田
- 中野原
- 中野原
- 三和
- 三和
- 倉水
- 倉水
- 青山新田十字路
- 青山新田十字路
- 御林・フジクラ入口
- 御林・フジクラ入口
- 外記林入口
- 外記林入口
- 七沢入口
- 七沢入口
- 三里塚小学校
- 三里塚小学校
- 下総みどり学園脇
- 下総みどり学園脇
- 三ツ矢団地前
- 三ツ矢団地前
- 小御門神社前
- 小御門神社前
- 下総高校前
- 下総高校前
- 大菅
- 大菅
- 下総運動公園
- 下総郵便局
- 下総郵便局
- 下総支所下
- 下総支所下
- 高岡交差点
- 高岡交差点
- 高岡運動施設前
- 高岡運動施設前
- 三里塚小学校北
- 三里塚小学校北
- 大和田竜安寺入口
- 大和田竜安寺入口
- 小野
- 小野
- 冬父入口
- 冬父入口
- 中里入口
- 中里入口
- しもふさ学園入口
- しもふさ学園入口
- 青山入口
- 青山入口
- 青山・倉水入口
- 青山・倉水入口
- 名木常福寺前
- 名木常福寺前
- 旧名木小前
- 旧名木小前
- 名木坂下
- 名木坂下
- 本三里塚共同利用施設入口
- 本三里塚共同利用施設入口
- 高・つつじヶ丘
- 高・つつじヶ丘
- 高青年館入口
- 高青年館入口
- 野馬込
- 野馬込
- 小浮［島］
- 小浮［島］
- 小浮［下］
- 小浮［下］
- 小浮［上］
- 小浮［上］
- こすもす苑
- こすもす苑
- 新川下通り
- 新川揚水機場前
- 滑川川岸
- 滑川川岸
- 光ヶ丘共同利用施設
- 光ヶ丘共同利用施設
- 吉倉入口
- 吉倉入口
- 吉倉共同利用施設
- 吉倉共同利用施設
- さくらの山
- さくらの山
- 駒井野
- 駒井野
- 新取香橋
- 新取香橋
- 取香
- 取香
- 天神峰
- 天神峰
- 東峰
- 東峰
- 成田市場
- 新田南
- 新田南
- 三里塚御料牧場記念館北
- 三里塚御料牧場記念館北
- 川上入口
- 川上入口
- 川上
- 川上
- 多良貝
- 多良貝
- 多良貝駐在所
- 多良貝駐在所
- 前林入口
- 前林入口
- 前林坂下
- 前林坂下
- 前林小学校
- 前林小学校
- 大松
- 大松
- 道祖神
- 道祖神
- 城山入口
- 城山入口
- 西三里塚北
- 西三里塚北
- 保健福祉館
- 官林
- 官林
- 公会堂前
- 公会堂前
- 新木戸
- 新木戸
- 北の台
- 北の台
- 大沼入口
- 大沼入口
- 伊地山入口
- 伊地山入口
- 東ノ台
- 東ノ台
- 桜田
- 桜田
- 桜田権現前
- 桜田権現前
- 市場入口
- 市場入口
- 西三里塚共同利用施設
- 西三里塚共同利用施設
- 八坂神社前
- 八坂神社前
- 新田中央
- 新田中央
- 水の上西
- 水の上西
- 水の上中央
- 水の上中央
- 水の上
- 水の上
- にっぽり団地
- にっぽり団地
- 大栄ニュータウン入口
- 大栄ニュータウン入口
- and 248 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
6 findings, ordered by severity.
Show every finding
- Warning2976 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)
- Warning498 instances
498 of 498 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)
- 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.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info9 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Validator rule: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Validator rule: unknown_file · 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 164 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 164 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 85 / 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 60 / 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/narita-community-bus/2026-07-19.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-19. 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.