GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

Fujieda City Community Bus (藤枝市自主運行バス)

Based on the feed this agency publishes

Service mode Bus

78.5 / 100

unchanged since 2026-07-18

Catalogued in Shizuoka, Japan.

Covers 97 daysAccessibility gapsRealtime not yet published

Fujieda City's self-operated community bus (自主運行バス: 駅南循環・アクセスバス); a second Shizuoka feed record distinct from Shimada City.

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

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

154 of 154 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 +6 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 97 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

Correctness79.5 / 100

The MobilityData validator flagged 5 kinds of issue across 17 instances (0 error, 16 warning, 1 informational).

Freshness100.0 / 100

Service data covers the next 97 days.

Rider experience59.9 / 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

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

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.

  • アクセスバス (red)
  • 朝比奈線 (purple)
  • 大洲小学校線 (green)
  • 善左衛門線 (orange)
  • 駅南循環線病院系統藤枝駅行 (yellow)
  • 駅南循環線病院系統病院行 (yellow)
  • ゆらく線 (teal)
Routes in Fujieda City Community Bus (藤枝市自主運行バス)'s feed
RouteTypeLine color
アクセスバス 藤枝市富士山静岡空港アクセスバスBusred
朝比奈線Buspurple
大洲小学校線 藤枝駅南循環大洲小学校線Busgreen
善左衛門線 藤枝駅南循環善左衛門線Busorange
駅南循環線病院系統藤枝駅行 藤枝駅南循環線病院系統藤枝駅南口行Busyellow
駅南循環線病院系統病院行 藤枝駅南循環線病院系統病院行Busyellow
ゆらく線 藤枝駅ゆらく線Busteal

This feed has 201 stops.

