GTFS Scorecard
← All agencies

Feed status · checked 2026-07-23

恵那市自主運行バス（コミュニティバス）

Based on the feed this agency publishes

Service mode Bus

72.4 / 100

First scorecard for this agency

Catalogued in Gifu, Japan.

Covers 251 daysAccessibility gapsRealtime not yet published

恵那市自主運行バス（コミュニティバス） is the public schedule named by the repository. This registry item represents 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.

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

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

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

Correctness71.0 / 100

The MobilityData validator flagged 7 kinds of issue across 5524 instances (0 error, 5518 warning, 6 informational).

Freshness100.0 / 100

Service data covers the next 251 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

  • 11 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (10 まちなか巡回バス, 14 飯地線, 16 毛呂窪線, 17 藤線, 21 三郷線, 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.

FaresLegacy fares

Fares are applied to trips.

Realtime qualityNot yet measured

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 data

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

  • 10 まちなか巡回バス (red)
  • 11 まちなか巡回バス (teal)
  • 12 丸池線 (brown)
  • 13 中野方線 (purple)
  • 14 飯地線 (gray)
  • 15 笠置線 (purple)
  • 16 毛呂窪線 (green)
  • 17 藤線 (orange)
  • 21 三郷線 (teal)
  • 22 大洞循環線 (teal)
  • 23 椋実＝武並線 (teal)
  • 24 小野川線 (purple)
  • 25 元起線 (yellow)
  • 51 瑞浪＝山岡線 (teal)
  • 52 吹越線 (teal)
  • 61 明智まちなか線(滝坂・東山ルート) (red)
  • 62 明智まちなか線(片平ルート) (green)
  • 63 阿妻＝横通線 (yellow)
  • 64 明智＝峰山線 (teal)
  • 71 串原ささゆり線 (purple)
  • 72 中沢線 (purple)
  • 73 福原線 (purple)
  • 81上矢作線 (teal)
Routes in 恵那市自主運行バス（コミュニティバス）'s feed
RouteTypeLine color
10 まちなか巡回バスBusred
11 まちなか巡回バスBusteal
12 丸池線Busbrown
13 中野方線Buspurple
14 飯地線Busgray
15 笠置線Buspurple
16 毛呂窪線Busgreen
17 藤線Busorange
21 三郷線Busteal
22 大洞循環線Busteal
23 椋実＝武並線Busteal
24 小野川線Buspurple
25 元起線Busyellow
51 瑞浪＝山岡線Busteal
52 吹越線Busteal
61 明智まちなか線(滝坂・東山ルート)Busred
62 明智まちなか線(片平ルート)Busgreen
63 阿妻＝横通線Busyellow
64 明智＝峰山線Busteal
71 串原ささゆり線Buspurple
72 中沢線Buspurple
73 福原線Buspurple
81上矢作線Busteal

This feed has 363 stops.

List every stop
  • 清水西
  • 清水西
  • 下阿妻
  • 下加須里
  • 下加須里
  • 下河合
  • 下田
  • 下田良子
  • 下手向郵便局前
  • 下栃久保
  • 下沼
  • 自由ヶ丘
  • 石ヶ花
  • 正家
  • 松林名
  • 白坂
  • 新田
  • 新田大橋
  • 新道
  • 新畑
  • 新町
  • 神明町
  • 神明町
  • 石橋
  • スタンド前
  • 勢井後
  • 大日
  • 大福橋
  • 高佐
  • 高佐
  • 高瀬
  • 高波
  • 竹折
  • 竹折
  • 武並
  • 武並駅前
  • 石洞
  • 武並コミュニティ前
  • 武並診療所前
  • 田沢口
  • 田代郷入口
  • 田畑
  • 中央図書館前
  • 中央図書館前
  • 恵那南中学校下
  • 長楽寺前
  • 津島神社
  • 出合橋
  • 井尻
  • 寺口
  • 天地平
  • 土井ヶ根
  • 道木
  • 陶業文化センター
  • 藤内
  • 診療所バスターミナル
  • 常盤町四丁目
  • 土助
  • 一の沢口
  • 橡明
  • 栩杭
  • 栩杭クラブ前
  • 栃久保
  • 戸中
  • 殿町
  • 土橋
  • 中阿妻
  • 中沢
  • 中沢口
  • 一本松
  • 一本松
  • 中沢倶楽部前
  • ＪＡ上村支店前
  • 中島
  • 永田
  • 永田口
  • 中田集会所
  • 中田尻
  • 中野方振興事務所前
  • 中野方中切
  • 中野方中切
  • 中野方馬越
  • 伊保
  • 中畑裏
  • 流田
  • 二軒家
  • 西川橋
  • 西深瀬
  • 西深瀬
  • 西洞
  • 西山
  • 野井
  • 野瀬
  • 野瀬
  • 乗越
  • 乗越
  • 入野
  • 馬木
  • 橋場
  • 八幡
  • 八幡
  • 浜井場
  • 原公民館
  • 原中田信号
  • バロー岩村店
  • 東野駅前
  • 岩倉
  • 東野万場
  • 東野向島
  • 東野向島
  • 東原
  • 東山２丁目
  • 姫栗
  • 平井
  • 広瀬
  • 深萱
  • 深萱
  • 深萱上
  • 深萱上
  • 岩倉橋
  • 相走
  • 深瀬
  • 深瀬
  • 福原
  • 福原尾
  • 藤
  • 藤多目的センター前
  • 吹越
  • 不動の滝
  • 文化センター前
  • 文化センター前
  • 変電所前
  • 岩崎
  • 弁天橋
  • 法明
  • 本郷口
  • 本町
  • 槙ヶ根
  • 槙ヶ根
  • 馬坂
  • 益見バロー前
  • 益見バロー前
  • 町切
  • 町切
  • 松林
  • 松林住宅下
  • 岩村駅前
  • 松本
  • 松本口
  • 丸池公会堂前
  • 丸池市営住宅前
  • 丸池住宅口
  • 丸草
  • 丸草口
  • マレットハウス前
  • 三郷上平
  • 三郷上平
  • 三郷平
  • 岩村上町
  • 岩村上町
  • 三郷殿畑
  • 瑞浪駅前
  • 道の駅
  • 道の駅
  • 道の駅ラ・フォーレ福寿の里
  • 三作
  • 緑ヶ丘
  • 緑ヶ丘
  • 南口
  • 峯
  • 峰山
  • 峰山橋
  • 岩村警部交番前
  • 岩村警部交番前
  • 美濃
  • 宮田前
  • 椋実
  • 室屋
  • 茂立
  • 森上
  • 森下（上矢作線）
  • 森下（毛呂窪線）
  • 谷下辻
  • 安主
  • 佐藤一斎學びのひろば前
  • 佐藤一斎學びのひろば前
  • 岩竹口
  • 山足
  • 山岡駅前
  • 山岡振興事務所前
  • 山岡滝口
  • 山岡郵便局前
  • 山中
  • 山中口
  • 山中口
  • 山中口
  • 横道
  • 横道車庫
  • 岩村診療所前
  • みんなのテラス前
  • 隆生園
  • 両島
  • 両島
  • 両山神
  • 和合橋
  • 茶屋町
  • 野畑１
  • 野畑２
  • 野畑３
  • 土々ヶ根南
  • 岩村歴史資料館前
  • 恵那銀の森
  • 新栄町
  • 恵那市役所入口
  • 恵那ファミリークリニック
  • アクロスプラザ恵那
  • 河上クリニック
  • 松下眼科
  • 松下眼科
  • 肉の岩島屋前
  • 林外科内科前
  • 森川クリニック前
  • 上野
  • フヂシマヤ
  • 関戸
  • 岡瀬沢
  • 岡瀬沢中組研修センター
  • 東鉄恵那車庫
  • 恵那総合庁舎
  • 元起
  • 元起
  • 元起１
  • 原集会所
  • 下岡瀬沢
  • 下岡瀬沢
  • 梅平
  • 大井宿本陣
  • 大井橋
  • 東野１
  • 東野２
  • 大洞市営住宅
  • まきがね公園前
  • ＪＡひがしみの恵那西支店
  • 瀬々良瀬公民館
  • 中野方車庫
  • 小野川上
  • 漆原
  • 明智駅前
  • 新井中組
  • 滝坂
  • and 113 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
  • Warning5474 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

  • Warning363 instances

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

  • Warning222 instances

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

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

  • Warning10 instances

    Stop has too many matches for shape (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: stop_has_too_many_matches_for_shape · See MobilityData GTFS Validator rules

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

    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

  • Info4 instances

    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

  • 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

    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 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 71 / 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.

恵那市自主運行バス（コミュニティバス） 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/enacity-communitybus/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.