← All agencies

Feed status · checked 2026-10-15

Minamichita Town Umikko Bus (南知多町海っ子バス)

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

Service mode Bus

FDCBA

69.0 / 100

unchanged since 2026-10-14

Cataloged in Aichi, Japan.

Covers 350 daysAccessibility gapsRealtime not yet published

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

Minamichita Town's Umikko 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.4, validator 8.0.1.

Checked for changes 3 hours ago; last changed 15 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

Minamichita Town Umikko Bus (南知多町海っ子バス)’s published feed lists 3 bus routes, 49 scheduled trips and 107 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

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

Missing required field (flagged by the MobilityData validator). See the linked rule for what this affects.

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.

⏱ Varies.worth about +18 points in its category

Fix 02

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

107 of 107 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 107 stops in the feed.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category

Fix 03

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

49 of 49 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 49 trips in the feed.

⏱ A default or per-trip field in your export.worth about +15 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

Agency: Minamichita Town Umikko Bus (南知多町海っ子バス)
Finding: missing_required_field
Feed evidence: Missing required field (flagged by the MobilityData validator).
Why it matters: See the linked rule for what this affects.
Requested change: Review the rule documentation for 'missing_required_field' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Recheck: Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Evidence: https://gtfsscorecard.org/agency/minamichita-umikko-bus/?finding=missing_required_field#finding-handoff

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.

Fix 01
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.
Fix 02 · 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.
Fix 03 · 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.

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

Hi,

