Feed status · checked 2026-07-19
Goshogawara City Community Bus (五所川原市コミュニティバス)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
Catalogued in Aomori, 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 6 hours ago; last changed 6 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
123 of 123 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
18 of 18 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 5 kinds of issue across 481 instances (0 error, 479 warning, 2 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
4 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)
- にこにこバス（磯松・脇元地区） (green)
- にこにこバス（太田・相内地区） (teal)
- 川倉の湯っこバス（嘉瀬・中柏木） (pink)
- 川倉の湯っこバス（金木・蒔田・神原・大東ヶ丘） (teal)
- 川倉の湯っこバス（藤枝・川倉・喜良市） (green)
| Route | Type | Line color |
|---|---|---|
| にこにこバス（十三地区） | Bus | pink |
| にこにこバス（磯松・脇元地区） | Bus | green |
| にこにこバス（太田・相内地区） | Bus | teal |
| 川倉の湯っこバス（嘉瀬・中柏木） | Bus | pink |
| 川倉の湯っこバス（金木・蒔田・神原・大東ヶ丘） | Bus | teal |
| 川倉の湯っこバス（藤枝・川倉・喜良市） | Bus | green |
This feed has 123 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 | 75.3 | first check |
| 2026-07-19 | 75.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
8 findings, ordered by severity.
Show every finding
- Warning467 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)
- Warning123 instances
123 of 123 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)
- Warning18 instances
18 of 18 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)
- 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)
- 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.)
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 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 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 78 / 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/goshogawara-city-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.