Feed status · checked 2026-07-18
Uozu Community Bus (魚津市民バス)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Toyama, 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
315 of 315 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
94 of 94 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 256 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 8 kinds of issue across 3857 instances (0 error, 3855 warning, 2 informational).
Service data covers the next 256 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
3 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.
- ①市街地巡回ルート東回り (red)
- ⑩西布施ルート (white)
- ②市街地巡回ルート西回り (teal)
- ③上野方ルート (black)
- ④経田－道下ルート (yellow)
- ⑤天神ルート (green)
- ⑥中島ルート (yellow)
- ⑦松倉ルート (white)
- ⑧坪野ルート (pink)
- ⑨片貝ルート (orange)
| Route | Type | Line color |
|---|---|---|
| ①市街地巡回ルート東回り | Bus | red |
| ⑩西布施ルート | Bus | white |
| ②市街地巡回ルート西回り | Bus | teal |
| ③上野方ルート | Bus | black |
| ④経田－道下ルート | Bus | yellow |
| ⑤天神ルート | Bus | green |
| ⑥中島ルート | Bus | yellow |
| ⑦松倉ルート | Bus | white |
| ⑧坪野ルート | Bus | pink |
| ⑨片貝ルート | Bus | orange |
This feed has 315 stops.
List every stop
- 新川高校前
- 新川高校前
- 新川学びの森天神山交流館口
- 新川学びの森天神山交流館前
- 西魚津駅口
- TPSCo前
- TPSCo前
- 原信前
- 東尾崎（関口英範宅前）
- 東尾崎（関口英範宅前）
- 東尾崎口
- 東尾崎公民館前
- 東尾崎公民館前
- 東町（経田運輸前）
- 東町（経田運輸前）
- 浅生公民館前
- 東山公民館前
- 東山バス停前
- 平野クリニック前
- 仏田（颯創建前）
- 仏田（颯創建前）
- 平伝寺口（はなはな前）
- 平和台ニュータウン
- 新金屋
- 新金屋
- 舛田公民館前
- 松倉郵便局前
- 松倉郵便局前
- アップルヒル前
- 港町（経田魚商前）
- 港町（経田魚商前）
- 本新町
- 本新町
- 弥源寺公民館前
- 八幡社前
- 八幡社前
- 八幡橋北（大光寺町口）
- 八幡橋北（大光寺町口）
- 山下口
- 山下口
- 湯上
- 湯上
- 清流小学校口
- 吉野公民館前
- 吉野西口住宅前
- 吉野西口住宅前
- メガドンキユニー魚津店前
- ヨ八魚問屋口
- 労災病院前（玄関口）
- 伊豆ケ谷
- 伊豆ケ谷
- 下中島コミュニティセンター口
- 下中島コミュニティセンター口
- 下天神北（平田宅前）
- 加積コミュニティセンター前
- 海の駅蜃気楼
- 海の駅蜃気楼
- 観音堂
- 観音堂
- 宮津（山本酒店前）
- 宮津（山本酒店前）
- 魚津港前
- 魚津港前
- ありそドーム前
- ありそドーム前
- 魚津市役所前
- 魚津市役所前
- 橋場
- 橋場
- 金山谷
- 金山谷
- 慶野神社前
- 三ケ北
- 三ケ北
- 持光寺（大徳寺前）
- 持光寺北（セブンイレブン持光寺店前）
- 鹿熊
- 室田公民館口（富川務宅前）
- 室田公民館口（富川務宅前）
- 住吉１区
- 住吉１区
- 有山公民館前
- 住吉２区
- 住吉２区
- 住吉郵便局前
- 住吉郵便局前
- 出公民館前
- 出橋口
- 升方公民館前
- 旧松倉小学校前
- 旧松倉小学校前
- とみ里口
- とみ里口
- 上町１区会館前
- 上町１区会館前
- 信金本店前
- 信金本店前
- 新住吉西
- 新住吉西
- 石垣交差点（セントラル自動車前）
- 新川文化ホール前
- 新川文化ホール前
- 諏訪町・本町二丁目
- 諏訪町・本町二丁目
- 水族館前
- 村木コミュニティセンター前
- 村木コミュニティセンター前
- 大光寺口
- 大光寺口
- 中央通りイベントホール前
- 中央通りイベントホール前
- 町三ケ公民館前
- 町三ケ公民館前
- 坪野（旧地鉄バス停前）
- 坪野口
- 坪野口
- 石垣公民館前
- 電鉄魚津駅前
- 道下コミュニティセンター口
- 道下コミュニティセンター口
- 稗畠（稗苗商店前）
- 稗畠（稗苗商店前）
- 稗畠口（稗苗勉宅前）
- 稗畠口（稗苗勉宅前）
- 北山鉱泉前
- 北陸職業能力開発大学校前
- 本江新町（本江接骨院前）
- 本江新町（本江接骨院前）
- 満天の湯前
- 友道（友道生産組合集会所前）
- 友道（友道生産組合集会所前）
- 埋没林博物館前
- よつば小学校前
- 東部中学校前
- 東部中学校前
- 東山円筒分水槽前
- 江口東
- 木下新団地
- 東蔵
- 平沢口
- 山女
- 山女中央
- 山女公民館前
- 石垣平三叉路
- 脇坂
- 黒谷
- 上島尻公民館前
- 島尻局前
- 島尻
- 毛勝の郷シェルピース
- 奥東城
- 前東城
- 東城口
- 発電所前
- 泉町（魚津工業高校口）
- 貝田新
- 道坂
- 道坂口（MEGA・会社寮前）
- 横枕
- 袋
- 上六郎丸
- 六郎丸
- 加積コミュニティセンター口
- 天神口
- 魚津東口
- 岩高公民館前
- 大沢
- 黒沢
- 上長引野
- 長引野
- 布施爪コミュニティセンター前
- 下長引野
- 西布施交流館前
- 小川寺
- 旧西布施保育園前
- 小川寺口
- 印田公民館前
- 新幹線高架下
- 蛇田
- 下蛇田
- 蛇田口
- 北鬼江
- 川の瀬口
- 新川みどり野高校
- 経田口
- 商工会議所前
- 商工会議所前
- 金太郎温泉社員寮前
- 印田口（サツキモータース前）
- 印田口（サツキモータース前）
- 金太郎温泉口（旧青森商店前）
- 上石垣
- 上石垣新
- 上石垣新
- 上野方コミュニティセンター前
- 上野方コミュニティセンター前
- 上野方市営住宅前
- 上野方市営住宅前
- 上開木
- 上村木郵便局前
- 上村木郵便局前
- 魚津インター口
- 青島１区北（コーポラス前）
- 魚津駅西口
- 魚津駅前
- 魚津工業高校前
- 魚津工業高校前
- 魚津消防署前（三田口）
- 魚津神経サナトリウム前
- 魚津神経サナトリウム前
- 魚津病院口
- 魚津病院口
- 魚津もくもくホール
- 魚津郵便局前
- 魚津郵便局前
- 魚津歴史民俗博物館口（11～3月運休）
- 青島１区南（新栄組前）
- 青島１区南（新栄組前）
- 上野高速道路橋上
- 上野高速道路橋上
- 江口（8号高架下）
- 江口（松崎精機前）
- 江口研修センター前
- 江口研修センター前
- 大杉台掲示板前
- 旧小川田住宅口（舘建築前）
- 旧小川田住宅口（舘建築前）
- 尾崎かまぼこ館前
- 尾崎かまぼこ館前
- 上坂１区（野村表具店前）
- 上坂１区（野村表具店前）
- 上坂２区（経田駐在所前）
- 上坂２区（経田駐在所前）
- 青島２区（市営住宅口）
- 上村木南（谷川歯科医院前）
- 上村木南（谷川歯科医院前）
- 川の瀬公民館前
- 川の瀬公民館前
- 川の瀬団地（市営団地前）
- 川の瀬東
- 川原（山崎宅前）
- 川原湊建材工業前
- 川縁（川縁公民館口）
- 川縁（川縁公民館口）
- 川縁旧８号線口
- 川縁旧８号線口
- 旧かんのん亭前
- 北中（南保運輸前）
- 北中（南保運輸前）
- 青島３区会館前（児童公園前）
- and 65 more (see the full list on the map or in the GeoJSON)
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
11 findings, ordered by severity.
Show every finding
- Warning3746 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)
- Warning315 instances
315 of 315 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)
- Warning99 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)
- Warning94 instances
94 of 94 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)
- Warning3 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Validator rule: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
Stops match shape out of order (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stops_match_shape_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Validator rule: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Missing feed contact email and url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
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 256 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 256 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 64 / 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/uozu-community-bus/2026-07-18.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-18. 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.