GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

Ganu Area Shiokaze Line (岩宇地域しおかぜライン)

Based on the feed this agency publishes

Service mode Bus

76.1 / 100

unchanged since 2026-07-18

Catalogued in Hokkaido, Japan.

Covers 73 daysAccessibility gapsRealtime not yet published

The Shiokaze Line shared bus serving the Ganu area (Iwanai and the neighbouring towns) of western Hokkaido.

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

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

16 of 16 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 73 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 4 kinds of issue across 1078 instances (0 error, 1076 warning, 2 informational).

Freshness100.0 / 100

Service data covers the next 73 days.

Rider experience52.2 / 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

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

  • しおかぜライン (blue)
Routes in Ganu Area Shiokaze Line (岩宇地域しおかぜライン)'s feed
RouteTypeLine color
しおかぜラインBusblue

This feed has 105 stops.

List every stop
  • リヤムナイ
  • リヤムナイ
  • 下リヤムナイ
  • 下リヤムナイ
  • 更生
  • 更生
  • 隈元橋
  • 隈元橋
  • 発足局前
  • 発足局前
  • 北辰小学校
  • 北辰小学校
  • 大曲
  • 大曲
  • 大曲分岐点
  • 大曲分岐点
  • 柏木
  • 柏木
  • 原子力PRセンター
  • 原子力PRセンター
  • 岩内高校
  • 堀株
  • 渋井
  • 渋井
  • 滝の澗
  • 滝の澗
  • 泊中学校
  • 泊中学校
  • 茅沼
  • 茅沼
  • 南山
  • 南山
  • 福祉センター
  • 福祉センター
  • 茅沼診療所
  • 臼別
  • 臼別
  • 泊村役場前
  • 泊村役場前
  • 岩内協会病院
  • 泊
  • 泊
  • 法輪寺
  • 法輪寺
  • 糸泊
  • 糸泊
  • 汐見橋
  • 汐見橋
  • 旧神社前
  • 旧神社前
  • 寺町
  • 寺町
  • 旧盃漁協前
  • 旧盃漁協前
  • 興志内
  • 興志内
  • 盃温泉湯元
  • 盃温泉湯元
  • 茂岩
  • 茂岩
  • 岩内ターミナル
  • 弁財澗
  • 弁財澗
  • トラセ
  • トラセ
  • 商工観光センター前
  • 商工観光センター前
  • 神恵内郵便局前
  • 神恵内郵便局前
  • 神恵内村役場前
  • 神恵内村役場前
  • 青少年旅行村入口
  • 青少年旅行村入口
  • 神恵内港前
  • 神恵内港前
  • 赤石入口
  • 赤石入口
  • 稲荷神社
  • 稲荷神社
  • 赤石集会所前
  • 赤石集会所前
  • 岩内十字街
  • 岩内十字街
  • 赤石
  • 赤石
  • 北村の澗
  • 北村の澗
  • 道の駅かもえない
  • 道の駅かもえない
  • 珊内
  • 珊内
  • 川白オネナイ
  • 川白オネナイ
  • 川白
  • 川白
  • 壁坂十字街
  • 壁坂十字街
  • 大浜
  • 大浜
  • 変電所前
  • 変電所前
  • 上梨浜中
  • 上梨浜中
  • 山崎
  • 山崎

Over time

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

2026-07-18: 76.12026-07-19: 76.1
Show the numbers
CheckScoreChange
2026-07-1876.1 first check
2026-07-1976.1 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
  • Warning986 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

  • Warning105 instances

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

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

  • Warning16 instances

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

  • 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

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

Ganu Area Shiokaze Line (岩宇地域しおかぜライン) 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/ganu-area-shiokaze-line/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.