Feed status · checked 2026-07-23
おでかけ北設（設楽町・東栄町・豊根村） (北設楽郡公共交通活性化協議会)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Aichi, 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
182 of 182 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
121 of 121 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 251 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 6 kinds of issue across 2835 instances (0 error, 2828 warning, 7 informational).
Service data covers the next 251 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
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (おでかけ北設 2 豊根東栄線, おでかけ北設 4 稲武線, おでかけ北設 N2 三沢線, おでかけ北設 N3 富山線).
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
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- おでかけ北設 1 東栄設楽線 (green)
- おでかけ北設 2 豊根東栄線 (red)
- おでかけ北設 3 東栄まちなか線 (yellow)
- おでかけ北設 4 稲武線 (pink)
- おでかけ北設 5 豊根設楽線 (yellow)
- おでかけ北設 6 津具線 (gray)
- おでかけ北設 R2 三都橋豊邦線 (brown)
- おでかけ北設 N1 坂宇場線 (gray)
- おでかけ北設 N2 三沢線 (pink)
- おでかけ北設 N3 富山線 (pink)
| Route | Type | Line color |
|---|---|---|
| おでかけ北設 1 東栄設楽線 | Bus | green |
| おでかけ北設 2 豊根東栄線 | Bus | red |
| おでかけ北設 3 東栄まちなか線 | Bus | yellow |
| おでかけ北設 4 稲武線 | Bus | pink |
| おでかけ北設 5 豊根設楽線 | Bus | yellow |
| おでかけ北設 6 津具線 | Bus | gray |
| おでかけ北設 R2 三都橋豊邦線 | Bus | brown |
| おでかけ北設 N1 坂宇場線 | Bus | gray |
| おでかけ北設 N2 三沢線 | Bus | pink |
| おでかけ北設 N3 富山線 | Bus | pink |
This feed has 182 stops.
List every stop
- 下津具
- 麓
- 見出
- 見出原
- 上津具
- 中林
- 大桑
- 南大桑
- スノ子
- 大野橋
- 奴田口
- 奴田口
- 添沢
- 小松口
- 太田口
- 栄町
- 設楽警察署前
- 田口
- 川向公会堂前
- 中川向
- 川向
- 長沢
- 峠
- 名大設楽前
- 名倉大桑
- 大平
- 名倉局前
- 下林
- 名倉小学校前
- 湯谷
- 貝津田
- 川口
- 森田橋
- 清水
- 駒ヶ原口
- 下山
- 桜橋
- 中当
- 横川
- 大井平公園前
- 稲武
- どんぐりの湯前
- とうえい温泉前
- 市場
- 市場
- 東栄町役場前
- 東栄町役場前
- 小野
- 豊川信用金庫東栄支店前
- 本郷
- 下岡本
- 三ツ瀬口
- 奈根
- 奈根住宅前
- JA直売所前
- JA直売所前
- 東栄インター
- 東栄市原
- 横引
- 横引
- 東栄駅北
- 東栄駅前
- 二タ田
- 東栄小学校前
- 柿野口
- 加賀野
- 中設楽ファミリーマート東
- 千代姫荘前
- 三沢
- 月
- 東栄中村
- 引田
- 向嶋
- 神田
- 川端
- 新黒倉
- 新和市
- 荒尾口
- 上杉平
- 東太田口
- 宮平
- 川合
- 金越
- 金越
- 上津川
- 田口高校前
- 田口高校前
- 豊根村役場前
- 豊根村診療所前
- 津川
- 杉橋
- 折古戸
- 古戸
- 日向
- 下古戸
- 布川
- 底瀬
- 下粟代
- 杉下
- 振草局前
- 粟代
- 小林
- 島口
- 柿平
- 桑平
- 下桑平
- 豊邦交流センター前
- 笠井島
- 豊邦
- 鳴沢橋
- 栗島
- 行戸
- 三都橋交流センター前
- 折立
- 下折立
- 竹島
- 大輪橋
- 田峯
- 田峯
- 清崎
- 五道
- 設楽中学校
- 金紫
- 下田
- のき山学校下
- 平岩
- 松の本住宅前
- 石堂
- 小造
- 豊根小学校前
- 老平
- 大沢
- 倉平
- 湯野島
- 熊打
- 久原
- 塩瀬
- 中平
- 豊根宇連
- 岳地土
- 中野
- 坂場
- 宮嶋
- 倭橋
- 日余沢下
- 日余沢
- 砦山
- 茶臼山口
- 御所平
- 豊根中村
- 山内
- 門原
- 樫谷下
- 宝
- 六斗畑
- 大菅下
- 大菅
- 牧ノ嶋
- 矢木沢
- 上粟世
- 粟世
- 宝沢
- 間黒
- 瀬戸
- 漆島
- 明金
- 赤坂
- 牧野口
- 浅草
- 小田橋
- 小田
- 川上
- 富山郵便局前
- 豊根市原
- 井戸川橋
- 大嵐駅
- 三ツ石・桃源橋
- 東栄診療所前
- 戦橋北
- 戦橋南
- 設楽町役場
- 清嶺小学校
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
9 findings, ordered by severity.
Show every finding
- Warning2812 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)
- Warning182 instances
182 of 182 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)
- Warning121 instances
121 of 121 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)
- Warning11 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)
- Warning4 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)
- Info5 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)
- 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 251 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 251 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 77 / 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/kitashitara-odekakehokusetsu/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.