List every stop
  • 村良
  • 村良
  • 岡部中学入口
  • 岡部中学入口
  • 子持坂
  • 子持坂
  • 若宮神社前
  • 若宮神社前
  • 藤枝市岡部支所前
  • 藤枝市岡部支所前
  • 岡部小学校前
  • 岡部小学校前
  • 岡部営業所入口
  • 岡部営業所入口
  • 青南町三丁目
  • 青南町三丁目
  • 大西町一丁目
  • 大西町一丁目
  • 大西町三丁目
  • 大西町三丁目
  • 持田製薬前
  • 科研製薬前
  • ニチビ工場前
  • ニチビ工場前
  • つつじ平団地
  • 村上開明堂前
  • 善左衛門南
  • 善左衛門南
  • 善左衛門健診センター北
  • 善左衛門健診センター北
  • 藤枝駅南口
  • ヘルスポート前
  • ヘルスポート前
  • 大洲2丁目
  • 大洲2丁目
  • 忠兵衛中
  • 忠兵衛中
  • 県立藤枝特別支援学校
  • 県立藤枝特別支援学校
  • 下青島南
  • 下青島南
  • 下青島
  • 下青島
  • 青島中学入口
  • 青島中学入口
  • 瀬戸新屋北
  • 瀬戸新屋北
  • 水上平成記念病院西
  • 水上平成記念病院西
  • 駿河台南
  • 駿河台南
  • 前島神社入口
  • 前島神社入口
  • さくら通り
  • さくら通り
  • 藤枝市立総合病院
  • 順心高校前
  • 順心高校前
  • 労金藤枝支店
  • 労金藤枝支店
  • 杏林堂藤枝田沼店前
  • 杏林堂藤枝田沼店前
  • 高洲南 北川医院前
  • 高洲南 北川医院前
  • 泉町
  • 泉町
  • 大洲四丁目 鈴木レディースクリニック前
  • 大洲四丁目 鈴木レディースクリニック前
  • 大洲中学入口
  • 大洲中学入口
  • 弥左衛門
  • 弥左衛門
  • 青葉町錦野クリニック前
  • 青葉町錦野クリニック前
  • 大洲五丁目
  • 大洲五丁目
  • 大洲小学校前
  • 大洲小学校前
  • JA大井川大洲支店
  • JA大井川大洲支店
  • 大西町二丁目
  • 大西町二丁目
  • きのこ団地
  • きのこ団地
  • 県立藤枝特別支援学校西
  • 県立藤枝特別支援学校西
  • 空港南
  • 富士山静岡空港
  • 藤枝駅前
  • 駿河台
  • 駿河台
  • 青島中学校
  • 青島中学校
  • 南駿河台四丁目
  • 南駿河台四丁目
  • 金吹橋
  • 金吹橋
  • 総合運動公園入口
  • 総合運動公園入口
  • すげがやファミリークリニック
  • すげがやファミリークリニック
  • 堀之内
  • 堀之内
  • 矢崎橋
  • 矢崎橋
  • 稲葉小学校
  • 稲葉小学校
  • 稲葉地区交流センター
  • 稲葉地区交流センター
  • 薬師堂入口
  • 薬師堂入口
  • 寺島
  • 寺島
  • 岩城神社
  • 岩城神社
  • 三井農林日東紅茶前
  • 三井農林日東紅茶前
  • 聖稜リハビリテーション病院
  • 聖稜リハビリテーション病院
  • 宮原上
  • 宮原上
  • 中山
  • 中山
  • 中山上
  • 中山上
  • 本郷普門寺前
  • 本郷普門寺前
  • 瀬戸谷小学校前
  • 瀬戸谷小学校前
  • 本郷原
  • 本郷原
  • 大出橋
  • 大出橋
  • 藤太夫島
  • 藤太夫島
  • 青葉町三丁目
  • 青葉町三丁目
  • 瀬戸谷温泉ゆらく前
  • 玉田橋
  • 玉田橋
  • 中里
  • 中里
  • 中里上
  • 中里上
  • 筈の木橋
  • 筈の木橋
  • 小布杉
  • 小布杉中
  • 小布杉中
  • 山中入口
  • 山中入口
  • 玉取沢
  • 玉取沢
  • 公民館前
  • 公民館前
  • 青島南地区交流センター入口
  • 青島南地区交流センター入口
  • 玉取
  • 玉取
  • 近又
  • 近又
  • 小園
  • 小園
  • 小園下
  • 小園下
  • 清養寺前
  • 清養寺前
  • 宮島
  • 宮島
  • 宮島中
  • 宮島中
  • 宮島下
  • 宮島下
  • 新舟
  • 新舟
  • 朝比奈第一小学校入口
  • 朝比奈第一小学校入口
  • ふれあい広場
  • ふれあい広場
  • 玉露の里
  • 玉露の里
  • 殿
  • 殿
  • 殿橋
  • 殿橋
  • 羽佐間橋
  • 羽佐間橋
  • 羽佐間
  • 羽佐間
  • もくせいの家
  • もくせいの家
  • 桂島
  • 桂島
  • 関谷橋
  • 関谷橋
  • 谷川口
  • 谷川口
  • 兎島
  • 兎島
  • 青南町四丁目坂本医院前
  • 青南町四丁目坂本医院前

Over time

Overall score across the last 2 checks — unchanged since 2026-07-18.

2026-07-18: 78.52026-07-19: 78.5
Show the numbers
CheckScoreChange
2026-07-1878.5 first check
2026-07-1978.5 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change

What changed in this feed

Overall grade and score held steady since 2026-07-18.

Same feed file as 2026-07-18; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

Everything we checked

7 findings, ordered by severity.

Show every finding
  • Warning201 instances

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

  • Warning154 instances

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

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

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

  • Warning1 instance

    Some route long names repeat the route's short name inside them.

    Apps show both names together, so riders see the number twice, like '5 5 Downtown'.

    Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)

    Validator rule: route_long_name_contains_short_name · See MobilityData GTFS Validator rules

  • Warning1 instance

    Route short name too long (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: route_short_name_too_long · See MobilityData GTFS Validator rules

  • 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

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 97 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 97 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 80 / 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 60 / 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.

Fujieda 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/fujieda-city-bus/2026-07-19.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-19. 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.