Our GTFS feed (Minamichita Town Umikko Bus (南知多町海っ子バス)) scored D (69.0 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Review the rule documentation for 'missing_required_field' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
   What: Missing required field (flagged by the MobilityData validator).
   Finding code: missing_required_field

2. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
   What: 107 of 107 stops don't say whether a wheelchair user can board there.
   Finding code: scorecard_wheelchair_boarding_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_boarding_unknown/

3. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
   What: 49 of 49 trips don't say whether the vehicle is wheelchair accessible.
   Finding code: scorecard_wheelchair_accessible_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_accessible_unknown/

Full scorecard: https://gtfsscorecard.org/agency/minamichita-umikko-bus/

Score by category

Correctness63.0 / 100

The MobilityData validator flagged 6 kinds of issue across 2918 instances (8 error, 2905 warning, 5 informational).

Freshness100.0 / 100

Service data covers the next 350 days.

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

This feed has no route shapes, so the map shows its stops only.

This feed has 107 stops.

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.

Routes in Minamichita Town Umikko Bus (南知多町海っ子バス)'s feed
Route	Type	Line color
海っ子バス　南知多・美浜環状線　右回り	Bus	teal (no shape in feed)
海っ子バス　南知多・美浜環状線　左回り	Bus	gray (no shape in feed)
海っ子バス　豊浜線	Bus	orange (no shape in feed)

List every stop

美舟前
美舟前
花乃丸
小佐
荒磯
荒磯
新居
新居
豊浜港・魚ひろば
高浜
高浜
豊浜
豊浜
中村
初神口
初神口
南知多町役場前
南知多町役場前
花ひろば・総合体育館前
乙方
丸豊工業前
海田川
鳶ヶ崎北
鳶ヶ崎北
鳶ヶ崎
鳶ヶ崎
鳶ヶ崎南
鳶ヶ崎南
北大井
北大井
大井
大井
長谷
長谷
片名
片名
新師崎
新師崎
師崎東口
師崎東口
師崎
師崎
半月
東中須
中須
西中須
桜公園口
大泊
サンタバーバラ　サンセット
サンタバーバラ　サンセット
山海
山海
まるはリゾート前
まるはリゾート前
東浜
内田佐七家前
内田佐七家前
大井戸
内海海岸
内海海岸
西浜田
西浜田
長城
長城
内海駅
組合前
名切
名切
楠
彼岸橋
彼岸橋
大地の丘
内海高校前
内海高校前
夫婦松
河和山
河和駅
味工房大徳（つぶてヶ浦）
味工房大徳（つぶてヶ浦）
Comas hui（コマスフイ）
Comas hui（コマスフイ）
南知多町役場下
南知多町役場下
豊浜南
豊浜南
師崎港
師崎西口
山田（南知多病院前）
ぽんかふぇ
ぽんかふぇ
蟹川橋
矢梨
矢梨
矢梨海岸
矢梨海岸
魚太郎前
魚太郎前
古布
古布
浜田整形外科・内科前
浜田整形外科・内科前
南河和
南河和
中河和
中河和
北河和
知多厚生病院前

Over time

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

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-10-02	69.0	first check
2026-10-03	69.0	no change
2026-10-04	69.0	no change
2026-10-05	69.0	no change
2026-10-06	69.0	no change
2026-10-07	69.0	no change
2026-10-08	69.0	no change
2026-10-09	69.0	no change
2026-10-10	69.0	no change
2026-10-11	69.0	no change
2026-10-12	69.0	no change
2026-10-13	69.0	no change
2026-10-14	69.0	no change
2026-10-15	69.0	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.

Feed history by published file
Checked	Published file	Service dates through	Grade at the time
2026-10-02 to 2026-10-15 (14 checks)	`2f8928beecf8`	2027-09-30	Current rubric: see the trend above
2026-09-30 to 2026-10-01 (2 checks)	`2f8928beecf8`	2027-09-30	D, 69 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-25 to 2026-09-29 (63 checks)	`63179a7955ac`	2026-09-30	F, 52 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-19 to 2026-07-24 (3 checks)	`63179a7955ac`	2026-09-30	C, 76.6 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade

Everything we checked

9 findings, ordered by severity.

Show every finding

Error8 instances
Missing required field (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_required_field' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: missing_required_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning2892 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 (opens the validator rules on an external site)
Warning107 instances
107 of 107 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 (opens the GTFS Schedule reference on an external site)
Warning49 instances
49 of 49 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 (opens the GTFS Schedule reference on an external site)
Warning12 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 (opens the validator rules on an external site)
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.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide for missing_feed_contact_email_and_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info3 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide for big_gap_in_service · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info2 instances
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 (opens the validator rules on an external site)
Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

Conformance mark Not yet

Two requirements remain for this feed to earn the conformance mark. 1 validator error to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

Valid Not yet: 1 validator error to resolve.
Current Met: Service data covers the next 350 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 349 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 8 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.

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

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

Similar feeds in Aichi

Other scorecards in Aichi, 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.

Badge HTML

<a href="https://gtfsscorecard.org/agency/minamichita-umikko-bus/"><img src="https://gtfsscorecard.org/agency/minamichita-umikko-bus/badge.svg" width="320" height="58" alt="Minamichita Town Umikko Bus (南知多町海っ子バス): current GTFS data quality score from GTFS Scorecard"></a>

Badge Markdown

[![Minamichita Town Umikko Bus (南知多町海っ子バス): current GTFS data quality score from GTFS Scorecard](https://gtfsscorecard.org/agency/minamichita-umikko-bus/badge.svg)](https://gtfsscorecard.org/agency/minamichita-umikko-bus/)

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/minamichita-umikko-bus/2026-10-15.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-15. 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.

GTFS Scorecard. (2026). Minamichita Town Umikko Bus (南知多町海っ子バス) GTFS feed-quality record, dated 2026-10-15 (grade D (69.0/100), rubric v1.4, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 2f8928beecf8…). https://gtfsscorecard.org/data/artifacts/minamichita-umikko-bus/2026-10-15.json

@misc{gtfsscorecard-minamichita-umikko-bus-2026-10-15,
  title        = {Minamichita Town Umikko Bus (南知多町海っ子バス) GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/minamichita-umikko-bus/2026-10-15.json}},
  note         = {Checked 2026-10-15; rubric v1.4; gtfs-validator 8.0.1; reader archive profile raw-v1; grade D (69.0/100)}
}

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.