Feed status · checked 2026-09-05
Mie Kotsu Nanki (三重交通 南紀営業所)
Based on the official feed source on file
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.3, validator 8.0.1.
Checked for changes 1 hours ago; last changed 1 hours ago.
Measured 3 of 4 score categories from the official feed URL on file.
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 official feed URL on file.
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
252 of 252 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
177 of 177 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
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
- 252 of 252 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
- 177 of 177 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 internal IDs use characters outside the basic text set.
- Next action
- 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.
- 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. 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 117 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 11 kinds of issue across 18618 instances (0 error, 18403 warning, 215 informational).
Service data covers the next 117 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.
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.
This feed has 252 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.
- 13 熊野新宮線 (green)
- 13 熊野新宮線 (green)
- 13 熊野新宮線 (green)
- 13 熊野新宮線 (green)
- 51→57 尾鷲長島線 (green)
- 54 島勝線 (green)
- 54 島勝線 (green)
- 55→54 島勝線 (green)
- 54→55 島勝線 (green)
- 41 河合線 (green)
- 41 河合線 (green)
| Route | Type | Line color |
|---|---|---|
| 13 熊野新宮線 | Bus | green |
| 13 熊野新宮線 | Bus | green |
| 13 熊野新宮線 | Bus | green |
| 13 熊野新宮線 | Bus | green |
| 13 熊野新宮線 | Bus | green (no shape in feed) |
| 13 熊野新宮線 | Bus | green (no shape in feed) |
| 13 熊野新宮線 | Bus | green (no shape in feed) |
| 14 熊野新宮線 | Bus | green (no shape in feed) |
| 14 熊野新宮線 | Bus | green (no shape in feed) |
| 14 熊野新宮線 | Bus | green (no shape in feed) |
| 13 熊野新宮線 | Bus | green (no shape in feed) |
| 13 熊野新宮線 | Bus | green (no shape in feed) |
| 57→51 尾鷲長島線 | Bus | green (no shape in feed) |
| 51→57 尾鷲長島線 | Bus | green |
| 57 尾鷲長島線 | Bus | green (no shape in feed) |
| 57 尾鷲長島線 | Bus | green (no shape in feed) |
| 51 尾鷲長島線 | Bus | green (no shape in feed) |
| 57→51 尾鷲長島線 | Bus | green (no shape in feed) |
| 54 島勝線 | Bus | green |
| 54 島勝線 | Bus | green |
| 55→54 島勝線 | Bus | green |
| 54→55 島勝線 | Bus | green |
| 54 島勝線 | Bus | green (no shape in feed) |
| 54→55 島勝線 | Bus | green (no shape in feed) |
| 55→54 島勝線 | Bus | green (no shape in feed) |
| 54 島勝線 | Bus | green (no shape in feed) |
| 41 河合線 | Bus | green |
| 41 河合線 | Bus | green |
List every stop
- 新宮駅前
- 丹鶴ホール前
- 丹鶴ホール前
- 速玉大社前
- 速玉大社前
- 成川（南紀）
- 成川（南紀）
- 中村（南紀）
- 中村（南紀）
- 飯盛口
- 飯盛口
- 矢渕
- 矢渕
- 鵜殿
- 鵜殿
- 紀宝町役場前
- 紀宝町役場前
- 堤谷
- 堤谷
- 鵜殿駅前
- 鵜殿駅前
- 平島（南紀）
- 平島（南紀）
- 梶鼻
- 上野口（南紀）
- 上野口（南紀）
- 井田小林前
- 井田小林前
- 井田駅前
- 井田駅前
- 竹島
- 竹島
- 井田舞子
- 井田舞子
- 山地口
- 山地口
- 向山（南紀）
- 向山（南紀）
- 御浜町阿田和
- 御浜町阿田和
- 阿田和端地
- 阿田和端地
- 紀南病院前
- 紀南病院前
- 阿田和駅前
- 阿田和駅前
- 平見（南紀）
- 平見（南紀）
- 御浜町役場前
- 御浜町役場前
- 萩内
- 萩内
- 市木
- 市木
- 向地口
- 向地口
- 三軒屋
- 三軒屋
- 神志山
- 神志山
- 志原尻
- 志原尻
- 釜ノ平
- 釜ノ平
- 丁塚
- 丁塚
- 中茶屋
- 中茶屋
- 芝園
- 芝園
- 立石
- 立石
- 有馬
- 有馬
- 花の窟
- 花の窟
- 羽市木
- 羽市木
- 獅子岩
- 獅子岩
- 松原（南紀）
- 松原（南紀）
- 熊野市駅前
- 熊野市駅前
- 紀北信用前
- 紀北信用前
- 記念通り
- 記念通り
- 新町（南紀）
- 新町（南紀）
- 阿須賀神社前（新宮行き）
- 新宮城跡前（新宮行き）
- 鬼ヶ城西口
- 鬼ヶ城東口
- 鬼ヶ城東口
- 大泊
- 大泊
- 船石
- 大馬谷
- 大馬谷
- 紀伊佐田
- 紀伊佐田
- 小阪
- 小阪
- 新田（南紀）
- 新田（南紀）
- 発電所前
- 発電所前
- 下地
- 主婦の店長島店
- 矢口
- 大又
- 大又
- 相賀新町北
- 相賀新町北
- 中熊
- 相賀新町(島勝)
- 相賀新町(島勝)
- 尾鷲市病院前
- 尾鷲市病院前
- 熊野大橋
- 熊野大橋
- 小又
- 小又
- 大又大久保
- 大又大久保
- 上橋
- 上橋
- 池田橋（南紀）
- 池田橋（南紀）
- 中央橋（南紀）
- 中央橋（南紀）
- 朝尾橋
- 朝尾橋
- 江竜
- 江竜
- 小口野
- 小口野
- 飛鳥
- 飛鳥
- 波瀬戸橋
- 波瀬戸橋
- 河上横町
- 河上横町
- みえ熊野古道商工会前
- みえ熊野古道商工会前
- 古里
- 古里
- 三浦
- 三浦
- 紀北町海山
- 紀北町海山
- 朝日町（南紀）
- 朝日町（南紀）
- 有久寺口
- 生熊
- 大原
- 尾鷲港
- 尾鷲港
- 加田教会前
- 加田教会前
- 上里
- 上里
- 河合（南紀）
- 紀北町役場前
- 紀北町役場前
- 漁業会館前
- 栄町（南紀）
- 栄町（南紀）
- 志子
- 島勝
- 白浦
- 白口（南紀）
- 新長島橋
- 新長島橋
- 地蔵前（南紀）
- 地蔵前（南紀）
- 十須
- 十須農協前
- 造船所前
- 玉戸
- 田山口
- 鳥先
- 鳥先
- 道瀬
- 道瀬
- 中桐
- 中里（南紀）
- 中里（南紀）
- 中新田（南紀）
- 中新田（南紀）
- 瀬木山（尾鷲せぎやまホール前）
- 瀬木山（尾鷲せぎやまホール前）
- 紀伊長島駅前
- 紀北町社会福祉協議会前
- 長浜
- 引本
- 引本口
- 船越（南紀）
- 船津（南紀）
- 船津（南紀）
- 船津駅前
- 船津駅前
- 三船中学校前
- 三船中学校前
- 海山総合支所前
- ムナシ
- 山本（南紀）
- 冷蔵庫前
- 鷲毛
- 鷲毛
- 渡利
- 尾鷲駅口
- 尾鷲駅口
- 尾鷲市役所前
- 尾鷲市役所前
- イオン前（南紀尾鷲）
- イオン前（南紀尾鷲）
- 県尾鷲庁舎前
- 県尾鷲庁舎前
- 海山バスセンター
- きれい橋
- きれい橋
- 相賀駅前（南紀）
- 赤羽学校前
- 赤羽口
- 赤羽口
- 赤羽公民館前
- 馬瀬（南紀）
- 馬瀬（南紀）
- 茂原
- 三交南紀
- 主婦の店
- プライスカット
- 海山公民館
- 海山公民館
- 尾鷲駅
- 町民サービスセンター
- 町民サービスセンター
- オレンジロード有馬
- オレンジロード有馬
- 上野町
- 上野町
- Ｆハローワーク
- Ｆハローワーク
- Ｆ相谷
- Ｆ相谷
- Ｆやまびこ
- Ｆ赤羽公園
- Ｆ此ヶ野橋
- and 2 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
14 findings, ordered by severity.
Show every finding
- Warning7051 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.)
Finding code: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning6542 instances
Some rows in stop_times.txt leave the timepoint column blank.
That column says whether a time is a real checkpoint or an estimate. Blank leaves apps guessing, and they may show your estimates as promises.
Fix: Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1. (Usually one export setting.)
Finding code: missing_timepoint_value · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4647 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)
- Warning252 instances
252 of 252 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)
- Warning177 instances
177 of 177 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)
- Warning144 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)
- Warning18 instances
Two or more routes share the same name.
Riders can't tell the routes apart in apps.
Fix: Give each route a distinct short or long name. (One field per route.)
Finding code: duplicate_route_name · 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)
- Info177 instances
Unsorted stop times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unsorted_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: unsorted_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info30 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info5 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)
- Info2 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
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · 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).
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 · 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 117 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 117 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 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/mie-kotsu-nanki/2026-09-05.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-09-05. 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.