GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

Yanagawa City Community Bus (柳川市コミュニティバス)

Based on the feed this agency publishes

Service mode Bus

80.9 / 100

First scorecard for this agency

Catalogued in Fukuoka, Japan.

Covers 255 daysAccessibility gapsRealtime not yet published

Yanagawa City's community bus network.

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 59 minutes ago; last changed 59 minutes 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

Fix 01

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

174 of 174 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

Fix 02

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

43 of 43 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

Fix 03

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.

  1. 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.

  2. 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.

  3. 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 255 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

Correctness85.0 / 100

The MobilityData validator flagged 4 kinds of issue across 15224 instances (0 error, 15216 warning, 8 informational).

Freshness100.0 / 100

Service data covers the next 255 days.

Rider experience59.8 / 100

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.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

1 accessibility depth signal

  • 6 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (蒲池ひがしルート, 蒲池にしルート, 両開ひがしルート, 両開にしルート, 大和みなみルート, and more).

    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.

FaresLegacy fares

Fares are applied to trips.

Realtime qualityNot yet measured

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 data

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

  • 三橋ルート (red)
  • 両開にしルート (pink)
  • 両開ひがしルート (green)
  • 大和にしルート (teal)
  • 大和ひがしルート (purple)
  • 大和みなみルート (yellow)
  • 市街循環線 (yellow)
  • 昭代ルート (blue)
  • 蒲池にしルート (red)
  • 蒲池ひがしルート (pink)
Routes in Yanagawa City Community Bus (柳川市コミュニティバス)'s feed
RouteTypeLine color
三橋ルートBusred
両開にしルートBuspink
両開ひがしルートBusgreen
大和にしルートBusteal
大和ひがしルートBuspurple
大和みなみルートBusyellow
市街循環線Busyellow
昭代ルートBusblue
蒲池にしルートBusred
蒲池ひがしルートBuspink

This feed has 174 stops.

List every stop
  • あめんぼセンター前
  • あめんぼセンター前
  • アスタラビスタ
  • 豊後屋
  • 筑後中部魚市場（西）
  • 筑後中部魚市場（西）
  • 藤吉コミュニティセンター
  • 橋本町
  • 亀の井ホテル柳川
  • 橋本公民館前
  • 町矢加部
  • 町矢加部
  • 蒲池農村環境改善センター
  • 蒲池・立石団地
  • 立石北
  • 本園公民館
  • 蒲生公民館
  • 井出公民館
  • 中牟田公民館
  • 立石南
  • 北矢加部
  • 上八丁
  • 輝泉荘前
  • 鹿島
  • 南本村
  • 北本村
  • 中村
  • 野田公民館
  • JA根葉倉庫前
  • 根葉
  • 中古賀公民館前
  • 萩島公民館
  • 京手団地
  • 鹿島北
  • 蒲池農協前
  • 京町商店街
  • くろだ整形クリニック
  • 改善センター前
  • 改善センター前
  • ゆめモール
  • 高畑
  • 散田西
  • 磯鳥
  • 蒲船津
  • 正行
  • 三橋庁舎
  • JA柳川三橋支所
  • 百町（構造改善センター）
  • 木元
  • 起田
  • 吉開（コミュニティセンター）
  • 新村
  • 中山（（株）ヤスナガ前）
  • 中山公民館
  • 中山散田
  • 五拾町
  • 棚町
  • 棚町沖田
  • 垂見（構造改善センター）
  • 水の郷
  • まほろばセンター
  • 政屋
  • 中開（両開）
  • 中開四ツ角
  • 中開四ツ角
  • 西鉄蒲池駅
  • 中ノ切
  • 中六十丁公民館
  • 中島商店街（西口）
  • 長田病院
  • 西鉄柳川駅東口
  • 東宮永団地
  • 江曲団地
  • 対米公民館
  • 佃町古川
  • 猟町古川公民館
  • 四丁開公民館
  • 番所（両開）
  • 四平
  • 城戸
  • 東ノ切東
  • 東ノ切西
  • 両開郵便局
  • 東六十丁
  • 下八丁下
  • 西ノ切東
  • 西ノ切西
  • 明治
  • 西六十丁
  • 寿硯
  • 村山公民館
  • 外開
  • 作出
  • 矢留開
  • 吉富・矢留団地
  • うぶすな館
  • 沖端
  • 沖端
  • 古賀
  • 浜武漁協前
  • 崩道公民館
  • 吉原南
  • 八ッ家南
  • 七ッ家南
  • 大沢集会所
  • 野村公民館
  • 七ッ家北
  • 八ッ家北
  • 吉原公民館
  • 中野公民館
  • 浜武公民館
  • 甲斐田病院
  • 田脇
  • 旧マミーズ
  • 宮下
  • 宮上
  • 北沖田
  • 諸藤公民館
  • 四十丁公民館前
  • スーパーマルマツ
  • 下宮永
  • 下宮永
  • 徳益
  • 徳益
  • 柳川病院前
  • 柳川市民文化会館西口
  • 柳川病院
  • 上塩塚
  • 下棚町
  • 中棚町
  • 六合（学童保育所）
  • 鷹尾（因福寺）
  • 島
  • 西鉄中島駅
  • 漁村センター前
  • 南二重北
  • 西二重公民館
  • 旧北二重公民館
  • やまと小学校前
  • 平木
  • 大和生涯学習センター
  • 江曲
  • 江曲
  • 柳川警察署前
  • 柳川警察署前
  • 皿垣南
  • 皿垣
  • 宇土公民館
  • 上土居
  • 荒開西
  • 弁天
  • 弁天南
  • 弁天東
  • 甲木
  • 三五平
  • 南二重
  • 上ケ地
  • 江島
  • 徳益団地
  • 明古
  • 大和コミュニティセンター
  • 中開（大和）
  • 番所（大和）
  • 二十五丁
  • 南開東
  • 南野
  • 作出公民館
  • 下塩塚
  • 野田
  • 柳川リハビリテーション病院
  • 柳川ショッピングモール
  • 柳川市民体育館
  • 柳川市役所（柳川庁舎）
  • 大和庁舎

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
  • Warning15185 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

  • Warning174 instances

    174 of 174 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

  • Warning43 instances

    43 of 43 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

  • Warning31 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

  • Info5 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

  • Info3 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.)

    Validator rule: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules

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 255 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 255 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.

Yanagawa City Community Bus (柳川市コミュニティバス) GTFS data quality grade: B

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/yanagawa-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.