Feed status · checked 2026-07-23
コミュニティバス「のるmycar」 (滑川市)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Toyama, 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
Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Duplicate key (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +24 points in its category
Add the required column named in the finding to the flagged file.Likely your export tool
A file is missing a column that GTFS requires. Apps may reject the whole file, so riders could lose the affected routes or stops.
⏱ Often an export setting; ask your vendor if it recurs.worth about +12 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
167 of 167 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
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.
Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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.
Add the required column named in the finding to the flagged file. · 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_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.
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 69 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 9 kinds of issue across 5484 instances (2608 error, 2827 warning, 49 informational).
Service data covers the next 69 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
6 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (蓑輪 [12], 蓑輪 [11], 小森 [31], 小森 [32], 栗山 [41], 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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 蓑輪 [11] (red)
- 蓑輪 [12] (red)
- 大日室山 [21] (yellow)
- 大日室山 [22] (yellow)
- 小森 [31] (pink)
- 小森 [32] (pink)
- 栗山 [41] (orange)
- 栗山 [42] (orange)
- 市街地循環 [51] (green)
- 寺町 [61] (white)
- 北部循環 [71] (blue)
| Route | Type | Line color |
|---|---|---|
| 蓑輪 [11] | Bus | red |
| 蓑輪 [12] | Bus | red |
| 大日室山 [21] | Bus | yellow |
| 大日室山 [22] | Bus | yellow |
| 小森 [31] | Bus | pink |
| 小森 [32] | Bus | pink |
| 栗山 [41] | Bus | orange |
| 栗山 [42] | Bus | orange |
| 市街地循環 [51] | Bus | green |
| 寺町 [61] | Bus | white |
| 北部循環 [71] | Bus | blue |
This feed has 167 stops.
List every stop
- 市民交流プラザ・エール前
- 市役所前
- 中滑川駅・メリカ前
- 泉ケ丘・児童館口
- 行田公園口
- 柳原大橋
- JAアルプスなめりかわ支店前
- 野町
- 早月中学校口
- 大島新
- 北加積小学校口
- 中新
- 横道
- 二塚
- 大榎
- 森野新
- 杉本
- 杉本
- 下大浦
- 発電所口
- 大浦
- 上大浦
- みのわ温泉
- 厚生連滑川病院前
- 中川原
- アクアポケット前
- ほたるいかミュージアム前
- 常盤町2区公民館口
- 櫟原神社前
- 中町会館前
- 本陣遊園前
- 橋場
- 田中小学校前
- 滑川高校前
- 高月町
- 魚躬西
- 魚躬公民館前
- 大阪屋ショップ前
- 緑町公民館前
- 加島町消防分団前
- 幸町会館前
- 江尻公民館前
- 西滑川駅前
- 下島公民館口
- 市民健康センター口
- 滑川中学校前
- 上島
- プラント3前
- 宮窪台口
- 宮窪
- 七口西
- 小林
- 高柳
- 柴
- 安田
- 田林公民館前
- 東福寺野
- 東福寺野自然公園
- 小杉谷
- 小杉谷口
- 小森新
- 小森
- 旧JA山加積支店前
- 本江
- 滑川駅南口
- 辰野新町
- 藤栄公民館口
- 浜加積保育園前
- 北野西部
- 東部小学校前
- 追分会館前
- 大島公民館前
- 中村
- 東滑川駅口
- 中村西
- カモメ荘口
- 笠木
- 浜四ツ屋
- 高塚西
- 坪川
- 中川原西
- 滑川郵便局前
- 上小泉東
- パスタ前
- 稲泉
- 宮窪公民館口
- 七口
- 四屋新
- 栃山
- 金屋
- 東金屋
- 金屋開
- 開
- 博物館前
- 東加積小学校前
- 東加積コミュニティセンター前
- 大崎野
- 下大浦西
- 下大浦東
- 室山
- 大日
- 千鳥
- 中野
- 中野口
- 下野
- 東福寺開
- 上開
- 中開
- 中野島公民館前
- 北野中部
- 北野公民館前
- 四ツ屋東
- 早月加積地区公民館口
- 追分東
- 日本カーバイド早月工場前
- 大掛
- グリーンタウン北野口
- 大窪口
- 大窪
- YKKAP滑川製造所前
- 栗山橋
- 栗山公民館前
- 栗山北
- 上小泉中吉川
- 明文堂書店口
- 上梅沢公民館前
- 上梅沢ニュータウン
- 西加積地区公民館前
- 下梅沢公民館前
- 有金新町口
- 有金公民館前
- 運動公園前
- 中加積駅口
- 堀江東
- 南部小学校前
- 寺町
- 清寿荘前
- 赤浜
- 河端町
- 滑川駅前
- 北陸建工グループアスリートフィールド前
- 児童館前
- スポーツ・健康の森公園口
- 横道配水場前
- 大崎野北
- 上大浦公民館前
- 鉢
- 海老源前
- サンコーポラス上小泉前
- 上島公民館前
- 宮窪新
- 富士フイルム前
- 不二越滑川事業所前
- 北野南部
- 菰原八幡社口
- 柳原柿木
- 下梅沢南
- 堀江北
- 堀江
- 四ツ屋北
- 三ケ
- 水族館前
- 四ツ屋荒俣
- 荒俣公民館前
- あいのかぜ
- 法花寺
- 野町口
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
12 findings, ordered by severity.
Show every finding
- Error2605 instances
Duplicate key (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: duplicate_key · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error3 instances
A file is missing a column that GTFS requires.
Apps may reject the whole file, so riders could lose the affected routes or stops.
Fix: Add the required column named in the finding to the flagged file. (Often an export setting; ask your vendor if it recurs.)
Validator rule: missing_required_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2818 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)
- Warning167 instances
167 of 167 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)
- Warning57 instances
57 of 57 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)
- Warning7 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)
- 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)
- 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.)
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info46 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
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
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. 2 validator errors to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 2 validator errors to resolve.
- Current Met
- Service data covers the next 69 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 69 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 2608 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
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 40 / 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/namerikawacity-norumycar/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.