GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

Minami-Awaji City Ran-Ran Bus (南あわじ市らん・らんバス)

Based on the feed this agency publishes

Service mode Bus

71.9 / 100

First scorecard for this agency

Catalogued in Hyogo, Japan.

Covers 255 daysAccessibility gapsRealtime not yet published

Minami-Awaji City's Ran-Ran community bus.

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

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

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

Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.

The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

⏱ A small file for most flat-fare systems.worth about +15 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. Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. · 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 255 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
No fare information is published in the feed.
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

Correctness80.5 / 100

The MobilityData validator flagged 6 kinds of issue across 2883 instances (0 error, 2879 warning, 4 informational).

Freshness100.0 / 100

Service data covers the next 255 days.

Rider experience37.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 not published.

Accessibility0 / 100

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

1 accessibility depth signal

  • 7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (らん・らんバス　中央循環線（らんちゃん号）, らん・らんバス　西循環線（せい太君号）, らん・らんバス　南循環線（うずしお号）福良ルート, らん・らんバス　南循環線（うずしお号）賀集ルート, らん・らんバス　北循環線（ゆめるん号）松帆ルート, 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.

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 Minami-Awaji City Ran-Ran Bus (南あわじ市らん・らんバス)'s feed
RouteTypeLine color
らん・らんバス　中央循環線（らんちゃん号）Busred (no shape in feed)
らん・らんバス　南北幹線（すいせん号）Busbrown (no shape in feed)
らん・らんバス　東循環線（さんちゃん号）ＡルートBusorange (no shape in feed)
らん・らんバス　東循環線（さんちゃん号）BルートBusorange (no shape in feed)
らん・らんバス　西循環線（せい太君号）Buspink (no shape in feed)
らん・らんバス　南循環線（うずしお号）福良ルートBusteal (no shape in feed)
らん・らんバス　南循環線（うずしお号）賀集ルートBusteal (no shape in feed)
らん・らんバス　北循環線（ゆめるん号）松帆ルートBusgreen (no shape in feed)
らん・らんバス　北循環線（ゆめるん号）広田ルートBusgreen (no shape in feed)
らん・らんバス　北循環線（ゆめるん号）倭文ルートBusgreen (no shape in feed)

This feed has 274 stops.

List every stop
  • 陸の港西淡
  • マルナカ前
  • 松美橋
  • 松美橋
  • 徳長
  • 徳長
  • 小榎列
  • 小榎列
  • 西川
  • 西川
  • 三原中学校前
  • 三原中学校前
  • 南あわじ警察署前
  • 南あわじ警察署前
  • 南あわじ市役所前
  • 中八木
  • 中八木
  • 平成病院前
  • 中八木集会所先
  • 中八木集会所先
  • イングランドの丘
  • 淡路島牧場前
  • 淡路島牧場前
  • 鳥井
  • 鳥井
  • 立石
  • 立石
  • パルティ前
  • 円行寺
  • 円行寺
  • 市
  • 市
  • 三条
  • 三条
  • 神代
  • 神代
  • 中林病院前
  • 南所公会堂前
  • 南所公会堂前
  • イオン南淡路店前
  • 志知中島
  • 志知中島
  • 佐礼尾
  • 佐礼尾
  • 三原志知公民館前
  • 来川
  • 白崎
  • 倉川
  • 灘黒岩水仙郷
  • 黒岩
  • 吉野
  • 山本
  • 城方
  • 円実
  • 沼島汽船場前
  • 沼島汽船場前
  • 灘地区公民館前
  • 土生
  • 大川不動前
  • 大川
  • 地野
  • 仁頃
  • 丸田東
  • 丸田西
  • 丸田
  • 丸田
  • 東町海岸
  • 地野路
  • 地野口
  • 地野口
  • 東町
  • 阿万海岸
  • 西町
  • 新川
  • 新川
  • 田中医院前
  • 田中医院前
  • 中西
  • 中西
  • 吹上
  • 阿万農協前
  • 本庄
  • 佐野
  • 伊賀野南
  • 伊賀野
  • 高原
  • 筒井
  • 都劇場前
  • 当麻陵前
  • 福井
  • 福井
  • 賀集野田
  • 国衙
  • 国衙
  • 国衙
  • 神代小学校前
  • 神代小学校前
  • 富田公会堂前
  • 健康広場（淡路三原高校前）
  • きらら・ウインズ前
  • 浦壁
  • 八木病院前
  • 野原東
  • 野原西
  • 上幡多
  • 下幡多
  • おのころ島神社前
  • おのころ島神社前
  • 榎列ＢＳ（下り）
  • 榎列小学校前
  • 榎列小学校前
  • 大榎列
  • 大榎列南
  • 小榎列北
  • 寺内北
  • 寺内公会堂前
  • さんゆ～館前
  • サンプール前
  • 淡路三原高校前
  • 市青木
  • 三原郵便局前
  • 三原郵便局前
  • 市地区公民館前
  • 元三原法務局前
  • 市戎神社前
  • 市戎神社前
  • 西川南
  • 西川南
  • 湯の川
  • 伊加利農協前
  • 淡路島南ＩＣ
  • 伊毘
  • 阿那賀
  • 阿那賀団地前
  • 水口
  • 木場
  • 晴海ヶ丘
  • 小磯
  • 丸山
  • 津井橋
  • 津井郵便局前
  • 津井郵便局前
  • フローラせいだん前
  • フローラせいだん前
  • 津井
  • 中津浦
  • 松の前
  • 登立
  • 湊西口
  • 水門橋
  • 湊
  • 湊地区公民館前
  • シーパ前
  • 湊里上
  • 湊里上
  • 西路団地下
  • 玉青館前
  • 志知北
  • 八幡南
  • 八幡南
  • 八幡西
  • 赤坂
  • 原田
  • うずしお台下
  • うずしお台下
  • 仁尾
  • さくら苑前
  • 波止の浜公園前
  • 淡路人形座前
  • 南淡郵便局前
  • コミュニティプラザ向谷前
  • コミュニティプラザ向谷前
  • 向谷南
  • 向谷南
  • ゆーぷる前
  • 潮美台
  • 潮美台
  • 潮美台地区公民館前
  • 八幡東
  • 賀集郵便局前
  • 賀集西
  • 賀集
  • 賀集
  • 萬福寺前
  • 福井南
  • 新田中
  • 稲田南
  • 稲田南
  • 新田中東
  • 新田中東
  • 新田北集会所前
  • 大日寺前
  • 生子浄水場前
  • 生子浄水場前
  • 生子コミュニティプラザ前
  • 生子神社前
  • 福井北公会堂前
  • 南淡路病院前
  • 福井住宅前
  • 賀集地区公民館前
  • 掃守
  • 掃守
  • 榎列ＢＳ（上り）
  • 戒旦寺
  • 脇田公会堂前
  • 脇田南
  • 西路口
  • 西路口
  • 西路
  • 志知川公会堂前
  • 志知川西
  • 松帆活性化センター
  • 高屋
  • 江尻
  • 北浜東
  • 北浜東
  • 北浜西
  • 古津路
  • 古津路
  • 西原集会所前
  • 社教センター
  • 慶野松原
  • 西口医院前
  • 萬松園前
  • 萬松園前
  • 慶野
  • 慶野
  • 緑の道しるべ慶野公園
  • 慶野コミュニティプラザ
  • 慶野南
  • 檪田西
  • 日光寺前
  • 北方
  • 北方東
  • 広田公民館前
  • 川向岡団地下
  • 川向岡団地下
  • 淡路学園前
  • 山添公会堂前
  • 広田東
  • 広田東
  • 広田中学校前
  • 広田中学校前
  • 市場公会堂
  • 緑老人福祉センター
  • 翠鳳第一病院前
  • みどり診療所前
  • 久次米
  • 大戸
  • 鳩尾
  • and 24 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
  • Warning2862 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

  • Warning274 instances

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

  • Warning87 instances

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

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

    Validator rule: mixed_case_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

  • Warning1 instance

    The feed contains no fare information.

    Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

    Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)

    Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices

  • 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

    Some service dates fall outside the date window set in feed_info.txt.

    feed_info.txt should span every day your service runs, so apps know when the data applies.

    Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)

    Validator rule: service_window_outside_feed_period · 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 255 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 255 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 37 / 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.

Minami-Awaji City Ran-Ran 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/minamiawaji-ranran-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.