Feed status · checked 2026-09-05
Taito City Megurin (台東区「めぐりん」)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Tokyo, 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.
Measured 3 of 4 score categories from the official feed URL on file.
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 official feed URL on file.
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
128 of 128 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
290 of 290 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
- 128 of 128 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
- 290 of 290 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 117 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 9322 instances (0 error, 9319 warning, 3 informational).
Service data covers the next 117 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.
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 128 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.
- 北めぐりん（根岸まわり） (white)
- 北めぐりん（浅草まわり） (orange)
- 南めぐりん (gray)
- 東西めぐりん (pink)
| Route | Type | Line color |
|---|---|---|
| 北めぐりん（根岸まわり） | Bus | white |
| 北めぐりん（浅草まわり） | Bus | orange |
| 南めぐりん | Bus | gray |
| 東西めぐりん | Bus | pink |
List every stop
- ① 台東病院
- ② 吉原大門
- ③ 竜泉三丁目
- ④ 三ノ輪二丁目
- ⑤ 三ノ輪駅
- ⑥ 一葉記念館入口（いきいきてらす東）
- ⑦ 竜泉一丁目（いきいきてらす入口）
- ⑧ 金杉区民館下谷分館入口
- ⑨ 下谷三丁目
- ⑩ 金杉通り
- ⑪ 根岸三丁目
- ⑫ 防災広場根岸の里
- ⑬ 書道博物館
- ⑭ 鶯谷駅北
- ⑮ 鶯谷駅南
- ⑯ 入谷駅入口
- ⑰ 大正小学校
- ⑱ 生涯学習センター北
- ⑲ 千束二丁目
- ⑳ 千束三丁目
- ① 浅草駅
- ② 花川戸
- ③ 隅田公園
- ④ リバーサイドスポーツセンター前
- ⑤ 今戸一丁目
- ⑥ 今戸二丁目
- ⑦ 橋場老人福祉館西
- ⑧ 橋場一丁目
- ⑨ 清川一丁目
- ⑩ 東浅草二丁目
- ⑪ 吉原大門
- ⑫ 竜泉三丁目
- ⑬ 三ノ輪二丁目
- ⑭ 三ノ輪駅
- ⑮ 一葉記念館入口（いきいきてらす東）
- ⑯ 千束三丁目
- ⑰ 台東病院
- ⑱ 千束小学校前
- ⑲ 浅草五丁目
- ⑳ 浅草警察署前
- ㉑ 浅草四丁目
- ㉒ 浅草寺北
- ㉓ 二天門
- ㉔ 浅草松屋西
- ① 上野駅
- ② 永寿総合病院
- ③ 御徒町
- ④ 新御徒町駅
- ⑤ 台東三丁目
- ⑥ 台東地区センター
- ⑦ 三井記念病院前
- ⑧ 柳北スポーツプラザ
- ⑨ 浅草橋駅北
- ⑩ 柳橋中央通り
- ⑪ 柳橋分院入口
- ⑫ 鳥越神社前
- ⑬ 環境ふれあい館ひまわり入口
- ⑭ 三筋老人福祉館東
- ⑮ 南部区民事務所
- ⑯ 大江戸線蔵前駅
- ⑰ 田原町駅
- ⑱ 浅草菊水通り
- ⑲ 西浅草
- ⑲-2 菊屋橋
- ⑳ 台東区役所
- ㉑ 上野学園
- ㉒ 北上野二丁目
- ㉓ 松が谷
- ㉔ 生涯学習センター南
- ㉕ 生涯学習センター北
- ㉖ 千束二丁目
- ㉗ 千束三丁目
- ㉘ 台東病院
- ㉘-2 大正小学校前
- ㉙ 入谷地区センター
- ㉚ 入谷南公園
- ㉛ 北上野
- ㉜ 上野学園
- ㉝ 台東保健所
- ㉞ 台東区役所
- ① 上野駅終
- ① 台東区役所
- ② 上野駅入谷口
- ③ ＪＲ上野駅公園口
- ④ 東京国立博物館
- ⑤ 旧東京音楽学校奏楽堂
- ⑥ 寛永寺
- ⑦ 上野桜木会館
- ⑧ 谷中清水町公園
- ⑨ 旧吉田屋酒店
- ③-1 上野郵便局
- ④-1 下谷二丁目（鶯谷駅南）
- ⑤-1 上野桜木
- ⑥-1 谷中（旧吉田屋酒店前）
- ⑩ 谷中霊園入口
- ⑪ 三崎坂上
- ⑫ 特養ホーム谷中入口
- ⑬ 谷中銀座・よみせ通り
- ⑭ 千駄木駅
- ⑮ 谷中小学校
- ⑯ 三崎坂上
- ⑰ 谷中霊園入口
- ⑱ 旧吉田屋酒店
- ⑮-1 日本医科大学付属病院下
- ⑯-1 根津駅前
- ⑰-1 善光寺坂上
- ⑲ 三段坂上
- ⑳ 池之端四丁目
- ㉑ 池之端三丁目
- ㉒ 上野動物園池之端門前
- ㉓ 水上音楽堂
- ㉔ 京成上野駅・上野公園
- ㉕ 台東区役所
- ㉖ 上野駅入谷口
- ㉗ 北上野二丁目
- ㉘ 松が谷
- ㉙ 西浅草三丁目
- ㉚ つくばエクスプレス浅草駅
- ㉛ 雷門通り
- ㉜ 浅草駅
- ㉝ 雷門前
- ㉞ 都営浅草駅
- ㉟ 浅草消防署
- ㊱ 南部区民事務所
- ㊲ 三筋二丁目（台東デザイナーズビレッジ）
- ㊳ 小島社会教育館
- ㊴ 新御徒町駅
- ㊵ 永寿総合病院東
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
7 findings, ordered by severity.
Show every finding
- Warning8898 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)
- Warning420 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)
- Warning290 instances
290 of 290 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)
- Warning128 instances
128 of 128 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)
- 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)
- Info2 instances
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.)
Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
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)
Conformance mark Not yet
One requirement remains for this feed to earn 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 117 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 117 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 79 / 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/taito-megurin/2026-09-05.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-09-05. 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.