Feed status · checked 2026-07-19
Nagareyama Green Bus (流山ぐりーんバス)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
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
181 of 181 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
338 of 338 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 175 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 7509 instances (0 error, 7503 warning, 6 informational).
Service data covers the next 175 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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 流山ぐりーんバス 1江戸川台西ルート (gray)
- 流山ぐりーんバス 2江戸川台東ルート (gray)
- 流山ぐりーんバス 3西初石ルート (gray)
- 流山ぐりーんバス 4美田・駒木台ルート (gray)
- 流山ぐりーんバス 5松ケ丘・野々下ルート (gray)
- 流山ぐりーんバス 6南流山・木ルート (gray)
| Route | Type | Line color |
|---|---|---|
| 流山ぐりーんバス 1江戸川台西ルート | Bus | gray |
| 流山ぐりーんバス 2江戸川台東ルート | Bus | gray |
| 流山ぐりーんバス 3西初石ルート | Bus | gray |
| 流山ぐりーんバス 4美田・駒木台ルート | Bus | gray |
| 流山ぐりーんバス 5松ケ丘・野々下ルート | Bus | gray |
| 流山ぐりーんバス 6南流山・木ルート | Bus | gray |
This feed has 181 stops.
List every stop
- 南流山８丁目東
- 森の図書館
- 八木北小学校南門入口
- 八木北小学校南門入口
- 八木郵便局前
- 八木郵便局前
- ルアジーランド
- ロジポート前
- ロジポート前
- 若葉台
- 若葉台
- おおぐろの森中学校前
- おおぐろの森中学校前
- 流山おおたかの森駅東口
- 東初石五丁目
- 東初石五丁目
- 江戸川台１４号公園前
- おおたかの森西四丁目
- おおたかの森西四丁目
- 江戸川台小学校前
- 江戸川台西口商店街
- 江戸川台西口商店街
- 江戸川台東３丁目商店会
- 江戸川台東４丁目
- 江戸川台福祉会館前
- おおたかの森病院前
- おおたかの森病院前
- 小田急ハイツ
- 小田急ハイツ
- 木
- 木
- 青田１号公園前
- 青田１号公園前
- 木自治会館入口
- 木自治会館入口
- 北１号公園前
- 北１号公園前
- 木西
- 木西
- 木南
- 木南
- 県民プラザ前
- 県民プラザ前
- 駒木台第二自治会館入口
- 駒木台第二自治会館入口
- 駒木台中央
- 駒木台中央
- 駒木台東
- 駒木台東
- 駒木台福祉会館入口
- 駒木台福祉会館入口
- コミュニティプラザ前
- コミュニティプラザ前
- 青田東
- 青田東
- サンロード入口
- サンロード入口
- ＧＬＰ流山
- ＧＬＰ流山
- 四季野公園入口
- 四季野公園入口
- 四季の杜
- ショッピングセンター前
- ショッピングセンター前
- 星和住宅
- 星和住宅団地
- ＴＢＳやよい団地
- 東急１号公園前
- 青田南
- 青田南
- 東部近隣公園入口
- 東部近隣公園入口
- 東部診療所前
- 東部診療所前
- 東部中学校入口
- 東部中学校入口
- 豊四季駅南口
- 豊四季第一公園
- 豊四季第一公園
- 長崎入口
- 長崎入口
- 長崎小学校入口
- 長崎小学校入口
- 流山おおたかの森駅西口
- 流山おおたかの森駅西口
- 流山北高校前
- 流山北高校前
- 流山郵便局前
- 流山郵便局前
- 赤坂橋
- 赤坂橋
- 名都借
- 名都借
- 名都借交差点
- 名都借交差点
- ７号公園
- ７号公園
- 西初石３丁目（初石駅入口）
- 西初石３丁目（初石駅入口）
- 西初石中学校前
- 西初石中学校前
- 西初石２丁目
- 西初石２丁目
- 西初石４丁目
- 西初石４丁目
- 西松ケ丘１丁目
- 西松ケ丘１丁目
- 野々下１号公園
- 野々下１号公園
- 野々下５丁目
- 野々下５丁目
- 東小学校前
- 東小学校前
- 野々下５丁目西
- 野々下５丁目西
- 野々下３丁目
- 野々下３丁目
- 野々下４号公園
- 野々下４号公園
- 野々下４丁目北
- 野々下４丁目北
- パークホームズ前
- パークホームズ前
- ハートケア流山前
- ハートケア流山前
- ８号公園
- 東深井散策の森入口
- 東深井１２号緑地前
- 愛宕ふれあいの森
- 愛宕ふれあいの森
- 東深井小学校前
- 東深井７号公園前
- 東深井２８号公園前
- 東深井福祉会館入口
- 富士見台１・２丁目
- 富士見台１・２丁目
- 富士見台郵便局前
- 富士見台郵便局前
- 船戸
- 船戸
- 北部公民館入口
- 北部公民館入口
- 保健センター前
- 保健センター前
- 江戸川台駅西口
- ほっとプラザ
- 松ケ丘旭会館前
- 松ケ丘旭会館前
- 松ケ丘５丁目
- 松ケ丘５丁目
- 松ケ丘３丁目
- 松ケ丘３丁目
- 松ケ丘団地
- 松ケ丘団地
- 松ケ丘２丁目
- 松ケ丘２丁目
- 松ケ丘ふるさとの森公園
- 松ケ丘ふるさとの森公園
- 松ケ丘６丁目
- 松風自治会集会所前
- 美田１号公園
- 美田１号公園
- 江戸川台駅東口
- 美田桜並木通り
- 美田桜並木通り
- 美田団地入口
- 美田団地入口
- 南柏駅西口
- 南柏駅西口
- 南流山駅南口
- 南流山３丁目
- 南流山３丁目
- 南流山自治会館入口
- 南流山自治会館入口
- 南流山センター
- 南流山センター
- 南流山７丁目
- 南流山７丁目北
- 南流山８丁目西
- 江戸川台１５号公園前
- 江戸川台１５号公園前
Over time
Overall score across the last 2 checks — unchanged since 2026-07-18.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-18 | 73.3 | first check |
| 2026-07-19 | 73.3 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-18.
Same feed file as 2026-07-18; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
9 findings, ordered by severity.
Show every finding
- Warning7431 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)
- Warning338 instances
338 of 338 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)
- Warning181 instances
181 of 181 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)
- Warning57 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)
- Warning14 instances
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
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)
- Info3 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)
- Info3 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 175 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 175 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 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/nagareyama-green-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.