Feed status · checked 2026-09-05
Takayama Nora My Car (のらマイカー)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Gifu, 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.
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
655 of 655 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
117 of 117 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
- 655 of 655 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
- 117 of 117 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 207 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 7 kinds of issue across 5050 instances (0 error, 5008 warning, 42 informational).
Service data covers the next 207 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
9 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (N04L のらマイカー北線 左回り, N04R のらマイカー北線 右回り, N01L のらマイカー東線 左回り, N01R のらマイカー東線 右回り, のらマイカー国府荒城線, and more).
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.
This feed has 655 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.
- N04L のらマイカー北線 左回り (pink)
- N04R のらマイカー北線 右回り (pink)
- N01L のらマイカー東線 左回り (red)
- N01R のらマイカー東線 右回り (red)
- N03L のらマイカー西線 左回り (teal)
- N03R のらマイカー西線 右回り (teal)
- N02L のらマイカー南線 左回り (yellow)
- N02R のらマイカー南線 右回り (yellow)
- のらマイカー国府荒城線 (red)
- のらマイカー国府川西線 (pink)
- のらマイカー国府宇津江線 (white)
- のらマイカー上宝平湯温泉線 (pink)
- のらマイカー丹生川荒城線 (teal)
- のらマイカー丹生川朴の木線 (gray)
- のらマイカー国府～折敷地線 (yellow)
- のらマイカー清見江黒線 (teal)
- のらマイカー清見大原線 (yellow)
- のらマイカー荘川線 (pink)
- N08 のらマイカー岩滝線 (blue)
| Route | Type | Line color |
|---|---|---|
| N04L のらマイカー北線 左回り | Bus | pink |
| N04R のらマイカー北線 右回り | Bus | pink |
| N01L のらマイカー東線 左回り | Bus | red |
| N01R のらマイカー東線 右回り | Bus | red |
| N03L のらマイカー西線 左回り | Bus | teal |
| N03R のらマイカー西線 右回り | Bus | teal |
| N02L のらマイカー南線 左回り | Bus | yellow |
| N02R のらマイカー南線 右回り | Bus | yellow |
| のらマイカー国府荒城線 | Bus | red |
| のらマイカー国府川西線 | Bus | pink |
| のらマイカー国府宇津江線 | Bus | white |
| のらマイカー上宝平湯温泉線 | Bus | pink |
| のらマイカー丹生川荒城線 | Bus | teal |
| のらマイカー丹生川朴の木線 | Bus | gray |
| のらマイカー国府～折敷地線 | Bus | yellow |
| のらマイカー清見江黒線 | Bus | teal |
| のらマイカー清見大原線 | Bus | yellow |
| のらマイカー荘川線 | Bus | pink |
| N08 のらマイカー岩滝線 | Bus | blue |
List every stop
- 吉野公民館前
- 上宝支所前
- 宮原
- 見座公民館前
- 見座
- 新田口
- 岩井戸
- 古橋
- 長倉
- 細越和仁前
- 葛山
- 笹嶋
- 笹嶋
- 田頃家
- 田頃家
- 今見
- 柏当出荷場前
- 栃尾温泉
- 栃尾温泉
- 奥飛騨総合文化センター前
- 村上
- 村上
- 国府駅前
- 国府駅前
- 垣内医院前
- 桜野団地
- 度瀬神社前
- 糠塚公民館前
- 糠塚口
- 金桶橋口
- 飛騨うりす苑前
- 瓜巣中
- 瓜巣上
- 瓜巣公民館前
- 瓜巣下
- 名張
- 福祉の里
- 三日町
- 蓑輪
- 今公民館前
- 宮地公民館前
- 東門前
- 西門前
- 八日町（国府）
- 漆垣内
- 桐谷公民館前
- 半田
- 鶴巣公民館前
- 山本公民館前
- 四十八滝口南
- 四十八滝口南
- 宇津江口
- 宇津江公民館前
- 宇津江公民館前
- 横平橋
- しぶきの湯
- 折敷地
- 三駒屋口
- 三之瀬
- 柏原
- えびすの湯
- すくなの湯
- ほおのき平スキー場口
- ほおのき平スキー場口
- 久手
- 久手
- 旗鉾
- 旗鉾寺田前
- 旗鉾寺田前
- 岩井谷
- 岩井谷谷本前
- 駄吉神童橋
- 駄吉
- 日面
- 日面
- 掛の下
- 掛の下
- 鍾乳洞口
- 鍾乳洞口
- 日影
- 日影
- 板殿
- 芦谷
- 白井
- 白井
- 笠根橋
- 根方
- 瓜田
- 瓜田野上前
- 法力上野前
- 法力公民館前
- 法力寺林前
- 北方梨ヶ平
- 北方集会所前
- 北方足立前
- 町方歯科診療所前
- 町方歯科診療所前
- 丹生川診療所前
- 町方
- 町方
- 丹生川支所前
- こま草保育園前
- 上野
- 上野公民館前
- 新張ポンプ庫前
- 新張諏訪神社前
- 千光寺橋
- 千光寺橋
- 新張二俣
- 国府龍雲橋
- 三川公民館前
- 三川
- 丹生川口
- 呂瀬金山
- 呂瀬
- 折敷地古滝前
- 大沼
- 森部
- 下三之瀬
- 上大萱
- 上大萱
- 大萱滑谷口
- 大萱公民館前
- 大萱ポンプ庫前
- 大萱上西前
- 洞口工務店前
- 洞口工務店前
- 桐山
- 桐山
- 下保
- 細越
- ひろ野公園
- 町方下
- 高山濃飛バスセンター
- 高山濃飛バスセンター
- 高山警察署前
- 高山警察署前
- 斐太高校口
- 斐太高校口
- 三福寺町
- 三福寺町
- 松之木農協前
- 松之木農協前
- 円徳寺前
- 円徳寺前
- 落合橋
- 落合橋
- 滝町
- 上滝町
- 上根方
- 下根方
- 生井神社前
- 岩滝公民館前
- 岩滝公民館前
- 岩井町公民館前
- 岩井町公民館前
- 岩井町本洞
- 大八グラウンド前
- 大八グラウンド前
- 大洞町
- 大洞町
- 鍋山団地口
- 鍋山団地口
- 高山自動車学校前
- 高山自動車学校前
- 東小学校口
- 東小学校口
- 別院前
- 別院前
- 古い町並口
- 古い町並口
- 長坂辻
- 長坂辻
- 数河
- 乗鞍青少年交流の家
- 御手洗
- 御手洗
- 上野々俣公民館前
- 下野々俣公民館前
- 下野々俣山谷前
- 下野々俣野口前
- 牧戸公民館前
- 牧戸駅
- 岩瀬公民館前
- 牛丸渡邉前
- 牛丸北野前
- 中畑中田前
- 中畑村上前
- そばの里荘川前
- そばの里荘川前
- 荘川の里前
- 荘川支所前
- 飛騨農協荘川支店前
- 脇洞
- 桜の郷荘川前
- 惣則うけ
- 一色三沢荘前
- 一色橋
- 惣則公民館前
- 一色口
- 惣則ガンザワ
- 惣則ガンザワ
- 荘川体育館前
- 荘川体育館前
- 寺河戸公民館前
- 寺河戸池戸橋
- 黒谷塩屋
- 黒谷
- 坂巻
- 三尾河
- 三谷口
- 三谷
- 池野
- 六厩岡田前
- 六厩
- 六厩口
- 大原
- 橋辰前
- 楢谷
- 麦島
- 二俣
- 巣野俣
- 宮前橋
- 下巣野俣
- 大倉滝口
- 坂下
- 落合
- 荒木橋
- 三ツ谷中屋前
- 三ツ谷下垣内前
- 福寄広場前
- 福寄田島前
- 黒地橋
- 黒地橋
- 藤瀬神社前
- 藤瀬野中前
- 藤瀬林前
- 清見保育園前
- ウッドフォーラム前
- 清見Ｂ＆Ｇ海洋センター前
- しだれ桜公園
- 大江橋
- 江黒下垣津前
- 江黒くらや前
- 江黒
- 江黒診療所前
- やまびこの家前
- 野切口
- 池本加藤前
- 三駄谷口
- and 405 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
10 findings, ordered by severity.
Show every finding
- Warning4963 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)
- Warning655 instances
655 of 655 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)
- Warning117 instances
117 of 117 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)
- Warning43 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)
- 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)
- Warning1 instance
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)
- Info39 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.)
Finding code: 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.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Platform without parent station (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'platform_without_parent_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: platform_without_parent_station · 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 207 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 207 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 76 / 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/takayama-nora-my-car/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.