Feed status · checked 2026-09-05
Echizen City Citizen Bus Norossa (越前市市民バス「のろっさ」)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Fukui, 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
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
210 of 210 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
36 of 36 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
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
- A file is missing a column that GTFS requires.
- Next action
- Add the required column named in the finding to the flagged file.
- 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
- 210 of 210 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
- 36 of 36 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
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.
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.
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 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 1127 instances (3 error, 1118 warning, 6 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
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
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
This feed has no route shapes, so the map shows its stops only.
This feed has 210 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.
| Route | Type | Line color |
|---|---|---|
| 市街地循環北ルート（1便） | Bus | white (no shape in feed) |
| 市街地循環北ルート（3・5・7便） | Bus | white (no shape in feed) |
| 市街地循環北ルート（2便） | Bus | white (no shape in feed) |
| 市街地循環北ルート（4・6・8便） | Bus | white (no shape in feed) |
| 市街地循環南ルート（1便） | Bus | white (no shape in feed) |
| 市街地循環南ルート（3・5・7便） | Bus | white (no shape in feed) |
| 市街地循環南ルート（2・4・6便） | Bus | white (no shape in feed) |
| 市街地循環南ルート（8便） | Bus | white (no shape in feed) |
| 吉野・大虫ルート（吉野編・上り） | Bus | white (no shape in feed) |
| 吉野・大虫ルート（吉野編・下り） | Bus | white (no shape in feed) |
| 吉野・大虫ルート（大虫編・上り） | Bus | white (no shape in feed) |
| 吉野・大虫ルート（大虫編・下り） | Bus | white (no shape in feed) |
| 南ルート（上り） | Bus | white (no shape in feed) |
| 南ルート（下り） | Bus | white (no shape in feed) |
| 国高ルート（上り） | Bus | white (no shape in feed) |
| 国高ルート（下り） | Bus | white (no shape in feed) |
| 大虫ルート（上り） | Bus | white (no shape in feed) |
| 大虫ルート（下り） | Bus | white (no shape in feed) |
List every stop
- たけふ新駅
- 北府三丁目
- 大虫神社
- 大虫神社
- 上大虫
- 上大虫
- 四目口
- 四目口
- 下大虫
- 下大虫
- 岡本町
- 岡本町
- 北千福町
- 北千福町
- 北府三丁目
- 北府四丁目
- 北府四丁目
- 芝原一丁目北
- 芝原一丁目北
- ひかり幼稚園
- ひかり幼稚園
- 芝原四丁目・ハーツたけふ店
- 芝原四丁目・ハーツたけふ店
- 平出三丁目
- 平出三丁目
- 平出二丁目
- 平出二丁目
- 平出一丁目西
- 平出一丁目西
- 太田新保
- 太田新保
- 武生年金事務所
- 武生年金事務所
- たけふ新駅
- 武生駅
- 新町・シピイ前
- 新町・シピイ前
- 県合同庁舎
- 県合同庁舎
- だるまちゃん広場・菊人形前
- だるまちゃん広場・菊人形前
- 西小学校前
- 西小学校前
- 文化センター・中央図書館
- 文化センター・中央図書館
- ふるさと絵本館前
- ふるさと絵本館前
- 桜町
- 桜町
- タンス町通り口
- タンス町通り口
- 蔵の辻
- 蔵の辻
- 善光寺通り
- 善光寺通り
- 武生駅
- 市役所前
- 法務局
- 法務局
- 上太田保育園
- 上太田保育園
- 裁判所
- 裁判所
- 武道館・だるまちゃん広場前
- 武道館・だるまちゃん広場前
- 高瀬一丁目
- 高瀬一丁目
- 高瀬保育園
- 高瀬保育園
- 文京一丁目
- 文京一丁目
- 東千福町
- 東千福町
- 中消防署前
- 中消防署前
- 紫式部公園
- 紫式部公園
- 市役所前
- 総社
- 叔羅
- 叔羅
- 学園団地
- 学園団地
- 三ツ口
- 三ツ口
- 妙法寺・ワイプラザ武生南店
- 妙法寺・ワイプラザ武生南店
- 月見町
- 月見町
- 松森町西
- 松森町西
- 常久南
- 常久南
- しきぶ駅
- しきぶ駅
- 常久
- 常久
- 丹南健康福祉センター
- 丹南健康福祉センター
- 総社
- 桂町
- 上総社
- 上総社
- 若竹町
- 若竹町
- 住吉町
- 住吉町
- 堀川町
- 堀川町
- 錦町南
- 錦町南
- 公会堂記念館
- 公会堂記念館
- 片屋町南
- 片屋町南
- 片屋町
- 片屋町
- 氷坂町東
- 氷坂町東
- 氷坂町西
- 氷坂町西
- 桂町
- 本多二丁目
- 余田町
- 余田町
- 運転者教育センター
- 運転者教育センター
- 本保町
- 本保町
- 吉野公民館
- 吉野公民館
- 芝原五丁目
- 芝原五丁目
- 家久公園
- 家久公園
- 家久駅
- 家久駅
- スポーツ公園駅
- スポーツ公園駅
- 上太田町
- 上太田町
- 新小野
- 新小野
- 本多二丁目
- 北府駅
- 向が丘町
- 向が丘町
- 大虫小学校
- 大虫小学校
- 高森町
- 高森町
- 三ツ俣町
- 三ツ俣町
- 横根町
- 横根町
- 西部台
- 西部台
- 北山町
- 北山町
- 北山町入ヶ谷
- 北山町入ヶ谷
- ポリテクセンター
- ポリテクセンター
- 松森町
- 松森町
- 北府駅
- 本多二丁目・農協会館前
- 畷町東
- 畷町東
- 姫川一丁目
- 姫川一丁目
- 姫川二丁目
- 姫川二丁目
- 姫川北口
- 姫川北口
- 高木町
- 高木町
- 国高労働福祉センター
- 国高労働福祉センター
- 瓜生町
- 瓜生町
- 稲寄町
- 稲寄町
- 村国四丁目
- 村国四丁目
- 馬上免町
- 馬上免町
- 本多二丁目・農協会館前
- 平出一丁目東
- 長土呂町
- 長土呂町
- 商工会議所南
- 商工会議所南
- 塚町
- 塚町
- 塚町南
- 塚町南
- 横市町・武生楽市前
- 横市町・武生楽市前
- 国高公園
- 国高公園
- 村国北住宅
- 村国北住宅
- 村国公園
- 村国公園
- 武生高校前
- 武生高校前
- 朝陽台口
- 朝陽台口
- 平出一丁目東
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
- 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.)
Finding code: missing_required_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1089 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)
- Warning210 instances
210 of 210 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)
- Warning36 instances
36 of 36 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)
- Warning27 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)
- Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt to link entrances, platforms, and elevators. Give each one a level. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info3 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)
- 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.)
Finding code: 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).
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
Two requirements remain for this feed to earn the conformance mark. 1 validator error to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- 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. The feed also carries 3 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 65 / 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/echizen-city-norossa/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.