bus-yurihonjyocity - GTFS transit data for Japan

Active
Public-transport-open-data-center Japan March 24, 2026 — March 31, 2027

About This Feed

bus-yurihonjyocity is the GTFS feed Public-transport-open-data-center publishes for Japan: 21 routes, 336 stops, 1 transit agencies. BusMaps checks and corrects it every week and serves the result through the API and as GTFS files.

Valid from March 24, 2026 to March 31, 2027.

Checked and corrected automatically. How we do it →

One API for this feed

The API behind this page serves the same 21 routes and 336 stops: stops near a point, departures, trips, timetables and the GTFS files. The requests below use the coordinates of this feed.

  • Stops within a radius of a coordinate.

    GET /v1/stopsInRadius?location=39.3573,140.1314&radius=1000
  • Departures at the nearby stops, with real-time delays where the agency publishes them.

    GET /v1/nextDepartures?location=39.3573,140.1314&radius=500&results=30
  • Itineraries between two points on this network.

    GET /v1/routes?origin=39.3573,140.1314&destination=39.4194,140.1808
  • Directions, stop order and the schedule of one route.

    GET /v1/line?routeId={routeId}
  • GTFS files Free

    The corrected feed, the source feed, GeoJSON and the validation reports.

    GET /v1/getGtfsFeedsDownloads?feedName=bus-yurihonjyocity
  • Claude, ChatGPT or any MCP client asks this network questions in plain language.

    https://mcp.busmaps.com/mcp

Base URL https://capi.busmaps.com:8443. Send the key in the capi-key header. Route ids come from the responses above.

Per-feed pages: 21 routes, 336 stops, 1 agencies

Public pages merge every feed. Sign in to browse this feed on its own, which helps when you integrate or debug it.

Sign in →

GTFS files of this feed

Two builds: the copy BusMaps corrected and validated, and the original from Public-transport-open-data-center. The API returns either one for ?feedName=bus-yurihonjyocity. Documentation →

Enhanced & Validated Recommended

Updated 2026-08-22

Cleaned, corrected, and validated against GTFS specifications. View corrections.

ZIP GTFS Feed - Corrected & Enriched
0.05 MB
Available through API only This work is licensed under Busmaps_licence_v1. Content Hash: 95ca1609eed37f53
ZIP Validation Report
0.02 MB
Available through API only
0Errors
3,615Warnings
0Info
Top Issues
non ascii or non printable char3,564
mixed case recommended field50
missing recommended field1
GeoJSON GeoJSON Data
0.02 MB
Available through API only

Original Source

Obtained 2026-03-24

Unmodified GTFS data from official sources. May contain errors or inconsistencies.

ZIP GTFS Source Data
0.05 MB
Available through API only License: CC_BY_4.0 Content Hash: 5de5971b2cc77a2e
ZIP Validation Report
0.02 MB
Available through API only
0Errors
3,879Warnings
2Info
Top Issues
non ascii or non printable char3,827
mixed case recommended field50
missing feed contact email and url1

Overlapping Feeds

Other feeds that share stops or routes with this one.

Feed Stops Overlap Routes Overlap
ugokotsu-ugokotsu-honjo 2 (9.52%)

Frequently Asked Questions

What is GTFS data?

GTFS, the General Transit Feed Specification, is the open format transit agencies use to publish schedules, stops and route shapes. Trip planners, routing engines and analytics tools read it directly.

What is the difference between enhanced and source data?

The source feed is what the agency published. The enhanced feed is the same data after BusMaps fixed the errors and inconsistencies and checked it against the GTFS specification. Use the enhanced feed in production.

Can I use this data in my application?

That depends on the licence the publisher set; you find it next to the files above. Most GTFS feeds allow free use with attribution. Check the licence before you integrate.

How do I validate a GTFS feed?

Every feed here ships with a validation report of errors and warnings. For an independent check, run the MobilityData GTFS Validator. The enhanced feed has the critical issues resolved.

All data comes from public sources. If a file was posted in error, carries a wrong licence or lacks attribution, contact us and we will fix it.