GTFS Scorecard
← All agencies

Feed status · checked 2026-07-18

Toki City Community Bus (土岐市民バス)

Based on the feed this agency publishes

Service mode Bus

75.0 / 100

First scorecard for this agency

Catalogued in Gifu, Japan.

Covers 166 daysAccessibility gapsRealtime not yet published

Toki City's community bus (市民バス) network; counted as one feed record.

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 2 hours ago; last changed 2 hours ago.

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

Fix 01

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

173 of 173 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

Fix 02

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

71 of 71 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

Fix 03

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.

  1. 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.

  2. 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.

  3. 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 166 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

Correctness77.0 / 100

The MobilityData validator flagged 6 kinds of issue across 1662 instances (0 error, 1659 warning, 3 informational).

Freshness100.0 / 100

Service data covers the next 166 days.

Rider experience52.3 / 100

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.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

1 accessibility depth signal

  • 3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (市民バス２伝産会館線, 市民バス３美濃焼団地線, 市民バス７土岐南北線).

    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.

FaresLegacy fares

Fares are applied to trips.

Realtime qualityNot yet measured

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.

Skip to route and stop data

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

Routes in Toki City Community Bus (土岐市民バス)'s feed
RouteTypeLine color
市民バス１泉が丘線Busteal (no shape in feed)
市民バス２伝産会館線Busgreen (no shape in feed)
市民バス３美濃焼団地線Busteal (no shape in feed)
市民バス４河合線Busbrown (no shape in feed)
市民バス５肥田線Buspurple (no shape in feed)
市民バス６曽木＝妻木線Busteal (no shape in feed)
市民バス７土岐南北線Busred (no shape in feed)
市民バス13どんぶり会館バーデンパーク線Buswhite (no shape in feed)

This feed has 173 stops.

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

9 findings, ordered by severity.

Show every finding
  • Warning1637 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

  • Warning173 instances

    173 of 173 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

  • Warning71 instances

    71 of 71 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

  • 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

  • Warning2 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

  • Warning1 instance

    Missing feed contact email and url (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules

  • 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

  • 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.)

    Validator rule: platform_without_parent_station · See MobilityData GTFS Validator rules

  • 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

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 166 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 166 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.

Toki City Community Bus (土岐市民バス) GTFS data quality grade: C

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/toki-community-bus/2026-07-18.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-18. 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.