GTFS Scorecard
← All agencies

Feed status · checked 2026-10-17

Takasago City Joton Bus (高砂市じょうとんバス)

Based on the feed source on file; publisher ownership is not verified

Service mode Bus

80.9 / 100

unchanged since 2026-10-16

Cataloged in Hyogo, Japan.

Covers 348 daysAccessibility gapsRealtime not yet published

Source feed: https://api.gtfs-data.jp/v2/organizations/takasagocity/feeds/jotonbus/files/feed.zip?rid=current

Takasago City's Joton Bus community 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.4, validator 8.0.1.

Checked for changes 3 hours ago; last changed 17 days ago.

Measured 3 of 4 score categories from the feed URL on file (publisher not verified).

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 configured feed URL. Publisher ownership of that URL is not verified.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

About this feed

Takasago City Joton Bus (高砂市じょうとんバス)’s published feed lists 6 bus routes, 139 scheduled trips and 119 stops. Its service dates run from 2026-10-01 through 2027-09-30. The published file last changed on 2026-09-30.

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

119 of 119 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.

Fixing this covers all 119 stops in the feed.

⏱ 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

139 of 139 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

Fixing this covers all 139 trips in the feed.

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

This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

⏱ A planned ID change, not a quick text cleanup.worth about +8 points in its category

Riders and need behind these fixes

  • Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
  • The served-area need overlays cover the United States and Canada, so none of them applies to this feed.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

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.

Finding
Fix 01 in Top things to fix: its feed evidence and the requested change.
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.

  1. Fix 01 · Read the fix guide for scorecard_wheelchair_boarding_unknown

    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. See this feed's finding-clearance log.

  2. Fix 02 · Read the fix guide for scorecard_wheelchair_accessible_unknown

    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. See this feed's finding-clearance log.

  3. Fix 03

    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. See this feed's finding-clearance log.

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 348 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

Correctness85.0 / 100

The MobilityData validator flagged 4 kinds of issue across 2679 instances (0 error, 2676 warning, 3 informational).

Freshness100.0 / 100

Service data covers the next 348 days.

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

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.

This feed has 119 stops.

Skip to route and stop data

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.

  • じょうとんバス・米田西ルート (pink)
  • じょうとんバス・米田東ルート (red)
  • じょうとんバス・曽根宝殿ルート (orange)
  • じょうとんバス・曽根高砂ルート (teal)
  • じょうとんバスミニ・阿弥陀ルート (black)
  • じょうとんバスミニ・牛谷ルート (black)
Routes in Takasago City Joton Bus (高砂市じょうとんバス)'s feed
RouteTypeLine color
じょうとんバス・米田西ルートBuspink
じょうとんバス・米田東ルートBusred
じょうとんバス・曽根宝殿ルートBusorange
じょうとんバス・曽根高砂ルートBusteal
じょうとんバスミニ・阿弥陀ルートBusblack
じょうとんバスミニ・牛谷ルートBusblack
List every stop
  • 塩市橋南
  • 塩市橋南
  • 緑丘
  • 緑丘
  • 中島
  • 中島
  • 高砂市役所
  • 若宮町
  • 若宮町
  • 小松原交差点南
  • 小松原交差点南
  • 高砂警察署
  • 高砂警察署
  • 山陽荒井駅
  • 山陽荒井駅
  • 高砂市民病院
  • 浜田町
  • 浜田町
  • 生石神社
  • 山陽高砂駅
  • 平津
  • 平津
  • 米田地域交流センター
  • 米田地域交流センター
  • 米田東
  • 米田東
  • 米新
  • 米新
  • 古新北
  • 古新北
  • 古新南
  • 古新南
  • 小松原5丁目
  • 小松原5丁目
  • 小松原3丁目
  • 小松原3丁目
  • JR曽根駅
  • 総合運動公園
  • 総合運動公園
  • 中筋1丁目
  • 中筋1丁目
  • 時光寺
  • 時光寺
  • 中筋地域交流センター
  • 中筋地域交流センター
  • 中筋4丁目
  • 中筋4丁目
  • 北池
  • 北池
  • 魚橋西
  • 魚橋西
  • 魚橋
  • 魚橋
  • 魚橋東
  • 魚橋東
  • 天川東
  • 天川東
  • 曽根北
  • 曽根北
  • 島公会堂
  • 島公会堂
  • 曽根西
  • 曽根西
  • 山陽曽根駅
  • 曽根
  • 曽根
  • 松陽中学校
  • 松陽中学校
  • 伊保西部
  • 伊保西部
  • 伊保中部
  • 伊保中部
  • 山陽伊保駅
  • 山陽伊保駅
  • 島
  • 島
  • JR宝殿駅
  • 米田西
  • 米田西
  • 鹿島口
  • 鹿島口
  • 阿弥陀
  • 阿弥陀
  • 阿弥陀小学校・阿弥陀地域交流センター
  • 阿弥陀小学校・阿弥陀地域交流センター
  • 中所
  • 中所
  • 地徳
  • 地徳
  • 鹿嶋神社
  • 市ノ池公園
  • 公園墓地
  • 長尾
  • 長尾
  • 米田南
  • 米田南
  • 北山
  • 北山
  • 北池北
  • 北池北
  • めぐみ苑
  • めぐみ苑
  • CP1
  • 大開
  • 大開
  • 春日野
  • 春日野
  • 牛谷
  • 牛谷東
  • 牛谷會館
  • 牛谷會館
  • 牛谷団地東下り
  • 塩市郵便局
  • 塩市郵便局
  • はぎ公園
  • 牛谷霊園墓地
  • 牛谷団地中央
  • 牛谷団地東上り
  • 高砂市立図書館

