Feed status · checked 2026-07-19
Chigasaki City Community Bus Eboshi-go (茅ヶ崎市コミュニティバスえぼし号)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
Catalogued in Kanagawa, 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.
Checked for changes 4 hours ago; last changed 4 hours 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
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
222 of 222 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
61 of 61 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 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
The MobilityData validator flagged 4 kinds of issue across 2613 instances (0 error, 2610 warning, 3 informational).
Service data covers the next 255 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
1 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
This feed has no route shapes, so the map shows its stops only.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
| Route | Type | Line color |
|---|---|---|
| コミュニティバスえぼし号 中海岸南湖循環市立病院線 | Bus | teal (no shape in feed) |
| コミュニティバスえぼし号 北部循環市立病院線 | Bus | purple (no shape in feed) |
| コミュニティバスえぼし号 鶴嶺循環市立病院線 鶴嶺北コース | Bus | teal (no shape in feed) |
| コミュニティバスえぼし号 鶴嶺循環市立病院線 鶴嶺南コース | Bus | orange (no shape in feed) |
| コミュニティバスえぼし号 東部循環市立病院線 松が丘コース | Bus | brown (no shape in feed) |
| コミュニティバスえぼし号 東部循環市立病院線 小和田・松浪コース | Bus | teal (no shape in feed) |
This feed has 222 stops.
List every stop
- 県住入口
- 県住入口
- 日枝神社入口
- 古川
- 古川
- 萩園台河原
- 萩園台河原
- 萩園西
- 萩園西
- 環境事業センター
- 環境事業センター
- 温水プール
- 今宿北
- 浜之郷
- 東原
- 中海岸2丁目
- 若松町
- 若松町
- ラチエン通り旭が丘
- 松が丘郵便局
- 松が丘一丁目
- 松が丘緑地
- 菱沼海岸
- 開高健記念館
- 開高健記念館
- 東海岸南五丁目
- 菱沼海岸南
- 茅ヶ崎ゴルフ倶楽部前
- サザン通り北
- 松が丘二丁目
- 浜須賀小学校入口
- 平和町
- 浜須賀入口
- 平和学園前
- 平和学園前
- 平和町北
- 教会前
- 松が丘二丁目北
- 旭が丘
- 高田三丁目
- 高田三丁目
- サザン通り中央
- 室田二丁目
- 室田二丁目
- 松林三丁目
- 松林三丁目
- 松林二丁目
- 松林二丁目
- 松林
- 松林
- 松林一丁目
- 松林一丁目
- 小和田交番前
- 小和田交番前
- 西小和田
- 西小和田
- 伍仁原
- 伍仁原
- 伍仁原踏切
- 伍仁原踏切
- 浜竹一丁目
- 浜竹一丁目
- サザン通り南
- 浜竹二丁目
- 浜竹二丁目
- 辻堂駅西口
- 松浪自治会館前
- 松浪自治会館前
- 小和田公民館入口
- 小和田公民館入口
- 松浪小学校
- 松浪小学校
- 美住町交差点北
- 美住町交差点北
- 緑が浜小学校前
- 緑が浜
- 茅ヶ崎学園前
- 富士見町南
- サザンビーチ入口
- 松浪コミュニティセンター入口
- 松浪中学校入口
- 富士見町北
- 西浜
- 西浜小学校前
- 南湖6丁目
- ヨーロッパ村
- 南湖東
- 市立病院
- 市立病院
- 魚市場
- 南湖会館
- 金刀比羅神社前
- 南湖3丁目
- 上町入口
- 海岸通り
- 共恵
- 茅ヶ崎小学校前
- ツインウェイヴ
- 幸町
- 本村五丁目
- 本村五丁目
- ニュータウン入口
- ニュータウン入口
- 鶴が台入口
- 鶴が台入口
- 鶴が台中学校南
- 鶴が台中学校南
- 鶴が台中学校前
- 鶴が台中学校前
- 甘沼向原
- 甘沼向原
- 香川小学校入口
- 香川小学校入口
- 教会前
- 教会前
- 香川小学校プール前
- 香川小学校プール前
- 分教場跡
- 分教場跡
- 香川自治会館前
- 本村二丁目
- 本村二丁目
- 閑居山入口
- 閑居山入口
- 香川駅
- 香川駅
- 香川南
- 香川南
- 香川北
- 香川北
- 北陵高校入口
- 北陵高校入口
- 西方
- 西方
- 下寺尾
- 下寺尾
- みずき北
- みずき北
- 北陽中学校入口
- カトレアホーム・湘南さくら病院前
- 徳洲会病院前
- 徳洲会病院前
- 茅ヶ崎新北陵病院
- 文教大学
- 行谷
- 里山公園西駐車場前
- 里山公園平成の森前
- 里山公園
- 芹沢中部上
- 芹沢中部（善谷寺前）
- 芹沢中部下
- 芹沢細紺
- 茅ヶ崎駅南口
- 茅ヶ崎駅南口
- 茅ヶ崎駅南口
- 芹沢台田（斎場入口）
- 芹沢細谷入口
- 芹沢スポーツ広場
- 芹沢清水台上
- 小出小学校西
- 小出小学校前
- 小出二本松
- 堤自治会館前
- 堤仲谷
- 図書館前
- 浄見寺入口
- 北茅ヶ崎駅入口
- 北茅ヶ崎駅入口
- 前の田
- 前の田
- 中央公園前
- 中央公園前
- 茅ヶ崎駅北
- 茅ヶ崎駅北
- 市民文化会館前
- 市民文化会館前
- ジャスコ東
- 消防本部前
- 消防本部前
- 矢畑北
- 矢畑北
- 円蔵
- 円蔵
- 高砂通り中央
- 円蔵下町
- 円蔵下町
- 陽ざし野
- 陽ざし野
- 西久保南
- 西久保南
- 西久保保育園、つるみね老人ホーム前
- 西久保保育園、つるみね老人ホーム前
- 浜之郷小学校、コミュニティセンター前
- 浜之郷小学校、コミュニティセンター前
- 県立茅ヶ崎養護学校
- 徳洲会老人保健施設浜之郷前
- 徳洲会老人保健施設浜之郷前
- 萩園橋
- 萩園橋
- 十二天神社入口
- 市民活動サポートセンター前
- 恵泉幼稚園前
- ジャスコ前
- ジャスコ前
- 保健所前
- 浜之郷入口
- 浜之郷入口
- ＴＢＳ
- ＴＢＳ
- 浜之郷西
- 浜之郷西
- 鶴嶺八幡宮
- 鶴嶺八幡宮
- 鶴嶺小学校前
- 鶴嶺小学校前
- 今宿市営住宅前
- 今宿市営住宅前
- 入ノ田
- 入ノ田
- 宮ノ前
- 宮ノ前
- 福祉会館
Over time
Overall score across the last 2 checks — unchanged since 2026-07-18.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-18 | 80.9 | first check |
| 2026-07-19 | 80.9 | 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
6 findings, ordered by severity.
Show every finding
- Warning2594 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)
- Warning222 instances
222 of 222 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)
- Warning61 instances
61 of 61 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)
- Warning16 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)
- Info2 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Validator rule: service_window_outside_feed_period · Read the fix guide · 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 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.
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/chigasaki-city-eboshi-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.