Feed status · checked 2026-10-21
Mie Kotsu Iga (三重交通 伊賀営業所)
Based on the official feed source on file
Service mode Bus
up 1.1 since 2026-10-20 · C → C
Cataloged in Mie, Japan.
Source feed: https://api.gtfs-data.jp/v2/organizations/mie-kotsu/feeds/sancoiga/files/feed.zip?rid=current
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.4, validator 8.0.1.
Checked for changes 35 minutes ago; last changed 35 minutes ago.
Measured 4 of 4 score categories from the official feed URL on file.
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 official feed URL on file.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
About this feed
Mie Kotsu Iga (三重交通 伊賀営業所)’s published feed lists 19 bus routes, 823 scheduled trips and 580 stops. Its service dates run from 2026-10-01 through 2027-01-22. It publishes realtime trip updates, vehicle positions and service alerts; when we checked, all of them answered. The published file last changed on 2026-10-21.
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
580 of 580 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.
Fixing this covers all 580 stops in the feed.
⏱ 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
823 of 823 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Fixing this covers all 823 trips in the feed.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool
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.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
⏱ Often a bulk fix in your scheduling software.worth about +8 points in its category
Riders and need behind these fixes
- Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
- The served-area need overlays cover the United States and Canada, so none of them applies to this feed.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
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.
- Finding
- Fix 01 in Top things to fix: its feed evidence and the requested change.
- 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
- Finding
- Fix 02 in Top things to fix: its feed evidence and the requested change.
- 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
- Finding
- Fix 03 in Top things to fix: its feed evidence and the requested change.
- 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.
Fix 01 · Read the fix guide for scorecard_wheelchair_boarding_unknown
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.
Fix 02 · Read the fix guide for scorecard_wheelchair_accessible_unknown
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.
Fix 03 · Read the fix guide for mixed_case_recommended_field
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 100% 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 6 kinds of issue across 1624 instances (0 error, 1617 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; 100.0% of scheduled trips had live predictions; vehicle position plausibility was not measurable; predictions ran a median of 85s behind schedule.
Routes and stops
This feed has no route shapes, so the map shows its stops only.
This feed has 580 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.
| Route | Type | Line color |
|---|---|---|
| 阿波線 | Bus | green (no shape in feed) |
| 玉滝線 | Bus | green (no shape in feed) |
| 柘植線 | Bus | green (no shape in feed) |
| 諏訪・予野線 | Bus | green (no shape in feed) |
| 月瀬線 | Bus | green (no shape in feed) |
| 上野名張線 | Bus | green (no shape in feed) |
| 西山・島ヶ原線 | Bus | green (no shape in feed) |
| 名古屋上野高速線 | Bus | green (no shape in feed) |
| 友生線 | Bus | green (no shape in feed) |
| 桐が丘線 | Bus | green (no shape in feed) |
| 曽爾香落渓線 | Bus | green (no shape in feed) |
| 赤目線 | Bus | green (no shape in feed) |
| 奥津線 | Bus | green (no shape in feed) |
| 梅が丘線 | Bus | green (no shape in feed) |
| 名張つつじが丘線 | Bus | green (no shape in feed) |
| 名張百合が丘線 | Bus | green (no shape in feed) |
| 桔梗が丘循環線 | Bus | green (no shape in feed) |
| 桔梗が丘市立病院線 | Bus | green (no shape in feed) |
| すずらん台線 | Bus | green (no shape in feed) |
List every stop
- 名古屋（名鉄バスセンター）
- 関バスセンター
- 上野市駅
- 上野市駅
- 上野市駅
- 広小路
- 農人町
- 御代インター森精機前
- 荒木（伊賀）
- 荒木（伊賀）
- 岡山口
- 岡山口
- 中之瀬
- 千戸
- 千戸
- 真泥橋
- 炊口
- 畑
- 畑
- 大山田小学校
- 大山田小学校
- 山田（伊賀）
- 山田（伊賀）
- 宮の前（伊賀）
- 大山田支所前
- 大山田支所前
- 持中
- 持中
- 中村（伊賀）
- 出後橋
- 川北
- 川北
- 三谷
- 三谷
- 正覚寺前
- 寺坂橋
- 大橋
- 富永（伊賀）
- 成田山前
- 阿波
- 平松口
- 元町（伊賀）
- 元町（伊賀）
- 汁付
- 木の館前
- 子延口
- 赤坂
- 東丸之内
- 川東
- 春日口
- あけぼの学園前
- あけぼの学園前
- 御代
- 西新堂
- 小田口
- 小田口
- 服部口
- 印代
- 印代
- 百町
- 松原（伊賀）
- 松原（伊賀）
- 松原東
- 松原東
- 西方寺
- 佐那具
- 佐那具
- 佐那具
- 佐那具病院前
- 佐那具病院前
- 西之沢
- 川西
- 居附
- 佐那具駅前
- 岩瀬
- 円徳院
- 下川合
- 上川合
- 八丁口
- 馬場
- 河合
- 阿山支所前
- 北平野
- 服部
- 市営球場前
- 市営球場前
- 水源地前
- 水源地前
- 伊賀上野駅前
- 西三田
- 大谷
- 諏訪口
- 諏訪（伊賀）
- 諏訪下出
- 希央台
- 希央台
- 後出
- 案山子畑
- 木根
- 岩倉
- 出城
- 西高倉
- 木田原
- 鳥居出
- 寺辻
- 中出
- 西山
- 公園口
- 崇広堂前
- 西大手
- 鍵屋辻
- 鍵屋辻
- 市場（伊賀）
- 長田
- 新居市民センター前
- 銀座二丁目
- 銀座二丁目
- 銀座四丁目
- 銀座四丁目
- 恵美須町
- 恵美須町
- 恵美須町
- 恵美須町
- 勧進辻
- 八幡町（伊賀）
- 八幡町（伊賀）
- 八幡町（伊賀）
- 清水
- 大野木
- 大内口
- 成和西小学校前
- 成和西小学校前
- 七本木
- 七本木
- 永谷辻
- 白樫
- 石打保育所前
- 石打
- 石打
- 尾山診療所前
- 尾山診療所前
- 尾山
- 月瀬橋
- 嵩口
- 月ノ瀬
- 月ノ瀬
- 太郎谷
- 桃香野
- 口法花
- 中法花
- 奥法花
- ぎゅーとら蔵持店
- ぎゅーとら蔵持店
- さつき団地
- さつき団地
- 守田町
- 守田町
- 桑町
- 桑町
- 桑町南口
- 桑町南口
- 名阪東インター
- 名阪東インター
- 国道並松
- 国道並松
- 市民病院下
- 市民病院下
- 本郷口
- 本郷口
- 猪田道
- 依那具
- 西出口（伊賀）
- 田中（伊賀）
- 山出（伊賀）
- 山出団地前
- 金坪
- 金坪
- 金坪
- 上野インター
- 上野インター
- 大内
- 大内
- 笠部口
- 笠部口
- 上之庄
- 菖蒲池
- 菖蒲池
- 古山局前
- 古山局前
- 蔵縄手
- 蔵縄手
- 安場
- 安場
- 南口
- 南口
- 水越
- 水越
- 田原
- 田原
- 東田原
- 東田原
- 野中（名張）
- 野中（名張）
- 西原
- 西原
- 桔梗が丘
- 蔵持
- 蔵持
- 東町（名張）
- 東町（名張）
- 東町（名張）
- 東町（名張）
- 上八町
- 上八町
- 松崎町
- 松崎町
- 名張駅前
- 名張駅前
- 向島
- 向島
- 木興団地前
- 木興団地前
- 青山町駅前
- 労働基準監督署前
- 市営住宅前
- 東小学校前
- 東小学校前
- 下友生
- 中友生
- 中友生
- 友生局前
- 上友生
- 稲葉
- 蓮池
- 喰代
- 広
- 青ノ代
- 高山
- 茅町駅前
- 茅町駅前
- 茅町東
- 茅町東
- 緑ケ丘東町
- 緑ケ丘東町
- 緑ケ丘
- 緑ケ丘
- 文化会館口
- 伊賀広域防災拠点前
- 伊賀広域防災拠点前
- 荒木団地
- and 330 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 20 checks — up 1.1 since 2026-10-20.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-10-02 | 78.0 | first check |
| 2026-10-03 | 79.4 | up 1.4 |
| 2026-10-04 | 79.4 | no change |
| 2026-10-05 | 78.4 | down 1.0 |
| 2026-10-06 | 79.4 | up 1.0 |
| 2026-10-07 | 78.3 | down 1.1 |
| 2026-10-08 | 77.5 | down 0.8 |
| 2026-10-09 | 78.0 | up 0.5 |
| 2026-10-10 | 79.4 | up 1.4 |
| 2026-10-11 | 77.7 | down 1.7 |
| 2026-10-12 | 79.4 | up 1.7 |
| 2026-10-13 | 78.3 | down 1.1 |
| 2026-10-14 | 77.7 | down 0.6 |
| 2026-10-15 | 77.5 | down 0.2 |
| 2026-10-16 | 79.4 | up 1.9 |
| 2026-10-17 | 79.4 | no change |
| 2026-10-18 | 78.2 | down 1.2 |
| 2026-10-19 | 78.3 | up 0.1 |
| 2026-10-20 | 78.3 | no change |
| 2026-10-21 | 79.4 | up 1.1 |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality up 5.1
Feed history
Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-10-21 | 75be741258ba | 2027-01-22 | Current rubric: see the trend above |
| 2026-10-20 | 929f81285dfc | 2027-01-21 | Current rubric: see the trend above |
| 2026-10-19 | 181b1f28c297 | 2027-01-20 | Current rubric: see the trend above |
| 2026-10-18 | 61393eb872bb | 2027-01-19 | Current rubric: see the trend above |
| 2026-10-17 | da83ec36a269 | 2027-01-18 | Current rubric: see the trend above |
| 2026-10-16 | 65e6fa726391 | 2027-01-17 | Current rubric: see the trend above |
| 2026-10-15 | 77728a9f9cc7 | 2027-01-16 | Current rubric: see the trend above |
| 2026-10-14 | c5ed1a9385a2 | 2027-01-15 | Current rubric: see the trend above |
| 2026-10-13 | 8de393c59027 | 2027-01-14 | Current rubric: see the trend above |
| 2026-10-12 | 75dd896787d7 | 2027-01-13 | Current rubric: see the trend above |
| 2026-10-11 | 4414b21e746e | 2027-01-12 | Current rubric: see the trend above |
| 2026-10-10 | 58946b77f7db | 2027-01-11 | Current rubric: see the trend above |
Showing the 12 most recent of 85 periods.
What changed in this feed
Overall score rose 1.1 points since 2026-10-20.
The feed file was re-published since 2026-10-20.
What changed inside the export
- Service now runs through 2027-01-22 (was 2027-01-21).
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.
No longer reported since 2026-10-20 (1 finding)
- 1 of 8 trips scheduled during the sampling window had no live predictions. (scorecard_rt_trip_coverage)
This records the later feed state. It does not establish who made a change or why.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
Everything we checked
9 findings, ordered by severity.
Show every finding
- Warning868 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 for mixed_case_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning823 instances
823 of 823 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning747 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 for missing_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning580 instances
580 of 580 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1 instance
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 for fast_travel_between_consecutive_stops · 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 for missing_feed_contact_email_and_url · 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 for unknown_column · 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 for unknown_file · 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).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
One requirement remains for this feed to earn 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 200 checks in the 25 days to 2026-10-21, with 47s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment. The window ends at the newest observation, which is not always today: if the monitor stops, this window stops with it.
Live predictions vs schedule
Arrival predictions ran a median 85s late versus the schedule, and stayed within 205s nine times in ten. They were on time (about a minute early to five late) 99.2% of the time.
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 75 / 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 100 / 100
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Part of the Japan portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in Mie
Other scorecards in Mie, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
Show your grade
Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.
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-iga/2026-10-21.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-10-21. 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.