Yuki City Loop Bus (結城市巡回バス)

What changed since the last check

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

Top three things to fix

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

   Translation foreign key violation (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

2. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

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

   Effort: A column in stops.txt; your scheduling software likely has it.

3. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.

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

   Effort: A default or per-trip field in your export.

Key facts

Feed URL

https://api.gtfs-data.jp/v2/organizations/yukicity/feeds/junkaibus/files/feed.zip?rid=current

Last checked

2026-07-19

Service window

255 days of service data remain. Last service date 2027-03-31.

Feed version

4.001-2025年03月10日 11時08分30秒-西沢ツールver8.08

Location

Ibaraki, Japan