Feed status · checked 2026-07-18
Tsu City Community Bus (津市コミュニティバス)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Mie, 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
373 of 373 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
159 of 159 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 5 kinds of issue across 3691 instances (0 error, 3689 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
13 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.
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 | blue (no shape in feed) |
| 河芸南・一身田・白塚循環ルート | Bus | green (no shape in feed) |
| 久居北・片田・高茶屋ルート | Bus | green (no shape in feed) |
| 久居南・雲出ルート | Bus | blue (no shape in feed) |
| 芸濃北ルート | Bus | blue (no shape in feed) |
| 芸濃南ルート | Bus | green (no shape in feed) |
| 一志東・伊勢中川駅ルート | Bus | green (no shape in feed) |
| 一志西循環ルート | Bus | blue (no shape in feed) |
| 倭・八ツ山・一志病院ルート | Bus | blue (no shape in feed) |
| 元取・家城ルート | Bus | orange (no shape in feed) |
| 川口・大三・三重中央医療センタールート | Bus | green (no shape in feed) |
| 美杉東ルート | Bus | blue (no shape in feed) |
| 美杉西ルート | Bus | green (no shape in feed) |
| 観光ルート（アサギマダラシーズン（太郎生ルート）） | Bus | white (no shape in feed) |
| 観光ルート（ミツマタシーズン） | Bus | white (no shape in feed) |
| 観光ルート（桜シーズン） | Bus | white (no shape in feed) |
| 観光ルート（アサギマダラシーズン（下之川ルート）） | Bus | white (no shape in feed) |
| 観光ルート（ゴールデンウィーク） | Bus | white (no shape in feed) |
| 観光ルート（紅葉シーズン） | Bus | white (no shape in feed) |
This feed has 373 stops.
List every stop
- 相川町集会所
- 相川町集会所
- イオンタウン津城山
- 落合橋
- 休日応急診療所前
- 休日応急診療所前
- 木造
- 木造７区集会所
- 小野辺南
- こべき保育園
- 榊原車庫前
- 桜が丘集会所
- 桜が丘集会所
- 市営野村団地
- 庄田
- 新地北
- 新地北
- 須ヶ瀬
- 善応寺団地
- 高橋
- 津南警察署前
- 津南警察署前
- 寺野
- 中川原
- 桃園駅東
- 新家野菜出荷場
- 野村第二団地
- 白雲荘前
- 東出南公園
- 東町(久居地域)
- 久居アルスプラザ南
- 久居アルスプラザ南
- 久居インターガーデン
- 久居インターガーデン
- 久居駅東口
- 久居団地
- 久居東中学校
- 久居東中学校
- 久居老人福祉センター
- 久居老人福祉センター
- 藤ヶ丘団地
- スギ薬局久居元町店前
- スギ薬局久居元町店前
- 牧クラブ
- 三重中央医療センター
- 明神
- 諸戸山
- 八知山
- ぎゅーとらラブリー久居店
- 片田団地
- 上小川
- 上小川
- かわきた苑
- 池田集会所
- 雲出市民館
- 警察学校前
- 警察学校前
- 小森南
- 小森南
- 小森山
- 小森山
- 里の上
- 白塚いけだクリニック前
- 白塚いけだクリニック前
- 赤部北交差点
- イオン前
- いこいの森
- 一色中央
- 上野北
- 上野公民館
- 上野小学校西
- 上野中央霊園前
- 上野中
- 上野南
- 大蔵園中央
- 影重北
- 影重公民館
- 河芸公民館
- 河芸総合支所
- 北黒田
- 近鉄千里駅
- 近鉄豊津上野駅
- 久知野中央
- 久知野中央
- サンシ東
- 松林寺前
- 新上野東
- 高佐北
- 高佐東
- 千里ヶ丘公民館
- 千里ヶ丘公民館
- 千里ヶ丘第二公園
- 千里ヶ丘団地口バス停
- 千里ヶ丘団地口バス停
- 千里ヶ丘団地東
- 千里ヶ丘団地東
- 千里ヶ丘西
- 豊津小学校東
- 中瀬
- 浜田公民館
- 東上野中央
- 東上野中央
- 東千里北
- 東千里中央
- ほほえみセンター
- 道の駅津かわげ
- 南黒田
- 南黒田公民館
- 三行公民館
- 美松園団地
- 白塚駅西
- 白塚団地
- セノパーク
- 高茶屋
- 高茶屋
- 津北整形外科前
- 津北整形外科前
- 中小川
- 中小川
- 中山
- 中山
- 西豊野区集会所
- 北部市民センター前
- 北部市民センター前
- イオンモール津南
- 赤塚クリニック
- イオンタウン芸濃
- 市場(芸濃地域)
- 梅ヶ畑
- 岡本
- 忍田
- 落合の郷
- 小野平
- 下川
- 河原
- 北神山
- 北畑
- ぎゅーとらラブリー芸濃店
- 楠原
- 楠原東
- 芸濃総合支所
- 芸濃総合文化センター
- 下ノ垣内
- 錫杖湖水荘
- 新田
- 多門
- 団地南
- 長徳寺
- 殿町
- 中瀬古
- 中縄
- 中町
- 萩野
- 八幡前
- 林川原
- 林殿町
- 林町
- 林南
- 平林
- 藤ヶ丘
- 宝並
- 南山西
- 南山東
- 椋本新町東
- 椋本団地
- 椋本郵便局
- 市場公民館
- 青木団地
- 本山前
- 本山前
- 宮の前
- 一身田団地
- 一身田団地
- 一身田郵便局
- 家城駅前
- 家城小学校前
- 家城橋前
- 一志病院
- 上田
- 魚石前
- 魚九前
- 大原
- 大三駅前
- 大三出張所前
- 大三小学校前
- 大三小学校前
- 大三神社前
- 岡
- 奥佐田
- 垣内
- 垣内
- 上川口
- 上福田山
- 茅刈公民館前
- 川口駅前
- 川口小学校前
- 川久保
- きずな
- グリーンタウン
- グリーンタウン東
- 下司名
- 小杉
- 榊原温泉口駅
- 佐田
- 算所
- 算所
- 下川口
- 下福田山
- 成願寺前
- 城立
- 城立
- 関ノ宮
- 関谷
- 関谷
- 立町
- 立町
- 団地前
- 中央公園前
- 飛野
- 中徳田
- 中ノ村
- 中福田山
- 二本木
- 白山高校前
- 白山総合支所前
- 白山台
- 白山中学校前
- 八対野１区
- 八対野３区
- 八対野４区
- 八対野４区
- 東町(白山地域)
- 藤
- Ｆ内野
- Ｆグリーンタウン
- Ｆ公民館
- Ｆ下出福田山
- Ｆ中ノ村
- Ｆ藤
- Ｆ南大原
- Ｆ柳谷橋
- 古市
- 文化センター
- マックスバリュ(川口店)
- マックスバリュ(白山店)
- 三ヶ野上広
- 三ヶ野北谷
- 三ヶ野里川
- 三ヶ野田広
- 三ヶ野殿垣内
- and 123 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
8 findings, ordered by severity.
Show every finding
- Warning3661 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)
- Warning373 instances
373 of 373 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)
- Warning159 instances
159 of 159 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)
- Warning26 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 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 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/tsu-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.