Over time

Overall score across the last 16 checks — unchanged since 2026-10-16.

2026-10-02: 80.92026-10-03: 80.92026-10-04: 80.82026-10-05: 80.92026-10-06: 80.92026-10-07: 80.92026-10-08: 80.92026-10-09: 80.92026-10-10: 80.92026-10-11: 80.92026-10-12: 80.92026-10-13: 80.92026-10-14: 80.92026-10-15: 80.92026-10-16: 80.92026-10-17: 80.9
Show the numbers
CheckScoreChange
2026-10-0280.9 first check
2026-10-0380.9 no change
2026-10-0480.8 down 0.1
2026-10-0580.9 up 0.1
2026-10-0680.9 no change
2026-10-0780.9 no change
2026-10-0880.9 no change
2026-10-0980.9 no change
2026-10-1080.9 no change
2026-10-1180.9 no change
2026-10-1280.9 no change
2026-10-1380.9 no change
2026-10-1480.9 no change
2026-10-1580.9 no change
2026-10-1680.9 no change
2026-10-1780.9 no change

What changed since your last check

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

Feed history

Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.

CheckedPublished fileService dates throughGrade at the time
2026-10-02 to 2026-10-17 (16 checks)6547107bde402027-09-30Current rubric: see the trend above
2026-09-30 to 2026-10-01 (2 checks)6547107bde402027-09-30B, 80.9 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-09-01 to 2026-09-29 (25 checks)07c1b35aa0622027-03-31B, 80.9 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-25 to 2026-08-31 (38 checks)4b822b457a842027-03-31B, 80.8 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-18 to 2026-07-24 (4 checks)4b822b457a842027-03-31B, 80.8 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade

What changed in this feed

Overall grade and score held steady since 2026-10-16.

Same feed file as 2026-10-16; the published zip did not change.

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

Everything we checked

6 findings, ordered by severity.

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

  • Warning139 instances

    139 of 139 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference

  • Warning119 instances

    119 of 119 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference

  • Warning16 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 for mixed_case_recommended_field · 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.)

    Finding code: unknown_column · Read the fix guide for unknown_column · 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.)

    Finding code: unknown_file · Read the fix guide for unknown_file · See MobilityData GTFS Validator rules

Conformance mark Not yet

One requirement remains for this feed to earn 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 348 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 348 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 85 / 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.

Part of the Japan portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Hyogo

Other scorecards in Hyogo, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

Takasago City Joton Bus (高砂市じょうとんバス): GTFS feed quality grade B, 80.9 of 100, checked 2026-10-17. GTFS 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/takasago-joton-bus/2026-10-17.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-10-17. 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.