geiseivillage-gtfs-geiseivill-bus - GTFS transit data for Japan

Active
Transport-Japan Japan 2026年3月2日 — 2027年4月1日

About This Feed

geiseivillage-gtfs-geiseivill-bus is the GTFS feed Transport-Japan publishes for Japan: 3 routes, 43 stops, 1 transit agencies. BusMaps provides the original source through the API. Corrected and validated builds are not available in the API and require the data request form.

Valid from 2026年3月2日 to 2027年4月1日.

Checked and corrected automatically. How we do it →

One API for this feed

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

  • Stops within a radius of a coordinate.

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

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

    GET /v1/routes?origin=33.5234,133.8012&destination=33.531,133.8103
  • Directions, stop order and the schedule of one route.

    GET /v1/line?routeId={routeId}
  • The original source feed, source validation report, and provider links. Processed data is not returned.

    GET /v1/getGtfsFeedsDownloads?feedName=geiseivillage-gtfs-geiseivill-bus
  • 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: 3 routes, 43 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 Data Products

Request enhanced data access

The API provides source files only. Submit the data request form to discuss enhanced or custom data, coverage, and delivery terms.

Open the data request form →

Enhanced & Validated Recommended

Updated 2026-08-22

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

ZIP GTFS Feed - Corrected & Enriched
0.03 MB
Access: Submit the data request form This work is licensed under Busmaps_licence_v1. Content Hash: 44620f2ab430cd49
ZIP Validation Report
0.01 MB
0 Errors
331 Warnings
6 Info
Top Issues
non ascii or non printable char 331
trip headsign matches intermediate stop 6
GeoJSON GeoJSON Data
0.01 MB

Original Source

Obtained 2026-02-20

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

ZIP GTFS Source Data
0.03 MB
Available through API License: CC_BY_4.0 Content Hash: b7c7ff2452c74868
ZIP Validation Report
0.01 MB
Available through API
0 Errors
352 Warnings
6 Info
Top Issues
non ascii or non printable char 351
missing feed contact email and url 1
trip headsign matches intermediate stop 6

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?

Source data is the original GTFS feed obtained from the transit agency or official provider. The enhanced version has been processed to fix errors, remove inconsistencies, and ensure compliance with GTFS specifications. API plans include source data only. Enhanced data requires a separate request through the data request form. Request access through the form →

Can I use this data in my application?

Source-data use depends on the licence set by the publisher; check it before integration. Enhanced and custom data is supplied under terms agreed for your coverage, delivery, and intended use.

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, we will fix it.

Contact us →