Feed status · checked 2026-08-01
Mie Kotsu Shima (三重交通 志摩地域)
Based on the feed this agency publishes
Service mode Bus
up 6.9 since 2026-07-31 · D → C
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.3, validator 8.0.1.
Checked for changes 73 minutes ago; last changed 73 minutes ago.
Measured 4 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- 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
367 of 367 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
311 of 311 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
Review the flagged fields and fill in the ones your riders would use.
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.
⏱ A field at a time; not urgent.worth about +8 points in its category
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- 367 of 367 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- 311 of 311 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Some files leave out fields that GTFS asks for but does not require.
- Next action
- Review the flagged fields and fill in the ones your riders would use.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
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. See this feed's finding-clearance log.
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. See this feed's finding-clearance log.
Review the flagged fields and fill in the ones your riders would use. · 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. See this feed's finding-clearance log.
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 93 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
- Live-arrival data covered 80% of scheduled trips in the sampled window.
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 10 kinds of issue across 890 instances (0 error, 883 warning, 7 informational).
Service data covers the next 93 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.
Fares are applied to trips.
Sampled 9 times: 3 of 3 configured feeds healthy; 80.0% of scheduled trips had live predictions; 100.0% of vehicles on their route; predictions ran a median of 58s behind schedule.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 367 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 御座線 (green)
- 宿浦線 (green)
- 安乗線 (green)
- 五ヶ所線 (green)
- 志摩スペイン村線 (green)
- 志島循環線（国府経由） (green)
| Route | Type | Line color |
|---|---|---|
| 御座線 | Bus | green |
| 宿浦線 | Bus | green |
| 安乗線 | Bus | green |
| 五ヶ所線 | Bus | green |
| 志摩スペイン村線 | Bus | green |
| 志島循環線（うらじろ経由） | Bus | green (no shape in feed) |
| 志島循環線（国府経由） | Bus | green |
| 南伊勢町営バス・南海線 | Bus | green (no shape in feed) |
List every stop
- 山田上口
- 山田上口
- 宮町
- 宮町
- 尼辻
- 尼辻
- 新道
- 新道
- 伊勢市駅前
- 伊勢市駅前
- 伊勢市駅前
- 伊勢市駅前
- 伊勢市駅前
- 宇治山田駅前
- 宇治山田駅前
- 前田古市口
- 前田古市口
- 伊勢警察前
- 伊勢警察前
- 伊勢学園前
- 伊勢学園前
- 山商口
- 山商口
- 浦田町
- 浦田町
- 吹上町
- 吹上町
- 浦口町
- 浦口町
- 辻久留町
- 辻久留町
- 伊勢赤十字病院
- 一之木二丁目
- 一之木二丁目
- 一之木三丁目
- 一之木三丁目
- 一之木
- 一之木
- ミタス伊勢
- ミタス伊勢
- 論出
- 論出
- 清水(伊勢)
- 清水(伊勢)
- 済美学院前
- 済美学院前
- 大倉うぐいす台
- 大倉うぐいす台
- 大倉
- 佐八
- 佐八
- 佐八農協前
- 白木
- 白木
- 津村口
- 津村口
- 津村
- 津村
- 沼木中学校前
- 広岡
- 上野
- 宮川パーク
- 伊勢病院前
- 伊勢病院前
- 皇學館大学前
- 皇學館大学前
- 神宮徴古館前(倭姫宮前)
- 神宮徴古館前(倭姫宮前)
- 中村町（月讀宮前）
- 中村町（月讀宮前）
- 伊勢病院西口
- 伊勢病院西口
- 横輪口
- 河口外科前
- 河口外科前
- 佐八保育所
- 佐八保育所
- 辻久留二丁目
- 昭和苑口
- 電子前
- 上野南
- 開花橋
- 辻久留三丁目
- 辻久留三丁目
- 天の岩戸口
- 天の岩戸口
- 築地口
- 築地口
- 恵利原
- 恵利原
- 川辺
- 川辺
- 磯部小学校前
- 磯部バスセンター
- 磯部バスセンター
- 磯部バスセンター
- 磯部バスセンター
- 穴川
- 穴川
- 穴川駅口
- 穴川駅口
- 浅野
- 浅野
- 横山登山口
- 横山登山口
- 鵜方西口
- 鵜方西口
- 鵜方駅前
- 鵜方駅前
- 鵜方駅前
- 鵜方駅前
- 鵜方駅前
- 志摩市役所前
- 志摩市役所前
- 立神口
- 立神口
- 甲賀口
- 甲賀口
- 島茶屋前
- 島茶屋前
- 畔名口
- 岡山（志摩）
- 名田口
- 大王口
- 大王小坂
- 大王小坂
- 大王小学校前
- 波切
- 波切
- 大王支所前
- 大王支所前
- 志摩市民病院
- 船越浜
- 船越浜
- 船越
- 深谷水道
- 深谷水道
- 片田稲荷前
- 片田稲荷前
- 片田新開
- 片田新開
- 片田(志摩)
- 片田(志摩)
- 片田椿山
- 片田椿山
- 布施田
- 布施田西口
- 布施田西口
- 和具学校前
- 和具学校前
- 和具
- 和具
- 志摩高岡
- 志摩高岡
- 越賀神社前
- 越賀
- 越賀西
- 御座白浜
- 御座白浜
- 御座
- 御座
- 御座港
- 渡鹿野渡船場
- 鵜方西口(郵便局前）
- 鵜方西口(郵便局前）
- 立神
- 水産高校前
- 横山下
- 横山下
- 鵜方浜
- 鵜方浜
- 福川原
- 福川原
- 大崎口
- 大崎口
- 迫子
- 迫子
- 塩屋
- 桧山路
- 桧山路
- 浜島中学校前
- 浜島中学校前
- 鴻住
- 鴻住
- 朝日山
- 朝日山
- 浜島
- 塩鹿浜
- 塩鹿浜
- 磯笛峠
- 南張
- 田曽白浜
- 田曽白浜
- 田曽口
- 田曽
- 宿浦
- 宿浦
- 迫間
- 迫間
- 山原
- 山原
- 栗木広
- 栗木広
- 夏草
- 夏草
- 堀切
- 神津佐
- 神津佐
- 神津佐農協前
- 神津佐農協前
- 南勢小学校前
- 南勢小学校前
- 薬局前
- 薬局前
- 楓江橋
- 楓江橋
- 五ヶ所
- 南勢野添
- 南勢野添
- 迫間口
- 南勢迫間
- 神縄
- 南海体育館前
- 相賀口
- 相賀
- 国道相賀
- 国府三本松
- 国府三本松
- 国府
- 国府
- ゴルフ場前
- 国府白浜
- 国府白浜
- 国府坂の上
- 国府坂の上
- 安乗口
- 安乗
- 阿児の松原
- 阿児の松原
- 甲賀大半前
- 甲賀小学校前
- 甲賀小学校前
- 甲賀
- 志島
- 安乗埼灯台口
- 神津佐神社前
- 神津佐神社前
- 国道迫間口
- 礫浦
- 長沢
- and 117 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 2 checks — up 6.9 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-31 | 64.1 | first check |
| 2026-08-01 | 71.0 | up 6.9 |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality up 34.2
What changed in this feed
Grade improved from D to C since 2026-07-31.
The feed file was re-published since 2026-07-31.
What changed inside the export
- Service now runs through 2026-11-02 (was 2026-11-01).
Read from the feed file itself, compared with the previous export. A service change is normal; this is a heads-up so nothing disappears silently.
Changed counts
- up 2 of 10 trips scheduled during the sampling window had no live predictions. (1 → 2) (scorecard_rt_trip_coverage)
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
What changed over time
On 2026-07-31 this feed started at grade D. On 2026-08-01 the grade moved from D to C. As of 2026-08-01 it holds grade C.
A plain-language history of this feed, newest first.
- 2026-08-01 Grade went D to C, realtime rose 34 points.
Everything we checked
14 findings, ordered by severity.
Show every finding
- Warning508 instances
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.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning367 instances
367 of 367 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.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning313 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.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning311 instances
311 of 311 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.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning49 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.)
Finding code: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning7 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.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
2 of 10 trips scheduled during the sampling window had no live predictions.
Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.
Fix: Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. (A vendor data-mapping question.)
Finding code: scorecard_rt_trip_coverage · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Warning1 instance
Fast travel between far stops (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'fast_travel_between_far_stops' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: fast_travel_between_far_stops · 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.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info4 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.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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.)
Finding code: unknown_file · 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.)
Finding code: 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 93 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.
Realtime reliability
The realtime feed responded on 100.0% of 63 checks over the last 9 days, with 46s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Live predictions vs schedule
Arrival predictions ran a median 58s late versus the schedule, and stayed within 167s nine times in ten. They were on time (about a minute early to five late) 99.7% of the time. 100.0% of reported vehicle positions sat on or near the published route shape.
From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.
Clears the Google and Apple Maps four-week coverage bar. This feed has 93 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 55 / 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 93 / 100
- 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/mie-kotsu-shima/2026-08-01.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-08-01. 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.