Feed status · checked 2026-07-23
Ise Okage 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.
Checked for changes 75 minutes ago; last changed 75 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
Ask your AVL vendor why the feed stopped advancing; the GTFS-Realtime header timestamp should move forward on every publish.
The realtime feed's last update was about 2 hours old when sampled. A realtime feed this far behind has effectively stopped. Riders see buses that already left, or apps quietly fall back to the schedule while still showing a live label.
⏱ A vendor support ticket; treat it as a feed outage.worth about +50 points in its category
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
205 of 205 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
150 of 150 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
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.
Ask your AVL vendor why the feed stopped advancing; the GTFS-Realtime header timestamp should move forward on every publish.
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_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.
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 52 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
- One or more realtime feeds were reachable; live-arrival coverage is not known.
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 7 kinds of issue across 47 instances (0 error, 27 warning, 20 informational).
Service data covers the next 52 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
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (おかげバス10東大淀・明野・小俣線).
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.
Sampled 9 times outside service hours: 3 of 3 configured feeds healthy; vehicle position plausibility was not measurable.
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 |
|---|---|---|
| おかげバス1御薗線 | Bus | red (no shape in feed) |
| おかげバス2辻久留・藤里線 | Bus | green (no shape in feed) |
| おかげバス8二見線 | Bus | purple (no shape in feed) |
| おかげバス10東大淀・明野・小俣線 | Bus | gray (no shape in feed) |
| おかげバス7鹿海・朝熊線 | Bus | orange (no shape in feed) |
| おかげバス環状線(左回り) | Bus | white (no shape in feed) |
| おかげバス環状線(右回り) | Bus | white (no shape in feed) |
This feed has 205 stops.
List every stop
- 宮町
- 宮町
- 尼辻
- 尼辻
- 伊勢市駅前
- 宇治山田駅前
- 伊勢学園前
- 伊勢学園前
- 山商口
- 山商口
- 黒瀬町
- 黒瀬町
- 浜郷小学校前
- 浜郷小学校前
- 通り口
- 通り口
- 汐合
- 汐合
- 荘
- 荘
- 山田原
- 山田原
- 中之町
- 古市
- 古市
- 小俣郵便局前
- ベリー藤里店
- 伊勢赤十字病院
- 一之木二丁目
- 一之木二丁目
- 一之木
- 一之木
- ミタス伊勢
- ミタス伊勢
- 大倉うぐいす台
- 伊勢病院前
- 小俣総合支所前（ぎゅーとら 小俣店）
- 小俣総合支所前（ぎゅーとら 小俣店）
- 新出(伊勢)
- 新出(伊勢)
- 庚申前
- 庚申前
- 明野（へんばや商店 本店前）
- 植山口
- 村松
- 北浜支所前
- 東大淀口
- 東大淀
- 宮山小学校前
- 宮山小学校前
- 楠部
- 四郷小学校前(伊勢)
- 四郷小学校前(伊勢)
- 一宇田
- 朝熊町
- 勢田町
- 勢田町
- 庁舎前
- 庁舎前
- 庁舎前
- 明倫小学校前
- 明倫小学校前
- 五十鈴川駅前
- 船江
- 船江
- 船江新道
- 船江新道
- 桧尻（ぎゅーとら ハイジー店）
- 桧尻（ぎゅーとら ハイジー店）
- 新開
- 新開
- 伊勢病院西口
- 伊勢病院西口
- ララパーク
- ララパーク
- 河口外科前
- 河口外科前
- 二見総合支所前
- 二見総合支所前
- 月夜見宮前
- 月夜見宮前
- 伊勢ひかり病院
- 高向北
- 高向北
- 小俣
- 小俣
- 楠部公民館
- ふじが丘口
- ふじが丘口
- 松尾観音
- 松尾観音
- 大世古（伊勢ひかり病院口）
- イオン伊勢店
- 宮町駅口（ぎゅーとら TRY mart.宮町店）
- 宮町駅口（ぎゅーとら TRY mart.宮町店）
- 今社南
- 今社南
- ミタス伊勢北
- ミタス伊勢北
- 伊勢市役所正面
- 伊勢市役所正面
- 伊勢田中病院
- 伊勢田中病院
- 一志町
- 一志町
- 宮後三丁目
- 宮後三丁目
- 一之木北
- 一之木北
- 三軒屋
- 三軒屋
- 御薗総合支所前
- 御薗総合支所前
- ハートプラザみその
- 王中島
- ゆたか幼稚園前
- ゆたか幼稚園前
- 伊勢みそのショッピングセンター
- 上長屋公民館
- 高向大社前
- 高向
- 伊勢市立図書館前
- 伊勢市立図書館前
- ぎゅーとらラブリー藤里店
- 藤里団地口
- 藤里団地南
- ふじが丘
- ふじが丘
- 旭町住宅前
- 旭町住宅前
- 前山公民館
- 前山北
- 三郷山
- 辻久留団地口
- 辻久留団地中
- 辻久留団地第三公園前
- 小俣図書館
- 西本町
- ＪＲ宮川駅前
- ＪＲ宮川駅前
- ベリー小俣店
- 北部公民館
- 野村町
- ＪＡ明野前
- 明野第四
- 航空学校南
- 航空学校北
- 溝口
- 中小俣
- 中小俣
- ふじが丘中
- ふじが丘中
- 大淀
- 大淀
- 山大淀
- 千寿台
- いせトピア
- 光の街中央
- 鷹泊
- 伊勢やすらぎ公園
- 三重ハートセンター
- トライアル伊勢店
- 鹿海口
- 西鹿海
- 東鹿海
- 朝熊インター南
- 大久保市民館前
- 大久保南
- 朝熊北
- 松下広場
- 松下口
- 民話の駅蘇民前
- 民話の駅蘇民前
- 北浦新田
- 北浦新田
- 江コミュニティセンター
- ＪＲ二見浦駅前
- 三津
- 三津
- 二見郵便局北
- 荘東
- 御塩殿神社前
- 荘西
- 荘南
- 荘南
- プライスカット伊勢二見店
- 汐合東
- 汐合東
- 下小俣公民館
- 航空学校
- 航空学校
- 明野高校
- 明野保健福祉会館
- 近鉄明野駅前
- 近鉄明野駅前
- 桜木地蔵前
- 桜木地蔵前
- 光の街西
- 光の街西
- 村松口
- 大堀川橋
- 大堀川橋
- 楠部西
- 楠部団地前
- 一宇田東
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
- Error1 instance
The realtime feed's last update was about 2 hours old when sampled.
A realtime feed this far behind has effectively stopped. Riders see buses that already left, or apps quietly fall back to the schedule while still showing a live label.
Fix: Ask your AVL vendor why the feed stopped advancing; the GTFS-Realtime header timestamp should move forward on every publish. (A vendor support ticket; treat it as a feed outage.)
Validator rule: scorecard_rt_feed_lapsed
- Warning205 instances
205 of 205 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)
- Warning150 instances
150 of 150 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)
- Warning19 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)
- Warning7 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.)
Validator rule: missing_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)
- Info12 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Validator rule: trip_headsign_matches_intermediate_stop · 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.)
Validator rule: 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.)
Validator rule: 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.)
Validator rule: 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).
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 52 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 1 checks, with 8422s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Clears the Google and Apple Maps four-week coverage bar. This feed has 62 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 82 / 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 87 / 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 50 / 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/ise-okage-bus/2026-07-23.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-23. 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.